Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=NI7NF1nbdMxSneHEAUTT89GMSD+IlB0NhbDSBU/5sPuzAzhAFZFf3eozvqD9HwkxjLK3pFMiAZxhcycn6Qx6BiT1z/6zd9Gy6PkVKutgTWq5hE1Z3nAryCxl+3S96l8LGEmbn7YP8GxSO3q6KsF/pTewWOxcY1M27EwOqKSk+Ck=;
References: 
 <CAPoyBqQYipETM_dif9L_v9dcErkRoTBEer4iezPGeyqFmpyD-Q@mail.gmail.com>
 <2810907465646628150@unknownmsgid>
 <CAFNCU-_uNW=Sp9uvjkLzfHavWbGoyDO=4_4dGndEmAZ6krXA3A@mail.gmail.com>
 <CAPoyBqR4MjoBEVfA2=sv=rvhZQxi95auaEd3EdHV_wPMuy51_Q@mail.gmail.com>
 <05960578-5A2D-4065-B7DC-8A15559962AE@talios.com>
 <CAPoyBqSDx4xUK7g8JXNGL-zuKGfDOKNkQen5aNNUxmvftPJGWg@mail.gmail.com>
 <CAJZRQKxv9mL_Z_wEwk6diT6wBx8FhssRuK-x_oraeZPU2MBSWw@mail.gmail.com>
Message-ID: <1348161347.81439.YahooMailNeo@web28906.mail.ir2.yahoo.com>
Date: Thu, 20 Sep 2012 18:15:47 +0100 (BST)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: Re: Scm, Surefire,
 Wagon migrate to git (please check) [was Plan for git migration]
To: Maven Developers List <dev@maven.apache.org>
In-Reply-To: 
 <CAJZRQKxv9mL_Z_wEwk6diT6wBx8FhssRuK-x_oraeZPU2MBSWw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi folks!=0A=0AThe problem is the rollback.=0AIn DeltaSpike we do _not_ pus=
h now. deleting a tag on one repo is not a problem, but you would crash all=
 downstream clones as re-trying a release is basically a history rewrite.=
=0A=0AIn DeltaSpike I do the release locally and push the tag + release bra=
nch to my github clone (or any other public repo you like).=0AAfter the VOT=
E passes I merge it to master and push it to the ASF canonical repo.=0A=0AN=
ot perfect neither, but worked far better than history rewrites at least ;)=
=0A=0ALieGrue,=0Astrub=0A=0A=0A=0A=0A----- Original Message -----=0A> From:=
 Kristian Rosenvold <kristian.rosenvold@gmail.com>=0A> To: Maven Developers=
 List <dev@maven.apache.org>=0A> Cc: =0A> Sent: Thursday, September 20, 201=
2 4:56 PM=0A> Subject: Re: Scm, Surefire, Wagon migrate to git (please chec=
k) [was Plan for git migration]=0A> =0A> I just checked and there is no gen=
eral blocking for deleting tags. We=0A> should definitely push as part of r=
elease plugin. Tags ar cheap.=0A> =0A> Kristian=0A> =0A> =0A> 2012/9/20 Oli=
vier Lamy <olamy@apache.org>:=0A>>  2012/9/20 Mark Derricutt <mark@talios.c=
om>:=0A>>>  Olivier,=0A>>> =0A>>>  I'm not checked yet ( not thru lazyness,=
 but thru buzyness, and =0A> shooting this email just as I think of it ), i=
