On Tue, Mar 02, 1999 at 01:17:18PM +0100, Richard Braakman wrote:
> Michael Bramer wrote:
> > I think:
> > If we have release slink und we don't get many bugreports, we make a new
> > round and frozen potato.
> > We have > 300 new packages in potato and many packages have new (higher)
> > version numbers.
> >
> > Let release slink, wait 2-6 weeks and make a frozen and a new stable.
>
> That was the plan for slink itself! It failed miserably. If we
> try it again, I suspect we'll just have another release that takes
> just as long, but *without* all the stuff we wanted to add. And
> then we'll try it again, and in the meantime we'll never get any
> of these goals done.
>
> I think we should have at least 2 or 3 months to play with potato.
I have no problem with the long play time, _if_ we make a short frozen
time.
If we go this way:
* announce the starttime of the frozen.
* mail the 'Release-critical Bugreport' from unstable monthly
* mail the 'Release-critical Bugreport' from unstable weekly in the
last 5 weeks of the unstable potato
* remove all packages with release-critical Bugs on frozen time (or
1-2 weeks later) (and replace the package with the last stable version)
* only bug-fix uploades go in frozen
* have a nice stable (?)
The 'play'-time and the frozen time must IMHO shorter 4-5 months. Free
software have a to high speed for a longer release time.
Grisu
--
Michael Bramer -- a Debian Linux Developer http://www.debian.org
PGP: finger grisu@master.debian.org -- Linux Sysadmin -- Use Debian Linux
"A system without Perl is like a hockey game without a fight." -- Mitch Wright
Attachment:
pgpgRGePgizsA.pgp
Description: PGP signature