Kevin:
1. What exactly needs to be done to bump the version in the tree ? Just change
the values in xc/config/cf/xorgversion.def ?
2. To which version/revision should this first release canidate be set ?

(In reply to comment #1)
> 1. What exactly needs to be done to bump the version in the tree ? Just change
> the values in xc/config/cf/xorgversion.def ?

Yes, to bump the version numbers in the tree, simply update the xorgversion.def
file.

> 2. To which version/revision should this first release canidate be set ?

For release candidates, the version number should be 6.8.1.901 for the first
release candidate and 6.8.1.902 for the second, etc.  Also, set the date in
xorgversion.def to the same date as when the release candidate is ready.

After you've set the version number and the date in xorgversion.def and checked
in that file, you should tag the tree so that people can check out against the
release candidate for testing.  For the first release candidate, you should tag
the tree with "XORG-6_8_1_901".

Most of this is explained in the Versions document found in .../hw/xfree86/doc,
but some of the info there is incorrect and other info is missing.  Since this
is the first large point release that we've done, I think this document should
be updated, which I will take care of.

There is another problem: The code in .../hw/xfree86/common/xf86Init.c does not
handle release candidates for point releases properly.  It only handles major
releases.  I will attach a patch to fix that here.  You might want to check this
patch in before tagging the tree so that the version numbers are printed properly.

Created attachment 1556 [details] [review]
[FIXED_X11R68x] Fix for point releases

This should take care of the problems printing the release candidate version
number for point releases.

Comment on attachment 1556 [details] [review]
[FIXED_X11R68x] Fix for point releases

Patch checked-in into X11R6.8.x stable branch:

/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.365.2.106; previous revision: 1.365.2.105
cvs commit: Using deprecated info format strings.  Convert your scripts to use
the new argument format and remove '1's from your info file format strings.
/cvs/xorg/xc/programs/Xserver/hw/xfree86/common/xf86Init.c,v  <--  xf86Init.c
new revision: 1.12.2.2; previous revision: 1.12.2.1
cvs commit: Using deprecated info format strings.  Convert your scripts to use
the new argument format and remove '1's from your info file format strings.
Mailing the commit message to xorg-commit@lists.freedesktop.org...

Created attachment 1557 [details] [review]
[FIXED_X11R68x] Patch to bump the version number in the branch to X11R6.8.1.901 ...

Comment on attachment 1557 [details] [review]
[FIXED_X11R68x] Patch to bump the version number in the branch to X11R6.8.1.901 ...

Patch checked-in into X11R6.8.x stable branch:

/cvs/xorg/xc/ChangeLog,v  <--  ChangeLog
new revision: 1.365.2.107; previous revision: 1.365.2.106
cvs commit: Using deprecated info format strings.  Convert your scripts to use
the new argument format and remove '1's from your info file format strings.
/cvs/xorg/xc/config/cf/xorgversion.def,v  <--  xorgversion.def
new revision: 1.1.4.2; previous revision: 1.1.4.1
cvs commit: Using deprecated info format strings.  Convert your scripts to use
the new argument format and remove '1's from your info file format strings.
Mailing the commit message to xorg-commit@lists.freedesktop.org...

I've tagged the X11R6.8.x stable branch with the RC1 ("XORG-6_8_1_901") tag a
feww secs ago like this:
% export CVS_RSH=ssh
% export CVSROOT=:ext:hackedaccount@cvs.freedesktop.org:/cvs/xorg
% cvs -z6 checkout -r XORG-6_8-branch xc
% cvs -z1 tag XORG-6_8_1_901 xc

Created attachment 1562 [details]
X11R6.8.2RC1 release annoucement [Draft version 0.1]

Draft for the release annoucement.
Missing things:
- The URL for the source tarballs (it's 4:04 am here now, I'll defer that work
to tomorrow)
- ... Brookline MA, December 17, 2004 ..." - which town/country should be
listed here (in my case it would be "Giessn/Hessen/Germany" ... :)

Comments/suggestions welcome...

Marking bug as FIXED.