From owner-freebsd-hackers  Sun Apr  6 23:43:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA25880
          for hackers-outgoing; Sun, 6 Apr 1997 23:43:53 -0700 (PDT)
Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA25872
          for <hackers@freebsd.org>; Sun, 6 Apr 1997 23:43:49 -0700 (PDT)
Message-Id: <199704070643.XAA25872@freefall.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA259135089; Mon, 7 Apr 1997 16:38:09 +1000
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: on the subject of changes to -RELEASEs...
To: hackers@freebsd.org
Date: Mon, 7 Apr 1997 16:38:09 +1000 (EST)
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I've noticed some commits recently for RELENG_2_2 and as other have
commented, this changes (totally) a set of files for 2.2.1.

Can we have some sort of policy implemented so that revisions are
`automatically' made every 2 weeks (say0 if there have been any changes,
and each week, as part of the weekly update scripts, produce a list of
diffs from the last release in one file.

something like "cvs diff -r LATEST_2_2 src > ~ftp/freebsd/patch.level

that's got to be another nicety with linux.  you can update the kernel, you
don't need to configure sup/cvsup, etc.

it begs the question: if we're changing 2.2 after 2.2-RELEASE is made,
what does 2.2-RELEASE mean if my 2.2-RELEASE is different to yours ?

Does-RELEASE have any meaning any more ?

Should all FreeBSD just be a series of SNAPSHOTs ?

darren