Antonio Petrelli schrieb: > 2008/2/12, Rene Gielen <[EMAIL PROTECTED]>: >> Even if we would never opt for rolling out a 2.0.12, it still makes sense >> to mark patches done to the 2.0.x code tree in Jira. For example, as long >> as I have customers working on 2.0.x, I will commit on both the 2.1 and >> 2.0 branch if I see a sense in it. > > Struts (as the other Apache projects) is not customer-driven, but > community driven.
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... > 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. >> Tagging them as fixed in both branches' >> next unreleased version is the only way to keep track then about the >> actual changes made between two 2.0 versions - just in case the would be >> another one. > > IMHO tagging as fixed in two branches should be done only in > exceptional cases (for example, security issues). > 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. And, again, 2.1.x is definitely not a drop in replacement, as I for myself had to realize for a bigger project - the upgrade was cancelled then. WebWork gives a good impression on how many minor releases a "dead" project or project tree can still have. 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. >> and some security issues might be raised requiring >> us to roll out a GA fix > > In this case, will roll a 2.0.11.1 version, as discussed earlier: > http://cwiki.apache.org/WW/creating-and-signing-a-distribution.html#CreatingandSigningaDistribution-FastTrackinganImportantSecurityRelease > > Ciao > Antonio > > --------------------------------------------------------------------- > 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]
