+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. Johannes ################################################# web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2013/9/11 Lukasz Lenart <lukaszlen...@apache.org> > Hi, > > I'd like to start discussion about the migration process - there are > few things we must clarify, at least: > - Git structure > - development flow > > I think we should have just one repo: git.apache.org/struts.git and > diverse versions internally via branches - so the current S2 source > become the base and then we will transfer it to 2.5 and 3 in the > future. > > As a flow I like git-flow [1] - well known and used > > [1] https://github.com/nvie/gitflow > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > PS. It'll be implemented after cleaning up current pipeline :-) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
