Messages in this thread | | | Date | Mon, 26 Nov 2001 09:41:10 -0800 | From | David Rees <> | Subject | Re: Release Policy [was: Linux 2.4.16 ] |
| |
On Mon, Nov 26, 2001 at 01:54:11PM -0200, Marcelo Tosatti wrote: > > > I like the ISC's release methods. The do -rc's (-pre's would be fine > > for the kernel as it is already established), each -rc fixes problems > > found with the previous. When an -rc has been out long enough with no > > more bug reports they release that code, WITHOUT changes. > > Thats exactly the idea with the "pre-final" thingie.
Most groups use -rc release candidate releases, so using that instead of -pre-final would lead to the least confusion.
A 2.4.17 release might look like this:
Release 2.4.17-preX until all the new stuff you want is in. Release 2.4.17-rcX until no-one complains about the new stuff. Release the last 2.4.17-rcX as 2.4.17 and hope no one finds anything embarassing (which will probably happen anyway.
Seems to me though, that you can simply put a note in your Changelog which -pre releases are bound to be to the next final revision, this will save us from yet another numbering scheme.
-Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |