Ralph Giles wrote:
>
> On Wed, 24 Nov 1999, Brian Paul wrote:
>
> > > The mesa_3_2_dev branch still thinks it's 3.1, and our configure script
> > > reports it as such.
> >
> > It's correct as-is. The mesa_3_2_dev branch will end with the release
> > of Mesa 3.2 but the Mesa 3.1 release is also pending on this branch.
> > 3.2 will be the stabilization of 3.1.
>
> Ah. Fascinating. :)
>
> > I know this is a bit of a mess now. But 3.1 should be released soon.
> > I'm just waiting for the final GLU tessellator code and some bug fixes
> > from Keith Whitwell. Then, that branch really will be 3.2 code.
>
> Ok, I guess I'd mis-understood your release plans. Sorry I haven't been
> following the list very carefully lately. I had heard you were switching
> to the even/odd release module, and so assumed that 3.1 would be released
> as 3.2.
After 3.1 is released I expect there will be another batch of bug
reports since a lot of people don't try the beta releases and a _lot_
of code has changed since version 3.0. The bugs we iron out of 3.1
will result in 3.2, the final, stable release.
> Are there plans for internal changes between 3.1 and 3.2?
No, just bug fixes/cleanup.
> Which one should be be supporting?
> I don't think it makes sense for us (the glx project) to
> track 3.3 for now, since we're trying to get out a release, but I'm
> wondering if we'll want/need to support both 3.1 and 3.2.
3.1/3.2 will be the same, except for bug fixes.
-Brian
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
