Folks,

I think right at this point we should fork discussion on methodology
(Git) from new features as in the rest of this thread.

Moving development to the Git infrastructure ASF / Infra now provides is
*not* a no-brainer, and it requires a little bit more than just a few +1s :)

Let's step back, hold breath, and dive into serious discussion about
that. I'm preparing a more detailed post, but here are some first links
worth reading as a primer on on this topic:

http://nvie.com/posts/a-successful-git-branching-model/
https://git-wip-us.apache.org
http://git.apache.org (list of our mirrored Git repos)

For a deep dive, feel free to read the one-stop Git reference this weekend:
http://git-scm.com/book/

- René

Am 22.11.12 09:11, schrieb Lukasz Lenart:
> Hi,
> 
> I've prepared a simple plan to start working on Struts 3 which is
> available here [1]
> 
> Request Git repo from INFRA
> Import project
> Remove deprecated plugins
> Remove deprecated APIs
> Switch to Java 1.6
> Rename XWork packages to org.apache.struts.xwork
> Rename Struts 2 packages to org.apache.struts ?
> Prepare the first release
> 
> [1] https://cwiki.apache.org/confluence/display/WW/Struts+3
> 
> 
> Regards
> 

-- 
René Gielen
http://twitter.com/rgielen

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

Reply via email to