You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Yasser Zamani <ya...@apache.org> on 2017/12/12 14:08:06 UTC
Re: Struts 2.6
> On 11/27/2017 2:22 PM, Lukasz Lenart wrote:
>> Struts 2.5.14 is officially out so we can start working on Struts 2.6 :)
>>
>> I think we can basically merge all the open PRs, adjust Servlet API
>> version and release a first beta version :)
>> https://github.com/apache/struts/pulls
>>
On 11/17/2017 3:46 PM, René Gielen wrote: [1]
> +1 - not again - please don't use "Servlet 3" in any name. "Async" is the asset, so let's name it like that
> It's also valid for Servlet 4.0, isn't it? :) We should better stay with features than with version numbers, we had this problem already with adding the 2 to the product brand name (Struts 2) - will a 3.0 release called Struts 3 or Struts 2 3.x ?? Same goes for Servlet versioning. So I'm still +1 for a refactoring
I am wondering why we don't solve this one time for ever in 2.6 major
version? In technical point-of-view we can simply refactor all Struts 2
to Struts and then just preparing a migration guide.
I know there are maybe a lot of works and side effects but they will be
finished one they and the world will forget, I think. What do you think?
Regards.
[1] https://github.com/apache/struts/pull/179#issuecomment-345228928
Re: Struts 2.6
Posted by Lukasz Lenart <lu...@apache.org>.
2017-12-13 9:52 GMT+01:00 Yasser Zamani <ya...@apache.org>:
> On 12/13/2017 10:33 AM, Lukasz Lenart wrote:
>> I think we should create a branch (support-2-5) to continue support of
>> 2.5.x series in there and use master to work on 2.6 version. I expect
>> there will be a small 2.5.15 release soon as some issues were reported
>> but we should focus on 2.6 now.
>
> As so far, we don't have any committed change into master for 2.6, maybe
> we can wait, then when 2.6 related change was needed to being committed
> into master, then we make a fast release for 2.5.15, goto 2.6 and commit
> that change; If additional issues reported then we have to make a branch
> from 2.5.15 tag.
Works for me :)
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: Struts 2.6
Posted by Yasser Zamani <ya...@apache.org>.
On 12/13/2017 10:33 AM, Lukasz Lenart wrote:
> I think we should create a branch (support-2-5) to continue support of
> 2.5.x series in there and use master to work on 2.6 version. I expect
> there will be a small 2.5.15 release soon as some issues were reported
> but we should focus on 2.6 now.
As so far, we don't have any committed change into master for 2.6, maybe
we can wait, then when 2.6 related change was needed to being committed
into master, then we make a fast release for 2.5.15, goto 2.6 and commit
that change; If additional issues reported then we have to make a branch
from 2.5.15 tag.
Regards.
Re: Struts 2.6
Posted by Lukasz Lenart <lu...@apache.org>.
Hi,
I think we should create a branch (support-2-5) to continue support of
2.5.x series in there and use master to work on 2.6 version. I expect
there will be a small 2.5.15 release soon as some issues were reported
but we should focus on 2.6 now.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2017-12-12 15:17 GMT+01:00 Lukasz Lenart <lu...@apache.org>:
> 2017-12-12 15:08 GMT+01:00 Yasser Zamani <ya...@apache.org>:
>> I am wondering why we don't solve this one time for ever in 2.6 major
>> version? In technical point-of-view we can simply refactor all Struts 2
>> to Struts and then just preparing a migration guide.
>>
>> I know there are maybe a lot of works and side effects but they will be
>> finished one they and the world will forget, I think. What do you think?
>
> This isn't about package names - this is even a good idea to have
> different package names as then you can have Struts 1 and Struts 2 in
> the same war file and allow step by step migration.
>
>
> 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: Struts 2.6
Posted by Lukasz Lenart <lu...@apache.org>.
2017-12-12 15:08 GMT+01:00 Yasser Zamani <ya...@apache.org>:
> I am wondering why we don't solve this one time for ever in 2.6 major
> version? In technical point-of-view we can simply refactor all Struts 2
> to Struts and then just preparing a migration guide.
>
> I know there are maybe a lot of works and side effects but they will be
> finished one they and the world will forget, I think. What do you think?
This isn't about package names - this is even a good idea to have
different package names as then you can have Struts 1 and Struts 2 in
the same war file and allow step by step migration.
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