ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!

[Marc G. Fournier]

This should be documented somewhere clearly then, as my understanding was 
that -STABLE meant that anything MFCd back to it *was* tested and deemed 
stable ... and yes, I do run stable, and yes, I do expect to hit the 
occasional 'oopses', but "blantant and obvious bugs due to insufficient 
testing", IMHO, doesn't classify as an 'oops' ....



On Sun, 10 Sep 2006, Mark Andrews wrote:

>
>> Yeah, -STABLE is what you should run if you want stable code, right?
>
> 	No. STABLE means STABLE API.
>
> 	If you want stable code you run releases.  Between releases
> 	stable can become unstable.  Think of stable as permanent
> 	BETA code.  Changes have passed the first level of testing
> 	in current which is permanent ALPHA code.
>
> 	Most of the time beta code is perfectly fine to run but
> 	occasionally things will go wrong.  The point of BETA code
> 	is to catch those errors that escape detection in the ALPHA
> 	stage before they make it into a release.  That is done by
> 	having a wider diversity of clients run the BETA code.
>
> 	Occasionally you have bugs that make it through both the ALPHA
> 	and BETA stages.
>
> 	Mark
> --
> ISC Training!  October 16-20, 2006, in the San Francisco Bay Area,
> covering topics from DNS to DHCP.  Email training at isc.org.
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email . scrappy at hub.org                              MSN . scrappy at hub.org
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664