From owner-freebsd-current Sun Jul 9 11:15:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA05083 for current-outgoing; Sun, 9 Jul 1995 11:15:59 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA05077 for ; Sun, 9 Jul 1995 11:15:53 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id LAA09446; Sun, 9 Jul 1995 11:15:38 -0700 From: "Rodney W. Grimes" Message-Id: <199507091815.LAA09446@gndrsh.aac.dev.com> Subject: Re: Version numbers of the different branches? To: phk@freefall.cdrom.com (Poul-Henning Kamp) Date: Sun, 9 Jul 1995 11:15:38 -0700 (PDT) Cc: roberto@blaise.ibp.fr, peter@haywire.dialix.com, freebsd-current@freebsd.org In-Reply-To: <199507091327.GAA29319@freefall.cdrom.com> from "Poul-Henning Kamp" at Jul 9, 95 06:27:35 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1757 Sender: current-owner@freebsd.org Precedence: bulk > > > > How about making it either "2.2-BUILT-xxxxxx" or "2.X-BUILT-xxxxx" or > > > even "2.X-CURRENT-xxxxxx". > > > > > > > We should revert to something like it was before e.g. 2.2-Development. > > Putting the build date is not really informative because it gives > > no insight about the date of the files themselves... > > > > You can tell that the files are older than a particular date, that > is very useful. > > ("BUILT-950703" ? Hey, He hasn't got the "ls -s panic" patch that > got comitted on july 5th !) That may be true, but you surely can not say that he has all patches applied up to 950703 by that string, as he may have built it from 950301 sources... Any way I would like to have this small bit of confusing mess cleaned up and propose the following changes based on my understanding of why things are the way they are. The release folks wanted the SNAP shots to go out with a reasonable date in the snap shot that was done automagically is my understanding of the sole reason this was _really_ ever added. I propose that the release Makefile be modified to _require_ either a RELEASE=value or SNAP=value that is used in constructing a string of the form ``X.Y-RELEASE-`date`'' or ``X.Y-SNAP-`date`''. Without the pass in override the string should be ``X.Y-DEVELOPEMENT'', no date as the date of the build here is pretty darn meaningless. Ie, this applies when building from /usr/src/Makefile and not /usr/src- /release/Makefile. The value X.Y will be set to 2.0.6, 2.1, and 2.2 in the respective branches of the CVS tree (too late to set a 2.0.5 one :-(). Comments? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD