For the Documentation menu items why not use Struts 2 and Struts 1 as menu
choices instead of Struts 2.3.x and Struts 1.3.x. When we release Struts
2.4 we'll have to change those. The page those menu items link to (which
right now is not working) can specify the current version (e.g. 2.3.15.1).
On the main page of the new site:
We welcome your help! If you want to more about how to build and patch the
Struts 2 codebase, please read the Developer Docs
Should the above be:
We welcome your help! If you want to *learn *more about how to build and
patch the Struts 2 codebase, please read th
On Sat, Sep 14, 2013 at 11:13 AM, Lukasz Lenart wrote:
> Hi,
>
> Before moving to GIT I'd like to clean up struts2/branches. As already
> mentioned, most of them are fast-track release branches (branch from
> the latest tag), which suppose to be removed just after fast-track
> release process was
Hi,
Before moving to GIT I'd like to clean up struts2/branches. As already
mentioned, most of them are fast-track release branches (branch from
the latest tag), which suppose to be removed just after fast-track
release process was done.
This the list wit my comments
STRUTS_2_0_X/ - fast-track rel
2013/9/13 Rene Gielen :
> Lukasz,
>
> Please clarify - is it the idea to leave site, struts1 etc in San (agreed)
> or to move struts2/TRUNK *only*, that is not moving struts2/branches and
> struts2/tags? For the latter, I'm absolutely -1 - it's my strong opinion
> that we should move the full strut
2013/9/13 Rene Gielen :
> As this a major change, a formal vote might be a valid option.
I'd rather go with silence consensus here. Announcing Struts1 EOL
wasn't a big shock, there are still links to download the latest
version of it and to the archive site and to the EOL announcement
itself. All
2013/9/13 Brian Holzer :
> I checked out that staging site and one thing I found is that on the
> Documentation dropdown on the main page, the links to the Struts 2.3X
> and Struts 1.3X were both broken. Not sure that's what you were going
> for.
This is ok as those links are managed outside Apac