This is an excellent question and part of the discussion I wanted to
start (but wasn't able to follow up so far in the last busy days)

Given that we decide for Git:

As for me, it makes absolutely no sense to have a common origin codebase
split up into two repositories. If we vote for developing S3 based on a
Git repository and workflow, we should move *the full* Struts 2
development to Git. Developing a new major version takes time, and we
will have to deal with a lot of commits that need to be ported from 2.x
to 3.x branch and vice versa. Having S3 in Git an S2 in subversion makes
absolutely no sense to me then.

What I don't see is moving the S1, site, maven etc. parts of our
Subversion repo. A good way to start planning for chainsawing is having
a look at our Git mirror repos at http://git.apache.org. Currently there
are 5 repos:

struts1.git
struts2.git
struts-sandbox.git
struts-maven.git
struts-site.git

For migrating current SVN repo content to Git, Infra prefers to
completely move an existing Git mirror repo. As I see it, we should
migrate struts2.git and arguably struts-sandbox.git and let the other
parts reside in SVN with Git morring only.

- René

Am 06.12.12 11:32, schrieb Christian Grobmeier:
> On Thu, Dec 6, 2012 at 11:13 AM, Lukasz Lenart <lukaszlen...@apache.org> 
> wrote:
>> 2012/11/28 Dave Newton <davelnew...@gmail.com>:
>>> On Wed, Nov 28, 2012 at 4:42 PM, Christian Grobmeier wrote:
>>>> http://nvie.com/posts/a-successful-git-branching-model/
>>>
>>> https://github.com/nvie/gitflow
>>>
>>> Yeah, I like the workflow quite a bit, although I've only used it on a
>>> couple of smallish projects.
>>
>> The idea looks pretty nice, as we don't have a Git repo yet, I'm going
>> to fork struts2 on the GitHub and try to play a bit - especially with
>> release process
> 
> Would be glad to look at your repos on github.
> 
> One question: are we going to fix issues in Struts 2.x on SVN or are
> we going to have everything on GIT then?
> In the git-brnaching-model link I see one development branch. I think
> we would need a develop2x, develop3x etc branches, right?
> 
> Cheers
> Christian
> 
> 
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
>> For additional commands, e-mail: dev-h...@struts.apache.org
>>
> 
> 
> 
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
> 

-- 
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