Date: Thu, 20 Apr 1995 15:56:18 -0700 From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com> To: Gene Stark <gene@starkhome.cs.sunysb.edu> Cc: hackers@FreeBSD.org Subject: Re: Minutes of the Thursday, April 13th core team meeting in Berkeley. Message-ID: <12952.798418578@freefall.cdrom.com> In-Reply-To: Your message of "Thu, 20 Apr 95 00:13:20 EDT." <199504200413.AAA05141@starkhome.cs.sunysb.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Perhaps this idea is a bit radical, but I think it would be beneficial > to separate the technical development goals of FreeBSD from the pressures > to get a CD to market. A method I have been applying to get decent > snapshots to use is to build the world regularly, observing the general > stability of the system and reading the mailing lists to assess the > frequency of changes to key portions of the system. When the frequency > of key source changes appears to have reached a local minimum and the > number of serious instability reports seems small, I try to roll a > snapshot. It's a perfectly reasonable idea, but it involves a fair bit of discipline on the part of the release engineer, and up to now the release-rolling process has been arcane enough that not many (including us) could even figure it out well enough to generate a release. Perhaps, as rolling releases becomes easier and easier for the lay-person to do, we'll have broader interest in this by people who's SOLE interest is release engineering? It's never been mine, but it seems like folks like Poul and I have been getting stuck with it. I'd like this to change. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12952.798418578>