Date: Thu, 11 Sep 2003 01:41:05 +0200 From: Michael Nottebrock <michaelnottebrock@gmx.net> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@FreeBSD.org Subject: Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility) Message-ID: <3F5FB691.3040403@gmx.net> In-Reply-To: <20030910165645.GA2839@troutmask.apl.washington.edu> References: <3F5F2774.9010408@gmx.net> <20030910144620.GA2438@troutmask.apl.washington.edu> <3F5F420B.5030202@gmx.net> <20030910165645.GA2839@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote:
> Why? The portmgr can tag the ports collection at any point in
> time before or after the -pthread deprecation date.
Steve, ports-freeze dates are set and published ahead of time just as dates
for releases are. It's obviously not a good thing to have to try and be very
conservative with commits to ports (in order to have a maximum number of them
working for the next 4.x release) while at the same time there is loud demand
for fixing a big number of them for -CURRENT.
Don't bother telling me I'm whining, pointing at the handbook again and saying
"don't expect anything to work on -CURRENT at any given time", you're shooting
the messenger.
--
,_, | Michael Nottebrock | lofi@freebsd.org
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F5FB691.3040403>