Template versioning

Christian Robottom Reis kiko at async.com.br
Tue Dec 9 14:55:09 UTC 2003

On Tue, Dec 09, 2003 at 01:57:40PM +0000, Gervase Markham wrote:
> Hmm. We appear to have forgotten about our cunning scheme for template 
> versioning. (See http://bugzilla.mozilla.org/show_bug.cgi?id=140527)
> So what's the plan? Do we do an assessment before the 2.18 release and 
> bump the version numbers appropriately on every template? Sort of the 
> "big bang" approach?

Bradley has voiced his opinion in the past that templates will require
modifications for almost any change implemented. I tend to agree, but
mostly because we've been changing templates a lot, particularly now
when we are evaluating CSS changes and UI modifications -- our pages
just aren't stable enough. 

I think it makes sense to use template versioning over a stable branch,
where less checkins go in and we can really restrict *what* goes in; we
can make it a policy that *all* changes to templates require evaluation
and version updates. 

For the trunk it's a lot of effort, and IMO it's not going to help
customizers/localizers much given that we're still constantly whacking
the pages way beyond typo fixes. This from my personal experience with
running a customized site.

I would like to see the version comment moved inside the <doctype>
declaration, though [given that it's apparently causing problems with
IE, but you didn't hear that from me].

Take care,
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331

More information about the developers mailing list