From owner-freebsd-hackers Sat Jul 29 07:07:40 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id HAA20884 for hackers-outgoing; Sat, 29 Jul 1995 07:07:40 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id HAA20878 for ; Sat, 29 Jul 1995 07:07:35 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id PAA06144; Sat, 29 Jul 1995 15:03:35 +0100 From: Paul Richards Message-Id: <199507291403.PAA06144@server.netcraft.co.uk> Subject: Re: New 2.1.0-950726-SNAP available - come 'n get it! To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Sat, 29 Jul 1995 15:03:33 +0100 (BST) Cc: jcargill@cs.wisc.edu, jkh@time.cdrom.com, hackers@FreeBSD.org In-Reply-To: <199507280319.UAA02225@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jul 27, 95 08:19:14 pm Reply-to: paul@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1660 Sender: hackers-owner@FreeBSD.org Precedence: bulk In reply to Rodney W. Grimes who said > > Names (if Jordan agrees with the proposal) will become: > X.Y-BRANCH: > These are -current versions of the branch, and > BRANCH currently has the values ``STABLE'' or ``CURRENT''. > > X.Y-BRANCH-SNAPMMDDYY: > This is a snap shot on MMDDYY of one of the branches, > it is turned on by a release engineering during snap > shot building. Only the MMDDYY part is provided (and > the change with use "`date`" to get that.) > > X.Y-RELEASE: > This is a release, this requires a commit to build > a proper release src tree so that things built with > that src tree also say ``RELEASE''. This will appear > briefly at the end of a -stable branch as the release > is merged and such before -STABLE rolls up to the > next version and all the numbers get bumped by the > person doing the cvs ops such as tree tagging. [Humm.. > perhaps the branch should be called ``STABALIZING'' :-)] >From a gnats point of view there's a few things I'd like to see. If there's a unique release name then we can segragate reports in the database on a per-release basis. This would include alpha and beta releases so when we finally adopt a proper release process those who have alpha or beta copies will have the PR's labelled as such and we can look up just bug reports for any particular cycle of a release. Gnats is currently very broken in this respect because releases go out the door without the send-pr version getting bumped. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home)