RE: so what? Re: Debian development modem
IMO six months is too long. How about freeze every three months and
release twice a year at fixed dates? Something like the NetBSD schedule.
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
email@example.com | Europark A2, Adenauerstr. 20
firstname.lastname@example.org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
> -----Original Message-----
> From: Ian Jackson [SMTP:email@example.com]
> Sent: Thursday, May 28, 1998 2:49 PM
> To: Debian developers list
> Subject: Re: so what? Re: Debian development modem
> I see one big reason why hamm is taking so long to release: it's not
> compatible with bo.
> This has made developers (many of whom were attracted by Debian's
> incremental and partial upgrade capability) very reluctant to
> upgrade. It has also made it impossible to fix bugs in bo.
> Let us never make this mistake again.
> We should, instead, simply freeze unstable every six months, and
> release it three months or so later. A package should be allowed into
> frozen (or stable) if it would improve the quality of the
> We have often good backwards compatibility, so that it doesn't matter
> if our stable distribution is a mixture of a.out and ELF or libc5 and
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org