2.5 => 3.0 (was Re: @StringLengthFieldValidator for 2.5)

[Paul Benedict <pb...@apache.org>]

I began to recently wonder if 2.5 should really be called 3.0. When we
originally had the discussion, I advocated going to 2.5 to show
maturity but also because the current versioning was far away
(probably 2.1 was out then). I also probably didn't realize if any of
the changes would be major.

Well, I change my mind based on what I saw with the Maven 3.0 release.
Maven 3 had the theme of "Maven 2 done right", which was all about
fixing the inconsistencies in the software for a better user and
development experience. I advocate that approach now. It would be a
bit surprising to jump from 2.3 and 2.5 and find massive
incompatibilities. I'd rather us take a "Struts 2 done right" approach
for 3.0, do all the cleanup we need, and produce a new polished major
version.

Thoughts?

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: 2.5 => 3.0 (was Re: @StringLengthFieldValidator for 2.5)

[Łukasz Lenart <lu...@gmail.com>]

2012/7/27 Paul Benedict <pb...@apache.org>:
> Thoughts?

With 3.0 we must clean up the whole code base, rename packages, remove
obsolete classes and methods and move Convention into Core and so on.
With 2.5 we could do some less user harming things like remove some
plugins, some classes and methods and leave the rest for 3.0.

So maybe instead 2.5 either 3.0 we should have 2.5 and 3.0 after all.
So do it step by step.


Regards
-- 
Łukasz
mobile +48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org