struts-site migrated
https://git-wip-us.apache.org/repos/asf?p=struts-site.git
2014-12-13 9:43 GMT+01:00 Lukasz Lenart :
> Right now I'm waiting for INFRA to create a new Git project -
> struts-archive - to allow move deprecated plugins to it. Also I want
> to give enough time for people to migra
Right now I'm waiting for INFRA to create a new Git project -
struts-archive - to allow move deprecated plugins to it. Also I want
to give enough time for people to migrate to 2.3.20 and to see if
there any major problems which should be addressed with another 2.3.x
version or we're safe to start w
2014-11-20 15:56 GMT+01:00 Paul Benedict :
> I agree with the step by step approach. With GIT, each step can be a
> deveopment branch. It wouldn't make sense for all us all to do major
> refactoring in one branch. We need to lay out milestones on the wiki and
> merge in our work to the official str
I agree with the step by step approach. With GIT, each step can be a
deveopment branch. It wouldn't make sense for all us all to do major
refactoring in one branch. We need to lay out milestones on the wiki and
merge in our work to the official struts3 branch when ready.
Cheers,
Paul
On Thu, Nov
Hi,
I'm not against but I think you took 2.5 too literally ;-) Basically
we can merge plans for 2.5 and 3.0 and start coding. But even with
directly targeting 3.0 we still have to resolve a lot of code
unrelated issues - where to move deprecated plugins (and how without
losing history of commits)?
I hope Lukasz agrees. First order of business for me is updating the
package name to struts3 and updating the POM versions.
Cheers,
Paul
On Wed, Nov 19, 2014 at 12:32 PM, Dave Newton wrote:
> I'm good with this, although I'm struggling to find time for anything
> these days.
>
> I'd like to do
I'm good with this, although I'm struggling to find time for anything
these days.
I'd like to do some refactoring of several things, primarily for readability.
On Wed, Nov 19, 2014 at 1:20 PM, Johannes Geppert wrote:
> Hi,
>
> what you all think about starting with Struts3 and creating a brunch
Hi,
what you all think about starting with Struts3 and creating a brunch
directly after next 2.3.x release and create only maintenance releases for
Struts 2.3.
I personal think we should skip plans for 2.5 [1] and better concentrate on
creating a new major release.
Best Regards
Johannes
[1] h
