As much as I agree with your sentiment (about us eating what we cook), it's decidedly easier for some of us to actually stay bleeding edge than others.

Whatever I do at home may be bleeding edge, but once I step in the office ... well, I haven't pushed very hard for bleeding edge, but I'd like to acquire a bit more tenure at my current position before I try to "agressively encourage" usage of bleeding-edge stuff -- irrespective of the amount of faith I have in it.

----- Original Message ----- From: "Ted Husted" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Monday, October 25, 2004 12:30 PM
Subject: Re: When is a release ready for primetime (was [VOTE] HTTPD ...)



On Mon, 25 Oct 2004 09:05:10 -0500, Joe Germuska wrote:

What I do think we've been doing wrong is rushing to vote on a release right after it is cut. As I noted before, from the framework we've laid out, I would consider it totally normal for us to change (upward) the status of a release from test/alpha to beta to GA. In fact, I might even say that once we verify that a release is not fundamentally flawed, we should have a mandatory cooling off period before it would be appropriate to make a vote.

Something that is mentioned in the HTTP guidelines is that before certifying a release GA, "... the group has liked to see approximately 48-72 hours of usage in production to certify that the release is functional in the real world."


Personally, I think this would be a good guideline for PMC members to follow. If you vote +1 for GA, it should imply that you are already using the distribution in production yourself, and have done so for several business days. Of course, a +1 also implies that you will support the release, as always.

If we don't have the courage to use a distribution in our own work, then we should not be advising others to do the same :)

-Ted.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--- avast! Antivirus: Outbound message clean. Virus Database (VPS): 0443-3, 10/22/2004 Tested on: 10/25/2004 6:51:28 PM avast! - copyright (c) 2000-2004 ALWIL Software. http://www.avast.com




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to