Date: Mon, 07 Apr 1997 02:06:03 -0700 From: David Greenman <dg@root.com> To: Darren Reed <avalon@coombs.anu.edu.au> Cc: hackers@freebsd.org Subject: Re: on the subject of changes to -RELEASEs... Message-ID: <199704070906.CAA02532@root.com> In-Reply-To: Your message of "Mon, 07 Apr 1997 16:38:09 %2B1000." <199704070643.XAA25872@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>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 ? You don't understand how the tags work. The 2.2.1 release is tagged with a non-branch tag called RELENG_2_2_1_RELEASE. This tag will never be moved and you can't "commit" on a non-branch tag...so it will never change. If you check out the system with that tag, you'll get what went out in the release. The RELENG_2_2 tag is very different. It's the branch tag for the 2.2 tree. Changes for all 2.2 releases are made to this tag. When we're ready to make another release, we lay down another non-branch tag against that branch, which effectively takes a snapshot of it and freezes it. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704070906.CAA02532>