n all my local maven/git projects =0A> I set in the maven-release-plugin co=
nfiguration:=0A>>> =0A>>>  <pushChanges>false</pushChanges>=0A>>>  <localCh=
eckout>true</localCheckout>=0A>>> =0A>>>  to prevent any upstream/origin pu=
shes during release ( there may not BE =0A> an origin/remote yet ). There w=
as some discussion either on here, or in JIRA ( =0A> not sure off hand whic=
h ) about making these options the default for any of the =0A> supported di=
stributed version control systems.=0A>>> =0A>>>  Does anyone know if this w=
as done? Should these options be mandated as =0A> a standard practise for m=
aven+git conversion?=0A>> =0A>>  No release yet.=0A>>  But regarding <pushC=
hanges>false</pushChanges>, I remember we =0A> used on=0A>>  jenkins side a=
nd everybody missed the manual step (push the tag) when=0A>>  released. So =
we moved to true.=0A>>  BTW it's something to discuss.=0A>>  Maybe pushing =
the tag once release vote passed ?=0A>>  I remember some discussions on ASF=
 infra for blocking of tag deletion=0A>>  (I don't know if this has been ap=
plied on the final infra) because we=0A>>  sometimes delete tags if the rel=
ease vote fail.=0A>>  I can test creating a fake tag and try delete it :-)=
=0A>> =0A>>> =0A>>>  Mark=0A>>> =0A>>> =0A>>> =0A>>>  On 20/09/2012, at 1:4=
0 AM, Olivier Lamy <olamy@apache.org> wrote:=0A>>> =0A>>>>  BTW I have star=
ted a page here:=0A>>>>  http://maven.apache.org/developers/conventions/git=
.html=0A>>>> =0A>>>>  we could put some git tips and more conventions.=0A>>=
>> =0A>>>> =0A>>>>  2012/9/18 Arnaud H=E9ritier <aheritier@gmail.com>:=0A>>=
>>>  My remarks about these repos :=0A>>>>>  * trunk will have to be rename=
d master (I'm not sure if =0A> we'll go further=0A>>>>>  like using the git=
 workflow with the develop branch to keep =0A> master as=0A>>>>>  stable as=
 possible - In any case I would recommand to follow a =0A> convention=0A>>>=
>>  fix/XXXX, stable/A.B.C, feature/ZZZZ to organize branches)=0A>>>>>  * A=
 strange thing I didn't have in my company repositories =0A> I recently=0A>=
>>>>  migrated is the commit/tag (copy for tag) for each release done =0A> =
by the=0A>>>>>  release plugin. I don't know if it is a different setting =
=0A> in the plugin or=0A>>>>>  something cleaned by filters I applied in th=
e SVN -> GIT =0A> migration we did=0A>>>>>  * Some strange branches to clea=
nup ? ASF, APACHE or by user =0A> (trygvis,=0A>>>>>  evenisse ...)=0A>>>>> =
=0A>>>>>  That's all what I see for now.=0A>>>>> =0A>>>>>  Cheers=0A>>>>> =
=0A>>>>> =0A>>>>>  On Tue, Sep 18, 2012 at 8:29 PM, Arnaud H=E9ritier =0A> =
<aheritier@gmail.com>wrote:=0A>>>>> =0A>>>>>>  I Will test them. Will they =
keep these ugly URLs git-wip-us =0A> in the=0A>>>>>>  future ? I'm not a fa=
natic but I would prefer to have =0A> something stable=0A>>>>>>  to put in =
our POMs for releases. I know that we don't =0A> use often scm=0A>>>>>>  in=
fos after the release but it is sad if we know that =0A> they'll be=0A>>>>>=
>  discontinued in a near future. No ?=0A>>>>>> =0A>>>>>>  Le 18 sept. 2012=
 =E0 19:23, Olivier Lamy =0A> <olamy@apache.org> a =E9crit :=0A>>>>>> =0A>>=
>>>>>  Repositories has been migrated to:=0A>>>>>>>  * =0A> https://git-wip=
-us.apache.org/repos/asf/maven-surefire.git=0A>>>>>>>  * =0A> https://git-w=
ip-us.apache.org/repos/asf/maven-wagon.git=0A>>>>>>>  * https://git-wip-us.=
apache.org/repos/asf/maven-scm.git=0A>>>>>>>  They are currently read only.=
=0A>>>>>>>  Content looks good.=0A>>>>>>>  If nobody complains, I will ask =
to move to rw mode =0A> tomorrow. (in 24H)=0A>>>>>>> =0A>>>>>>>  2012/9/18 =
Olivier Lamy <olamy@apache.org>:=0A>>>>>>>>  Hi=0A>>>>>>>>  See =0A> https:=
//issues.apache.org/jira/browse/INFRA-5266=0A>>>>>>>>  Those tree svn paths=
 will be readonly now for =0A> migration.=0A>>>>>>>> =0A>>>>>>>>  2012/9/12=
 Olivier Lamy <olamy@apache.org>:=0A>>>>>>>>>  Hi Folks,=0A>>>>>>>>>  So th=
