On Wed, 15 Sep 1999, Keith Whitwell wrote:

> I think that the long development cycle for 3.1 was justified (I have to say that
> really...), but it'd be nice to cycle more rapidly for the next few iterations.
 
Yes - the dev cycle for 3.1 was justified - but it highlights
the need to go to an odd-even development cycle.

> I've actually got a fair chunk of the Mesa core work done, so
> it should be pretty much ready to drop into the 3.2 as soon as
> that work starts.

Could I plead for 3.1 to progress to 3.2 as soon as it's stable,
then to maintain 3.2 as the "stable" release with new dev going
into 3.3 (kinda like the Linux kernel dev advances). That somewhat
removes the pressure to cycle major versions quite so quickly.

There were quite a few simple fixes that could have gone into 3.0.n
that have been delayed for too long while we wait for 3.1. to appear.

eg The GLX Proxy texture bug. Was fixed *ages* ago in 3.1 - but
3.1 has been too unstable to run my stuff (eg Texture problems).
It would have been a simple thing to push out a 3.0.2 with that
fix in it so we would not have had to wait for the massive
(but necessary) upheavals in 3.1 to settle down.  The odd/even model
for code release is much more appropriate now than it was in
the Mesa 2.x era because there are now so many more people dabbling
in the core code.

There is also the (unresolved) issue of the Mesa numbering scheme
in relation to the library name requirements of opengl/linux-base
proposal.  That needs to be resolved before we release 3.1/3.2
because 3.1 switches us to libGL.so as the installation location
rather than libMesaGL.so and if we call it libGL.so.3.1 we'll
cause problems later when/if the OpenGL spec revision ever gets
that high.

That means that we have a one-shot chance to sort the naming issue
out *before* 3.1 is released - and it makes sense (to me at least)
to decide on the odd/even numbering at the same time.

Steve Baker                (817)619-2657 (Vox/Vox-Mail)
Raytheon Systems Inc.      (817)619-2466 (Fax)
Work: [EMAIL PROTECTED]      http://www.hti.com
Home: [EMAIL PROTECTED] http://web2.airmail.net/sjbaker1



_______________________________________________
Mesa-dev maillist  -  [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev

Reply via email to