2008/2/12, Rene Gielen <[EMAIL PROTECTED]>: > Antonio Petrelli schrieb: > > 2008/2/12, Rene Gielen <[EMAIL PROTECTED]>: > I'm not sure if I get you right here - are commercial efforts evil? Are > we not telling commercial as well as non-commercial users that Struts2 > let's you build mature application? Isn't a commercial company sometimes > good for paying some time of all day bug fixing? Don't we believe that > someone using Struts2 in real life applications is good for finding real > life bugs a framework developer would sometimes never realise? I am very > happy to be able to use S2 sometimes in my day jobs, and when I do I > still learn new aspects all the time. Some of this aspects may be useful > for others, too...
Sorry, I did not mean this. I meant that customer (or better, users) may "ask" for features/bug fixing, but it will be fixed only if there is a developer willing to do the work. Anyway, it's nice to hear that there is *finally* a paid Struts developer (TED where are you???) :-) > > So, as long as there is a community interest (i.e. active developers > > and contributors) in letting the 2.0.x branch to "survive", I agree > > that you can commit in the branch. > > > > As long someone volunteers support issues for both trees, and volunteers > to patch for both trees, I think there _is_ community interest, given > you regard him as a community member. Basically, this is to volunteer to > do a little bit more work than just to patch, test and commit to one branch. But the release process must be voted by the PMC members. If there is not a large consensus, your effort of merging bug fixes will be somewhat void. This does not mean that I will vote against it ;-) > 2.0.x is still the only S2 GA branch. For that reason, I find it quite > unusual to close it down before a 2.1.x is out. +1. In fact the switch seems too fast to me. Probably we should wait until Ted comes back, to answer the reason for switching so fast. > And again, being able to tag a fix for a 2.0.12 does not mean we have to > roll a out a 2.0.12. But in case there is someone standing up to do so, > this can help him. I disagree, fixing in the 2.0.x means that we *hope* to tag a release in that branch. Finally, Rene, you cannot rename the 2.1.2 back to 2.0.12, but, IMO, you could create a new 2.0.12 version and add the "fix for" tag to the candidate issues in JIRA, to help us understand how much work is needed. And, if you are willing to merge the fixes, you are free to do it, since it won't harm anyone :-) Ciao Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
