Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
MIME-Version: 1.0
In-Reply-To: <52397E0C.2060305@gmail.com>
References: 
 <CAMopvkMgj1GHzp-ana616=YiduVyR1zepz5bO-rahrBcVQDp9g@mail.gmail.com>
 <CAECLKPHStEBTH1_QpWYwaowC3DpZJAGTuX-MBBjEKH8Eq-QKXg@mail.gmail.com>
 <5232BAE9.5040804@gmail.com>
 <CAECLKPE-P==DBHtYu-k9rkWg7Y81ymteFRqtT0tWyAay5PHpvw@mail.gmail.com>
 <5238A9FE.7030503@gmail.com>
 <CAHZ=2HsZpihKWUgTqhA53p6FeRLGNNwVnDcCaP0Nw2VoV88sdg@mail.gmail.com>
 <5238C456.3000702@gmail.com>
 <CAMopvkP0uQJFBood7y9Vw4cmH_6TtHXiBAQi89jfM543Rhw6dA@mail.gmail.com>
 <52397E0C.2060305@gmail.com>
From: Lukasz Lenart <lukaszlenart@apache.org>
Date: Wed, 16 Oct 2013 10:50:14 +0200
Message-ID: 
 <CAMopvkOoMYpzXLsmC5R-NxW-4kOjjBa9rB+ZToqXQaCFFLppgg@mail.gmail.com>
Subject: Re: Svn to Git migration
To: Struts Developers List <dev@struts.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

As far as I know, SvnPubSub doesn't support Git right now. So we can
migrate struts2/trunk to Git but the rest must stay as is. And if we
plan to migrate/create new user guide, it will be hosted via
Subversion. Any doubts?


Regards
--=20
=C5=81ukasz
+ 48 606 323 122 http://www.lenart.org.pl/

2013/9/18 Rene Gielen <rene.gielen@gmail.com>:
> +1
>
> Am 18.09.13 11:38, schrieb Lukasz Lenart:
>> When 2.3.15.2 will be officially out, I want to send request to Infra
>> for Svn to Git migration
>>
>> 2013/9/17 Christian Grobmeier <grobmeier@gmail.com>:
>>> thats fine :-) Now as we have that agreement, let's keep us moving :)
>>>
>>> Am 17.09.13 22:48, schrieb Rene Gielen:
>>>> I just wanted to get this clarified. Seems like we have an agreement :=
-)
>>>> Am 17.09.2013 21:14 schrieb "Christian Grobmeier" <grobmeier@gmail.com=
>:
>>>>
>>>>> Am 17.09.13 21:06, schrieb Johannes Geppert:
>>>>>>> -1 for moving trunk only. We don't want to lose history, and we wou=
ld
>>>>>>> not want two repositories for one project (Struts 2). Once we moved=
 to
>>>>>>> git, the full struts2 svn tree should either be switched to read-on=
ly
>>>>>>> or/and later be removed.
>>>>>>
>>>>>> Sure you are right the history should not be lost.
>>>>>> What I mean is not to migrate the struts1, archive, sandbox
>>>>>> and site into the new struts.git repository.
>>>>>
>>>>> You speak of different things.
>>>>>
>>>>> This is not to migrate:
>>>>> http://svn.apache.org/repos/asf/struts/
>>>>> and I believe Jo is against migrating the content of all of that. I
>>>>> agree with him.
>>>>>
>>>>> We need to migrate this:
>>>>>
>>>>> http://svn.apache.org/repos/asf/struts/struts2/
>>>>> including branches (there are non in short time), tags and trunk.
>>>>>
>>>>> I bet you are on the same page here.
>>>>>
>>>>>
>>>>>>
>>>>>> Johannes
>>>>>>
>>>>>> #################################################
>>>>>> web: http://www.jgeppert.com
>>>>>> twitter: http://twitter.com/jogep
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2013/9/13 Rene Gielen <rene.gielen@gmail.com>
>>>>>>
>>>>>>> +1 for git flow as the way to go, including excellent tooling - com=
mand
>>>>>>> line extensions, Atlassian Sourcetree support and even a IDEA plugi=
n
>>>>>>> (https://github.com/OpherV/gitflow4idea) help to make this an elega=
nt
>>>>>>> abstract and reliable workflow.
>>>>>>>
>>>>>>> -1 for moving trunk only. We don't want to lose history, and we wou=
ld
>>>>>>> not want two repositories for one project (Struts 2). Once we moved=
 to
>>>>>>> git, the full struts2 svn tree should either be switched to read-on=
ly
>>>>>>> or/and later be removed.
>>>>>>>
>>>>>>> +1 for dealing with ../branches/STRUTS_3_X etc as hierarchical feat=
ure
>>>>>>> branches from which single feature branches will be forked for actu=
al
>>>>>>> development - at least for now. I want to investigate further on th=
is
>>>>>>> one, but basically there should not be a problem if we start like t=
his.
>>>>>>>
>>>>>>> - Ren=C3=A9
>>>>>>>
>>>>>>> Am 12.09.13 21:48, schrieb 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.
>>>>>>>>
>>>>>>>> Johannes
>>>>>>>>
>>>>>>>> #################################################
>>>>>>>> web: http://www.jgeppert.com
>>>>>>>> twitter: http://twitter.com/jogep
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/9/11 Lukasz Lenart <lukaszlenart@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 a=
nd
>>>>>>>>> diverse versions internally via branches - so the current S2 sour=
ce
>>>>>>>>> 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
>>>>>>>>> --
>>>>>>>>> =C5=81ukasz
>>>>>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>>>>>>
>>>>>>>>> PS. It'll be implemented after cleaning up current pipeline :-)
>>>>>>>>>
>>>>>>>>> -----------------------------------------------------------------=
----
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Ren=C3=A9 Gielen
>>>>>>> http://twitter.com/rgielen
>>>>>>>
>>>>>>> -------------------------------------------------------------------=
--
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>
>
> --
> Ren=C3=A9 Gielen
> http://twitter.com/rgielen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>

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