I've been wanting to finish Mesa 3.1 for some time now but
there's still outstanding bugs to be fixed. Keith's been
working on those and in the mean time I've been working on
newer development. We believe it's time to make a branch so
we can do both.
Here's the plan:
We're adopting an even/odd version numbering system similar
to Linux. Odd versions are experimental/development versions
and even versions are stabilizations of the preceeding odd
version.
Mesa 3.1 is considered somewhat unstable because of all
the new changes. Hopefully it'll be "done" soon. Any bug
fixes for it will go into a 3.2 release sometime thereafter.
Meanwhile, Mesa 3.3 will be the focus of new development.
That's where I'm headed.
To support thse paths we'll make a new branch with the
tag MESA_3_2 which will have the last of the 3.1 bug
fixes and the 3.2 follow-on fixes.
The main/default Mesa branch will be 3.3 since that's
the long-term path.
Bug fixes made in 3.1 / 3.2 will have to be duplicated
in 3.3 (when applicable). Eventually the 3.2 branch will
be left behind.
Personally, on my system I'll have two CVS trees, one for
3.1/3.2 and the other for 3.3. Each of you can do that or
just stick with one branch or the other.
I propose making the branch next Tuesday (or so). At that
time I'll provide details on what to do CVS-wise.
-Brian
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
