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. 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. > 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). > 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]
