I agree with respecting major/minor versions concerning breaking changes. I also encountered an unexpected problem with updating one of our projects at work to 2.5.10.1 (from 2.5.1), which didn’t even cause a compilation error.
In my case it was because of the introduction of a parameter object. (Google recaptcha parameter contains ’-’ => required manual fetching inside validator) Regards, Stefaan Dutry (sdutry) Op 16-mrt.-2017 20:23 schreef "Aaron Johnson" <johnson.aar...@gmail.com>: Keeping breaking changes in major releases is important. I recently took a project from 2.5.8 to 2.5.10.1 and had several compilation errors. Not a good surprise when attempting to get a security fix in quickly. On Thu, Mar 16, 2017 at 8:35 AM, Lukasz Lenart <lukaszlen...@apache.org> wrote: > 2017-03-16 13:21 GMT+01:00 Christoph Nenning < > christoph.nenn...@lex-com.net>: > > I'd say it is too big for a minor version update -> let's put it in 2.6 > > https://issues.apache.org/jira/issues/?jql=fixVersion% > 20%3D%202.6%20AND%20project%20%3D%20WW%20AND%20resolution% > 20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
