Are we doing a X11R6.8.x maintaince release ?

Torrey Lyons torrey at
Tue Oct 12 11:20:40 PDT 2004

At 12:05 PM -0400 10/12/04, Kristian Høgsberg wrote:
>Proposed guidelines for maintaining the stable branch:
>  - Each bug fixed in the stable branch must have a corresponding
>    bugzilla bug.  The ChangeLog entry must reference the bugzilla bug.
>  - For each point-release there must be a tracker bug.  Every bug
>    fixed on the 6.8 branch should be added as a dependency of the
>    currently open tracker bug.  This will make it easy to track what
>    exactly has been fixed, and will be a big help when preparing
>    release notes for the release.

The idea of maintaining a stable branch for one 
previous version and doing occasional maintenance 
releases is very good. However, these two 
proposed guidelines are overly restrictive. I 
have typically back ported important bug fixes. 
However, those guidelines would represent enough 
of a new potential barrier that I'd probably skip 

In particular, there are already plenty of change 
tracking features internal to CVS. For example, 
all the changes are already documented in the 
ChangeLog and this can be used for the release 
notes just as easily in preparing release notes. 
It does not add any value to force people to 
document their changes in parallel in X.Org's 

Bugzilla is a useful tool, but making it a 
mandatory tool does exact a price in 
productivity. This is a worthwhile price to pay 
in the middle of a pre-release code freeze, but 
not here.


More information about the xorg mailing list