Date: Mon, 27 Oct 1997 03:01:41 -0800 (PST) From: asami@cs.berkeley.edu (Satoshi Asami) To: peter@netplex.com.au Cc: jkh@freebsd.org, cvs-committers@freebsd.org, cvs-all@freebsd.org, cvs-sys@freebsd.org Subject: Re: cvs commit: src/sys/conf newvers.sh Message-ID: <199710271101.DAA01982@bubble.didi.com> In-Reply-To: <199710261412.WAA09524@spinner.netplex.com.au> (message from Peter Wemm on Sun, 26 Oct 1997 22:12:32 %2B0800)
next in thread | previous in thread | raw e-mail | index | archive | help
* 3.0-CURRENT won't exist beyond 3.0-RELEASE.. At some point I assume the * tree will branch, RELENG_3_0 will become 3.0-STABLE (on which * 3.0[.*]-RELEASE will happen), and HEAD will become 3.1-CURRENT or * something. So, there won't be a 3.0-CURRENT after 3.0-STABLE begins. I don't think so. I don't think DavidG will agree with that either. :) * So, how do we tell the difference between 3.0-STABLE before and after * 3.0-RELEASE? Damn good question, unless it becomes 3.0.0-STABLE or * 3.0.1-STABLE depending on how many aborted releases there are... :-] (can * you say 2.2.1? :-) As you say yourself above, this is just moving the problem from one place to another. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710271101.DAA01982>