As this a major change, a formal vote might be a valid option.
Am 12.09.2013 11:26 schrieb "Lukasz Lenart" :
> Can we go live?
>
> 2013/9/11 Lukasz Lenart :
> > I think we can go live with the new website even now - it looks much
> > better the old one and the rest can be improved in meantime.
>
+1 for git flow as the way to go, including excellent tooling - command
line extensions, Atlassian Sourcetree support and even a IDEA plugin
(https://github.com/OpherV/gitflow4idea) help to make this an elegant
abstract and reliable workflow.
-1 for moving trunk only. We don't want to lose history
2013/9/12 Johannes Geppert :
> +1 for starting with the Git migration process.
>
> What about only migrating the current svn struts2/trunk to git and leave
> the rest in the svn repository?
>
> If we need sometime also the site in git we can request a separate git
> repository like struts-site.git.
2013/9/12 Dale Newfield :
> On Sep 12, 2013, at 11:34 AM, Ken McWilliams wrote:
>> prefix, IE: "OGNL:" or "EL:
>
> I've long argued that %{}, #{}, ${} provides this already, and that this
> wrapping should therefore not be optional in preparation for when something
> other than %{} might be func
There should be a default EL (OGNL) for backward compatibility. Any IDE
will show you API breakage changes but none of them will pickup changes to
tag string requirements changes in the JSPs!
It's probably a good idea to force the user to explicitly state the default
in struts.xml but such an optio
Where can I see the "new" website before it goes live?
On Fri, Sep 13, 2013 at 2:22 AM, Rene Gielen wrote:
> As this a major change, a formal vote might be a valid option.
> Am 12.09.2013 11:26 schrieb "Lukasz Lenart" :
>
> > Can we go live?
> >
> > 2013/9/11 Lukasz Lenart :
> > > I think we c
http://struts.staging.apache.org/
Am 13.09.2013 18:35 schrieb "Paul Benedict" :
> Where can I see the "new" website before it goes live?
>
>
> On Fri, Sep 13, 2013 at 2:22 AM, Rene Gielen
> wrote:
>
> > As this a major change, a formal vote might be a valid option.
> > Am 12.09.2013 11:26 schrie
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 struts 2 scm repo tree, thus working in
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.
Brian
>>> Rene Gielen 13/09/2013 11:22 AM >>>
http://struts.staging.apache.org/
