Re: Plan for Struts 3

[Lukasz Lenart <lu...@apache.org>]

Hi,

I have few additional thoughts about S3 and the future. First with
should drop support of S1 and use simple Struts as a project name - no
more Struts2, Struts3, Struts4, ... Simple Struts and version 3.0.1,
4.1.0.1, etc. We should just keep support for one version back, so
when we release 3.x, we should support just the latest version of 2.x
branch (and drop support for S1) - critical issues and security
vulnerabilities.

Versioning:
x.y.z.s
x - major API changes, breaks backward compatibility
y - minor API changes, can break backward compatibility (minor, one
method replaced other, should be simple to adopt)
z - maintenance, no API changes, no backward compatibility breaks
s - security release

With these two in mind we can more flexible handle changes and adopt
new requirements. Also website can be keep much clearer, just /current
and /previous ;-)


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

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

Re: Plan for Struts 3

[Lukasz Lenart <lu...@apache.org>]

2013/3/5 Paul Benedict <pb...@apache.org>:
> Question on the fourth version point: I don't think the four points plays
> all that nicely with maven. They are strictly 3 with anything else being a
> lexicographic ordering. I know we created the 4th point for emergency patch
> releases, but in practice, how is it any different than an emergency
> maintenance release? I don't see a need for the 4th specifier anymore.

I think it clearly says what the release means - you can see which one
is just a security release and which one is a normal maintenance
release. Just take a look on that page [1], without reading version
notes you know which one solves security holes.

[1] http://struts.apache.org/downloads.html#Prior_Releases


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

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

Re: Plan for Struts 3

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

I have no problem with dropping support for S1. :-)

Question on the fourth version point: I don't think the four points plays
all that nicely with maven. They are strictly 3 with anything else being a
lexicographic ordering. I know we created the 4th point for emergency patch
releases, but in practice, how is it any different than an emergency
maintenance release? I don't see a need for the 4th specifier anymore.

Paul

On Tue, Mar 5, 2013 at 2:22 PM, Lukasz Lenart <lu...@apache.org>wrote:

> Hi,
>
> I have few additional thoughts about S3 and the future. First with
> should drop support of S1 and use simple Struts as a project name - no
> more Struts2, Struts3, Struts4, ... Simple Struts and version 3.0.1,
> 4.1.0.1, etc. We should just keep support for one version back, so
> when we release 3.x, we should support just the latest version of 2.x
> branch (and drop support for S1) - critical issues and security
> vulnerabilities.
>
> Versioning:
> x.y.z.s
> x - major API changes, breaks backward compatibility
> y - minor API changes, can break backward compatibility (minor, one
> method replaced other, should be simple to adopt)
> z - maintenance, no API changes, no backward compatibility breaks
> s - security release
>
> With these two in mind we can more flexible handle changes and adopt
> new requirements. Also website can be keep much clearer, just /current
> and /previous ;-)
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>