Template versioning

[GavinS]

Also related to template versioning is bug#186866

http://bugzilla.mozilla.org/show_bug.cgi?id=186866

which is the one about checking for outdated or changed versions of
templates.

When I asked about template versioning a few months ago, the reply was
that template versioning wasn't necessary or being done until that bug
was resolved.

Personally, I'd vote for starting to change the template version
numbers now, as described in bug 186866 and 140527, so that people can
get used to both doing it and reviewing it. (We would also see if it
does cause an unmanageable number of cvs conflicts, as some fear it may
do.)

Translators may also be able to start using (but not relying on!) the
system, see if it helps them, and provide feedback.

Gavin


>>>>> "Gervase" == Gervase Markham <gerv at mozilla.org> writes:

Gervase> Hmm. We appear to have forgotten about our cunning scheme for
Gervase> template versioning. (See
Gervase> http://bugzilla.mozilla.org/show_bug.cgi?id=140527)

Gervase> So what's the plan? Do we do an assessment before the 2.18
Gervase> release and bump the version numbers appropriately on every
Gervase> template? Sort of the "big bang" approach?

Gervase> Gerv

Gervase> - To view or change your list settings, click here:
Gervase> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=bugzilla@chimpychompy.org>