I plan on creating the 3.2 development branch today.
The branch tag will be mesa_3_2_dev.
When Mesa 3.1 is released I'll tag that branch's sources mesa_3_1.
When Mesa 3.2 is released I'll tag that branch's sources mesa_3_2.
As a reminder, 3.1 (an odd release) will (pessimistically) be
considered an unstable release while 3.2 (an even release) will
be the stabilization release. Hopefully, the 3.1 release won't
generate many bug reports and 3.2 will follow soon after.
The main/default CVS trunc will be 3.3 development.
If you want to work on both branches you should keep your
current source directory (it'll be 3.3) and create a second
directory tree for mesa_3_2_dev. You can do that by running
"cvs checkout -r mesa_3_2_dev" and "cvs update" in a new
directory.
If you want to only work on the mesa_3_2_dev branch you'll
just have to do a "cvs update -r mesa_3_2_dev" in your
current tree.
If you want to only work on the main/default 3.3 trunc you
don't have to do anything special.
I'll be checking in new 3.3 files over the next day or two.
I'll try not to break the build but it could happen.
-Brian
PS: Would somebody on the GLX project mailing list forward
this info to them?
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
