From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8730 invoked from network); 14 May 2004 18:01:43 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 14 May 2004 18:01:43 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1BOh0B-0000lH-F6 for arch-gentoo-dev@lists.gentoo.org; Fri, 14 May 2004 18:01:43 +0000 Received: (qmail 9175 invoked by uid 50004); 14 May 2004 18:01:43 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 17337 invoked from network); 14 May 2004 18:01:43 +0000 Date: Fri, 14 May 2004 14:01:11 -0400 From: Grant Goodyear To: gentoo-dev@lists.gentoo.org Message-ID: <20040514180111.GC11475@violet> Mail-Followup-To: gentoo-dev@gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qcHopEYAB45HaUaB" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: [gentoo-dev] What are Gentoo releases? X-Archives-Salt: dd58aba7-68ca-467a-983c-9210f77c8650 X-Archives-Hash: a319ad433621697c7371967c088edc7c --qcHopEYAB45HaUaB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dear all, I would like to get a discussion rolling about what, exactly, constitutes a Gentoo release, and what we want to accomplish with any given release. I'm forwarding (with Aron's permission) an e-mail that agriffis sent to -releng describing his view about what our release process currently is. I believe that this description does describe the current process reasonably well, but perhaps some may disagree. More important, is this process what we _want_ our release process to be? Gentoo "releases" are different from those of any other distribution, inasmuch as the "version" of Gentoo that a user is running (meaning what collection of packages are on the user's machine) depends on what *hour* Gentoo was installed, so from a technical standpoint the "release" has more to do with the installation medium than anything else. At the same time, it is important to recognize that releases also serve a public-relations purpose. Take a look at OpenBSD's recent release, http://www.openbsd.org/35.html. The "What's New" section of that page is fairly extensive, and distrowatch and other news sites have provided OpenBSD with a fair amount of coverage about their new release. = =20 Even if we maintain a calendar-based release system, should we also be striving to make releases goal-oriented as well? If so, how do we go about doing so? Some thoughts, g2boojum ----- Forwarded message from Aron Griffis ----- =46rom: Aron Griffis Date: Mon, 10 May 2004 14:48:25 -0400 To: gentoo-releng@lists.gentoo.org User-Agent: Mutt/1.5.6i Subject: Re: [gentoo-releng] Meeting time Hi Jon, ZhEN wrote: [Mon May 10 2004, 10:53:19AM EDT] > Please find attached the compiled list of features that I fielded > from -dev, -core, and personal e-mails.=20 My perception of the current release process is this: We set a date for release. Developers work on features. Whatever is done in time for the release is what goes in, the other stuff waits for the next release. IMHO, part of the point of doing more frequent releases is to ease pressure from developers; if we can't finish a given feature, then we know there will be another release in 3 months, so it's okay. So I don't understand this list of potential features for 2004.2. Shouldn't this be maintained separately from the release process? Why is releng meeting to talk about this list? Regards, Aron -- Aron Griffis Gentoo Linux Developer (alpha / baselayout / ia64 / mozilla / mutt / ruby /= vim) ----- End forwarded message ----- --=20 Grant Goodyear=09 Gentoo Developer g2boojum@gentoo.org http://www.gentoo.org/~g2boojum GPG Fingerprint: D706 9802 1663 DEF5 81B0 9573 A6DC 7152 E0F6 5B76 --qcHopEYAB45HaUaB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFApQlnptxxUuD2W3YRAs7XAJ9nN4PWS6JrlbZ2ZwBW+M78sdwtJACfXyWq NwA7MPiGmJaR10ollwA5MJ8= =ZRCr -----END PGP SIGNATURE----- --qcHopEYAB45HaUaB--