Agreed on releasing 2.0.10 as beta first. My suggestion is to release using the normal process of beta, vote, etc. Sorry if there was any confusion in my intent in the original email.
As far as the security fix, I agree as well on 2nd thought. Making a 2.0.9.1 is probably best so that we don't have any beta issues hanging us up. Sent via BlackBerry. -----Original Message----- From: "Rene Gielen" <[EMAIL PROTECTED]> Date: Tue, 14 Aug 2007 17:29:50 To:dev@struts.apache.org Subject: Re: [s2] 2.0.10 release - when? James, see comments below: Am Di, 14.08.2007, 15:20, schrieb James Holmes: > Since the 2.0.X releases are small point releases, I'm all for releasing 2.0.10 > soon. I'd like to see a regular schedule for these releases so we can keep fixing > the minor issues and getting these fixes out to the users. This will help Struts > 2 attract new users. It seems 2.1 is still a ways out (although I'd like to see > us put some scope around that and make a rough estimate of a goal when we'd like > to get it out). > > My vote is to release 2.0.10 with the WW-2107 security fix instead of doing a > special security fix release. I think we can wait the normal 72 hours that a > "regular" release requires. > > Thoughts? > The normal cycle would be to make a 2.0.10 beta release first and do normal voting, and I think we should keep this. Although I think we should be close to a 2.0.10 beta and would be good to push this out soon, IMO the security fix should follow the 2.0.9.1 versioning _only_ containing the fix. > That said, we need a release manager. I'm happy to work on bugs, but don't have > time to pour into learning all of the release steps and setting up the required > infrastructure on my machine right now. > (Hopefully) I should have a little more time the next few days, so I would volunteer to do this. Needless to say I never did this before and I will most probably dependent on someone holding my hands from time to time :) Regards, Rene --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
