Subject: Re: Release cycles (Was: Re: RealAudio)
To: None <current-users@NetBSD.ORG>
From: Michael C. Richardson <firstname.lastname@example.org>
Date: 11/01/1997 15:49:47
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Todd" == Todd Vierling <email@example.com> writes:
Todd> However, it shouldn't be nearly so bad to make periodic
Todd> subreleases (1.3.1, 1.3.2, ...) on the way to 1.4. And
Todd> _not_all_architectures_ should be required to be ready when
Todd> a subrelease cut is made; this is an interim release system.
Yes! Please. Let's do this.
I would further like to see a release date for 1.3.1 *NOW*, as well
as a "goals for 1.4" now as well. Maybe a 1.3.2 date.
a) this allows people to back out things from 1.3 if it isn't
working out, and know when it will get released (e.g. zs driver for
b) users can plan when they are going to upgrade.
I would propose that 1.3.1 get frozen February 1st, and released two
The other option is to pull a partial Microsoft and dispense with
the third number. Let's just call the next one 1.4. If we hit 1.9, and
don't have a 2.0, then we just declare 2.0 anyway.
:!mcr!: | Network and security consulting/contract programming
Michael Richardson | I do IPsec policy code for SSH <http://www.ssh.fi/>
Personal: firstname.lastname@example.org. PGP key available.
-----BEGIN PGP SIGNATURE-----
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
-----END PGP SIGNATURE-----