Bugzilla 2.18 Branch rules

[David Miller]

We will be branching for Bugzilla 2.18 within the next couple days 
(Finally!!!)

A couple rules for the 2.18 branch:

There will be a new flag added for approval2.18.  If you want to check 
in on the 2.18 branch, request this.  (This works just like the existing 
approval2.16 flag for the 2.16 branch).

In general, we only want low-risk high-impact bugfixes on the branch. 
If you think something qualifies, request the blocking2.18 flag, and 
I'll make a decision on it.

*ANYTHING* that gets checked in on the branch also gets checked in on 
the trunk, unless there's some damn good reason it shouldn't be (like 
the section of code it belongs to has already been replaced by some new 
feature introduction on the trunk or something like that).

Templates *DO* *NOT* *GET* *TOUCHED* unless *absolutely* necessary. 
This may seem a little harsh, but this is a necessity to give the 
localizers time to get their templates for 2.18 ready prior to the 
release.  If we can promise the localizers that the templates won't 
change between now and 2.18, they can proceed with localizing without 
fear of their templates breaking, and perhaps have some of the 
localizations ready to be posted at the same time we release.

I may make an exception to that last one for the HTML validation stuff. 
  Those changes should be pretty minor though, and easy enough for the 
localizers to pick up on later.

Any comments or questions, feel free to speak up.

-- 
Dave Miller      Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/             http://www.bugzilla.org/