e vote passed, now it's time for =0A> volunteers to use their fingers=0A>>>=
>>>  :-).=0A>>>>>>>>>  I have started a page [1] for ETA of migration =0A> =
(note the Volunteer=0A>>>>>>>>>  column :-) ) and for discussion on some st=
uff =0A> (plugins shared)=0A>>>>>>>>> =0A>>>>>>>>> =0A>>>>>>>>>  Thanks=0A>=
>>>>>>>>  --=0A>>>>>>>>>  Olivier Lamy=0A>>>>>>>>>  Talend: http://coders.t=
alend.com=0A>>>>>>>>>  http://twitter.com/olamy | =0A> http://linkedin.com/=
in/olamy=0A>>>>>>>>>  [1] =0A> https://cwiki.apache.org/confluence/display/=
MAVEN/Git+Migration=0A>>>>>>>> =0A>>>>>>>> =0A>>>>>>>> =0A>>>>>>>>  --=0A>>=
>>>>>>  Olivier Lamy=0A>>>>>>>>  Talend: http://coders.talend.com=0A>>>>>>>=
>  http://twitter.com/olamy | =0A> http://linkedin.com/in/olamy=0A>>>>>>> =
=0A>>>>>>> =0A>>>>>>> =0A>>>>>>>  --=0A>>>>>>>  Olivier Lamy=0A>>>>>>>  Tal=
end: http://coders.talend.com=0A>>>>>>>  http://twitter.com/olamy | http://=
linkedin.com/in/olamy=0A>>>>>>> =0A>>>>>>> =0A> ---------------------------=
------------------------------------------=0A>>>>>>>  To unsubscribe, e-mai=
l: =0A> dev-unsubscribe@maven.apache.org=0A>>>>>>>  For additional commands=
, e-mail: =0A> dev-help@maven.apache.org=0A>>>>>>> =0A>>>>>> =0A>>>>> =0A>>=
>>> =0A>>>>> =0A>>>>>  --=0A>>>>>  -----=0A>>>>>  Arnaud H=E9ritier=0A>>>>>=
  06-89-76-64-24=0A>>>>>  http://aheritier.net=0A>>>>>  Mail/GTalk: aheriti=
er@gmail.com=0A>>>>>  Twitter/Skype : aheritier=0A>>>> =0A>>>> =0A>>>> =0A>=
>>>  --=0A>>>>  Olivier Lamy=0A>>>>  Talend: http://coders.talend.com=0A>>>=
>  http://twitter.com/olamy | http://linkedin.com/in/olamy=0A>>>> =0A>>>> =
=0A> ---------------------------------------------------------------------=
=0A>>>>  To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org=0A>>>>  F=
or additional commands, e-mail: dev-help@maven.apache.org=0A>>>> =0A>>> =0A=
>>> =0A>>>  ---------------------------------------------------------------=
------=0A>>>  To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org=0A>>=
>  For additional commands, e-mail: dev-help@maven.apache.org=0A>>> =0A>> =
=0A>> =0A>> =0A>>  --=0A>>  Olivier Lamy=0A>>  Talend: http://coders.talend=
.com=0A>>  http://twitter.com/olamy | http://linkedin.com/in/olamy=0A>> =0A=
>>  ---------------------------------------------------------------------=
=0A>>  To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org=0A>>  For a=
dditional commands, e-mail: dev-help@maven.apache.org=0A>> =0A> =0A> ------=
---------------------------------------------------------------=0A> To unsu=
bscribe, e-mail: dev-unsubscribe@maven.apache.org=0A> For additional comman=
ds, e-mail: dev-help@maven.apache.org=0A> 

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