Date: Mon, 11 Jun 2001 17:44:34 -0500 From: David McNett <nugget@slacker.com> To: Jordan Hubbard <jkh@osd.bsdi.com> Cc: mixtim@home.com, rjackson@cs.csubak.edu, stable@FreeBSD.ORG Subject: Re: Why is the STABLE branch not so stable anymore? Message-ID: <20010611174434.A16013@dazed.slacker.com> In-Reply-To: <20010611153217J.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Mon, Jun 11, 2001 at 03:32:17PM -0700 References: <3B25405D.2090209@cs.csubak.edu> <20010611150838X.jkh@osd.bsdi.com> <20010611181632.A19118@home.com> <20010611153217J.jkh@osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11-Jun-2001, Jordan Hubbard wrote:
> Hmmm. It seems like this thread has degraded to simple
> project-bashing so I'll not be a party to keeping it on life support
> any longer.
I don't think this is the case at all. For whatever it's worth, it
doesn't appear that the stability of -stable is the same priority it
used to be. It's hardly project-bashing to raise concerns of this
nature on the -stable mailing list.
> Suffice it to say that people make mistakes and of far
> greater importance is whether or not they realize it when they do and
> correct those mistakes. The pam/ssh suckage was backed out by Mark,
> with profuse apologies for his mistake, and the rest of the reports
> we've already covered so I think we can just let that rest.
The fact is, Mark's back-out of his earlier libpam commit created a
brand-new breakage. It's not even a complicated or esoteric problem,
a simple "make clean" on a fresh cvsup fails. I'm quite appreciative
that Mark has been responsive to my emails and others to the list, but
I'm frustrated that it took six hours and at least that many users to
detect an error which should have been spotted prior to being committed.
> In fact, users in your category are always recommended to stick with
> the releases and not upgrade until a new one comes out so I'm not
> even sure why we're having this conversation in the first place.
Exactly what category of user am I? According to the handbook:
"If you are a commercial user or someone who puts maximum stability
of their FreeBSD system before all other concerns, you should
consider tracking FreeBSD-STABLE."
From my perspective, as a commercial user who puts the maximum stability
of my freebsd systems before all other concerns, the level of respect and
forethought being put into -stable commits is not at the same level it
has traditionally been.
This isn't project bashing so much as it is a plea to the freebsd core
team to be mindful of what "stable" means to those of us out here in the
userbase.
--
________________________________________________________________________
|David McNett |To ensure privacy and data integrity this message has|
|nugget@slacker.com|been encrypted using dual rounds of ROT-13 encryption|
|Austin, TX USA |Please encrypt all important correspondence with PGP!|
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010611174434.A16013>