Re: Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

Craig, So feature freeze and branch 2.0.x now, only fix reported bugs from beta tests and roll out the result as GA, while trunk moves on to 2.1.x, fully open for new features and whatever? IMO this would be the perfect way to go, you get a big +1 from me on this :) - Rene Craig McClanahan schri

DO NOT REPLY [Bug 31293] - javax.servlet.ServletException: Cannot find message resources under key org.apache.struts.action.MESSAGE

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

I'm with Don here - IMO, Struts 2.0.1 was been usable for the general public and the subsequent releases are all a result of Apache politics (or Mavenisms). ;-) Matt Ted Husted-3 wrote: > > On 2/6/07, Don Brown <[EMAIL PROTECTED]> wrote: >> I would love it if we actually did this. Unfortuna

Re: Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

On 2/6/07, Don Brown <[EMAIL PROTECTED]> wrote: Alexandru Popescu wrote: > I see two clear stages: > > - a product that is ready from developers point of view > - a product that gets its users acceptance > > An OSS project can take the same approach or not, and this is up to > its management. Ho

Re: Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

On 2/6/07, Don Brown <[EMAIL PROTECTED]> wrote: I would love it if we actually did this. Unfortunately, we don't do the second step, which is to have a scheduled period that allows fixes to go in if necessary. What we actually do is freeze the code in a test build, and put that through an undet

Re: Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

Alexandru Popescu wrote: I see two clear stages: - a product that is ready from developers point of view - a product that gets its users acceptance An OSS project can take the same approach or not, and this is up to its management. However, I feel that a project that would like to be widely use

Re: Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

On 2/6/07, Craig McClanahan <[EMAIL PROTECTED]> wrote: Isn't a feature of the current release practice that you could vote a particular x.y.z release as "beta" now, but later hold another vote to upgrade it to GA status later (i.e. without requiring another release)? Don's success with it is grea

Re: [VOTE] Struts 2.0.5 Quality

On 2/6/07, Rene Gielen <[EMAIL PROTECTED]> wrote: But if we throw out a GA now, we commit on a certain api stability which I doubt we can guarantee in nearest future. The "new API" is clearly marked experimental, and so I don't feel that we would be committing to anything. Worse case, we could

Re: Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

On 2/7/07, Craig McClanahan <[EMAIL PROTECTED]> wrote: On 2/6/07, Don Brown <[EMAIL PROTECTED]> wrote: > > Well, two comments here. First, how many beta releases do we need > before it is time for a GA? I think we've been at beta quality since > 2.0.1 and, yes, it has been helpful to weed out i

Re: [VOTE] Struts 2.0.5 Quality

I fully agree with Ted's explanation of vote meanings so [ ] Leave at test build [ ] Alpha [ x] Beta [ ] General Availability (GA) ./alex -- .w( the_mindstorm )p. On 2/7/07, Ted Husted <[EMAIL PROTECTED]> wrote: We might have to agree to disagree. I believe a beta vote is warranted when

Re: [VOTE] Struts 2.0.5 Quality

I'm going to do more testing this week, but I think (fear?) I have a first opinion so far: > [ ] Leave at test build > [ ] Alpha > [ x] Beta > [ ] General Availability (GA) Especially, I think we're not at GA level, because I have already two concerns preventing me from seeing the required lev

Re: Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

On 2/6/07, Don Brown <[EMAIL PROTECTED]> wrote: Well, two comments here. First, how many beta releases do we need before it is time for a GA? I think we've been at beta quality since 2.0.1 and, yes, it has been helpful to weed out issues, but now with several large applications running Struts

Struts Release Process (again) (was [VOTE] Struts 2.0.5 Quality)

Well, two comments here. First, how many beta releases do we need before it is time for a GA? I think we've been at beta quality since 2.0.1 and, yes, it has been helpful to weed out issues, but now with several large applications running Struts 2 and no significant issues in JIRA, I think we

Re: [VOTE] Struts 2.0.5 Quality

We might have to agree to disagree. I believe a beta vote is warranted when someone believes the code is ready for testing outside of the development group. Personally, I am not in favor of passing a set of bits straight to GA without a beta cycle, especially when a release series hasn't seen a GA

Re: [VOTE] Struts 2.0.5 Quality

I disagree; you shouldn't vote beta just because you haven't ran the code in production. A beta vote should be reserved for the case where you don't believe the quality is at the level of a GA release, and there should be specific issues you can point to that you feel need to be resolved first

Re: [VOTE] Struts 2.0.5 Quality

Beta is also an option :) On 2/6/07, Ian Roughley <[EMAIL PROTECTED]> wrote: +0 for GA. I have some testing code that looks good, but no production code that has been converted. /Ian - To unsubscribe, e-mail: [EMAIL PROTECTE

Re: [VOTE] Struts 2.0.5 Quality

+0 for GA. I have some testing code that looks good, but no production code that has been converted. /Ian Ted Husted wrote: The Struts 2.0.5 test build is now available. Release notes: * http://struts.apache.org/2.x/docs/release-notes-205.html Distribution: * http://people.apache.org/builds

Re: [VOTE] Struts 2.0.5 Quality

+1 for GA - I'm using it in HostedQA now and it is working great. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=62617&messageID=121464#121464

including files in struts.xml

Hi all! First of all I would like to say hello to the list - it's my first mail here :) Yesterday I've began migrating my app from WebWork to Struts2. Everything was quite easy except including other action files in struts.xml. I've encountered same issue as Matt Finholt who has reported it as c

Re: [VOTE] Struts 2.0.5 Quality

Ted Husted-3 wrote: > > The Struts 2.0.5 test build is now available. > > Release notes: > * http://struts.apache.org/2.x/docs/release-notes-205.html > > Distribution: > * http://people.apache.org/builds/struts/2.0.5/ > > Maven 2 staging repository: > * http://people.apache.org/builds/struts