Subject: Re: SUP/FTP tree of NetBSD-current/-release will switch on Dec 15
To: None <firstname.lastname@example.org>
From: John Darrow <John.P.Darrow@wheaton.edu>
Date: 12/13/2000 18:54:36
Noriyuki Soda <email@example.com> wrote:
>On December 15, the NetBSD-current tree of NetBSD SUP/FTP server will
>switch from NetBSD-1.5 release branch to main trunk, and the
>NetBSD-release tree will switch from NetBSD-1.4 release branch to
>NetBSD-1.5 release branch.
>In other words, after December 15,
>- if you SUP NetBSD-current, you will get NetBSD-1.5N (or something)
>- if you SUP NetBSD-release, you will get NetBSD-1.5.1_ALPHA
I'd like to add my voice to the chorus requesting that the 'release'
collection be left as-is, pointing to the netbsd-1-4 branch, and a new
'release-1-5' (or some similar name) collection be created for the
netbsd-1-5 branch. As was earlier hashed out on this list in the thread
"Re: CVS commit: syssrc [netbsd-1-5]" (starting with my message saved as
there are going to be multiple release branches being maintained at
once, even as the 1.4 and 1.5 branches were both receiving pullups at
the same time.
In fact, just earlier today, some additional pullups were made to the
netbsd-1-4 branch, including a conversion of the version number to
NetBSD-1.4.3A (indicating post-1.4.3 development)! While this doesn't
guarantee that a NetBSD-1.4.4 will be released, it does indicate that
there is still life on the branch...
I have no objections to reverting the 'current' collection to true
-current. But please don't modify -release.
(I also think it would be good to create an additional collection name
'release-1-4' and to encourage 1.4.x users to use that name, eventually
obsoleting the unnumbered 'release' collection. This shouldn't require
any additional disk space, or at most enough for a few index files - just
point them to the same actual tree as the current 'release'...)
John Darrow - Senior Technical Specialist Office: 630/752-5201
Computing Services, Wheaton College, Wheaton, IL 60187 Fax: 630/752-5968
Alphapage: firstname.lastname@example.org Pager: 630/316-0707