Thanks for the feedback - I was thinking the release candidate would be out there for review for at least a week or two and then if it all looked good the usual +72hr on whether it should be released or not.
One other point - once the RC was cut I was planning on announcing it on the Struts User list - to hopefully get as many people as possible to try it out. Does anyone object to that? Niall ----- Original Message ----- From: "Henri Yandell" <[EMAIL PROTECTED]> Sent: Friday, March 10, 2006 4:38 AM 72 hours seems to be the general ASF minimum time for replies on important issues - so I'd apply 72 hours minimum for the actual release - however as an RC is still quite vetoable later on, I don't think there's any reason to hold yourself back when there have been no negative replies. Hen On 3/9/06, Niall Pemberton <[EMAIL PROTECTED]> wrote: > I've just had a look at the release guidelines and I'm wondering if theres > any convention on how long to wait before cutting a release candidate, after > announcing the intention to do so, since the guide doesn't indicate it? > > I'm planning to cut a Validator 1.2.1 RC - which I announced in an email on > this list approx 36 hours ago and I'd like to get on with it. Appreciate it > if anyone could clarify this - since its not my intention to upset anyone by > not allowing enough time for other peoples input. > > Niall > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
