You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Olivier Lamy <ol...@apache.org> on 2012/09/12 10:44:11 UTC
Plan for git migration
Hi Folks,
So the vote passed, now it's time for volunteers to use their fingers :-).
I have started a page [1] for ETA of migration (note the Volunteer
column :-) ) and for discussion on some stuff (plugins shared)
Thanks
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
[1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Olivier Lamy <ol...@apache.org>.
2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
> Hi,
>
> +1.
> Though I'm volunteering to help, as I'm not Maven committer, I don't know
> if I'm really allowed to help.
> I could help on some projects if needed (I can see maybe enforcer & release
> for example).
>
> By the way, I'm not sure how this is supposed to work. After reading
> Kristian comment, I discovered there's actually already many (if not all)
> Maven projects that seem migrated (?).
> http://git.apache.org/ Is this something that was done by someone during
> the night? :-).
Apache Git mirror exists for long time (mirrored to github.apache.org/apache).
That's not new (just some communication missing imho).
Those are only for read and ease use of git-svn.
Write/cannonical asf git repos are here: https://git-wip-us.apache.org/repos/asf
>
> Or maybe that repos are not correct in some way (Kristian's comment say
> some are already usable as-is)?
>
> What makes a repo correct or not to be used as-is?
>
> Looking at the repo structure from the HTTP interface, I'm under the
> impression this is a git repo created by git svn (or svn2git?), .
> My naive first guess understanding is that there already may be a batch of
> "maven git scripts" running on the infrastructure that would git-svn the
> main repo, then filter-branch this repo for a bunch of directories
> (release, enforcer, etc.).
>
> If this is so, not totally sure what would be left?
moving to https://git-wip-us.apache.org (and various stuff) move some
svn paths to read only.
fix github mirroring.
etc..
>
> Thanks.
>
> 2012/9/12 Benson Margulies <bi...@gmail.com>
>
>> Who is going to open the initial negotiation with INFRA?
>>
>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> wrote:
>> > Hi Folks,
>> > So the vote passed, now it's time for volunteers to use their fingers
>> :-).
>> > I have started a page [1] for ETA of migration (note the Volunteer
>> > column :-) ) and for discussion on some stuff (plugins shared)
>> >
>> >
>> > Thanks
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>
>> --
>> Baptiste <Batmat> MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> nbsp;!
>> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
>>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Olivier Lamy <ol...@apache.org>.
2012/9/12 Kristian Rosenvold <kr...@gmail.com>:
> I'm a long time lurker on infra and #asfinfra; are these the sole places for
> discussing this stuff ?
yup.
>
> Kristian
>
> 2012/9/12 Olivier Lamy <ol...@apache.org>:
>> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>:
>>> Just to clarify additionally: There are existing read-only clones of a
>>> lot of our projects (i'm sure infra can make the rest if they have
>>> value)
>>>
>>> Some of these are excellent and of high quality (surefire, m3 + it's
>>> are the ones I know of) while at least maven-plugins is useless (due
>>> to a strange interpretation of tags - try checking out a tag in the
>>> current maven-plugins git clone !!!). So we need to collect the
>>> assessments of which repos are "migration ready" and which are not.
>>> Any community input on this would be great! (If you've used the clone
>>> and find that tags/branches etc work according to expectations we're
>>> cool)
>>>
>>> For those that are migration ready the process is is something like this:
>>>
>>> 1. Have infra make the existing read-only mirror the official master.
>>> 2. Change scm url in pom
>>> 3. Update github mirroring url (file issue with github)
>> that's something we maintain @asf infra.
>> I recommend you lurking on infra@ mailing list (if you don't already)
>> as some discussions will start here. (see
>> http://www.apache.org/dev/infra-mail.html)
>>
>>> 4. Celebrate
>>>
>>>
>>> For those that for /some/ reason are not ready, we need to resolve
>>> what needs to be done.
>>>
>>> Kristian
>>>
>>>
>>>
>>>
>>>
>>> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>>>> Hi,
>>>>
>>>> +1.
>>>> Though I'm volunteering to help, as I'm not Maven committer, I don't know
>>>> if I'm really allowed to help.
>>>> I could help on some projects if needed (I can see maybe enforcer & release
>>>> for example).
>>>>
>>>> By the way, I'm not sure how this is supposed to work. After reading
>>>> Kristian comment, I discovered there's actually already many (if not all)
>>>> Maven projects that seem migrated (?).
>>>> http://git.apache.org/ Is this something that was done by someone during
>>>> the night? :-).
>>>>
>>>> Or maybe that repos are not correct in some way (Kristian's comment say
>>>> some are already usable as-is)?
>>>>
>>>> What makes a repo correct or not to be used as-is?
>>>>
>>>> Looking at the repo structure from the HTTP interface, I'm under the
>>>> impression this is a git repo created by git svn (or svn2git?), .
>>>> My naive first guess understanding is that there already may be a batch of
>>>> "maven git scripts" running on the infrastructure that would git-svn the
>>>> main repo, then filter-branch this repo for a bunch of directories
>>>> (release, enforcer, etc.).
>>>>
>>>> If this is so, not totally sure what would be left?
>>>>
>>>> Thanks.
>>>>
>>>> 2012/9/12 Benson Margulies <bi...@gmail.com>
>>>>
>>>>> Who is going to open the initial negotiation with INFRA?
>>>>>
>>>>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> wrote:
>>>>> > Hi Folks,
>>>>> > So the vote passed, now it's time for volunteers to use their fingers
>>>>> :-).
>>>>> > I have started a page [1] for ETA of migration (note the Volunteer
>>>>> > column :-) ) and for discussion on some stuff (plugins shared)
>>>>> >
>>>>> >
>>>>> > Thanks
>>>>> > --
>>>>> > Olivier Lamy
>>>>> > Talend: http://coders.talend.com
>>>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>>>>
>>>>> --
>>>>> Baptiste <Batmat> MATHUS - http://batmat.net
>>>>> Sauvez un arbre,
>>>>> Mangez un castor !
>>>>> nbsp;!
>>>>> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Kristian Rosenvold <kr...@gmail.com>.
I'm a long time lurker on infra and #asfinfra; are these the sole places for
discussing this stuff ?
Kristian
2012/9/12 Olivier Lamy <ol...@apache.org>:
> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>:
>> Just to clarify additionally: There are existing read-only clones of a
>> lot of our projects (i'm sure infra can make the rest if they have
>> value)
>>
>> Some of these are excellent and of high quality (surefire, m3 + it's
>> are the ones I know of) while at least maven-plugins is useless (due
>> to a strange interpretation of tags - try checking out a tag in the
>> current maven-plugins git clone !!!). So we need to collect the
>> assessments of which repos are "migration ready" and which are not.
>> Any community input on this would be great! (If you've used the clone
>> and find that tags/branches etc work according to expectations we're
>> cool)
>>
>> For those that are migration ready the process is is something like this:
>>
>> 1. Have infra make the existing read-only mirror the official master.
>> 2. Change scm url in pom
>> 3. Update github mirroring url (file issue with github)
> that's something we maintain @asf infra.
> I recommend you lurking on infra@ mailing list (if you don't already)
> as some discussions will start here. (see
> http://www.apache.org/dev/infra-mail.html)
>
>> 4. Celebrate
>>
>>
>> For those that for /some/ reason are not ready, we need to resolve
>> what needs to be done.
>>
>> Kristian
>>
>>
>>
>>
>>
>> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>>> Hi,
>>>
>>> +1.
>>> Though I'm volunteering to help, as I'm not Maven committer, I don't know
>>> if I'm really allowed to help.
>>> I could help on some projects if needed (I can see maybe enforcer & release
>>> for example).
>>>
>>> By the way, I'm not sure how this is supposed to work. After reading
>>> Kristian comment, I discovered there's actually already many (if not all)
>>> Maven projects that seem migrated (?).
>>> http://git.apache.org/ Is this something that was done by someone during
>>> the night? :-).
>>>
>>> Or maybe that repos are not correct in some way (Kristian's comment say
>>> some are already usable as-is)?
>>>
>>> What makes a repo correct or not to be used as-is?
>>>
>>> Looking at the repo structure from the HTTP interface, I'm under the
>>> impression this is a git repo created by git svn (or svn2git?), .
>>> My naive first guess understanding is that there already may be a batch of
>>> "maven git scripts" running on the infrastructure that would git-svn the
>>> main repo, then filter-branch this repo for a bunch of directories
>>> (release, enforcer, etc.).
>>>
>>> If this is so, not totally sure what would be left?
>>>
>>> Thanks.
>>>
>>> 2012/9/12 Benson Margulies <bi...@gmail.com>
>>>
>>>> Who is going to open the initial negotiation with INFRA?
>>>>
>>>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> wrote:
>>>> > Hi Folks,
>>>> > So the vote passed, now it's time for volunteers to use their fingers
>>>> :-).
>>>> > I have started a page [1] for ETA of migration (note the Volunteer
>>>> > column :-) ) and for discussion on some stuff (plugins shared)
>>>> >
>>>> >
>>>> > Thanks
>>>> > --
>>>> > Olivier Lamy
>>>> > Talend: http://coders.talend.com
>>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>>>
>>>> --
>>>> Baptiste <Batmat> MATHUS - http://batmat.net
>>>> Sauvez un arbre,
>>>> Mangez un castor !
>>>> nbsp;!
>>>> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Mark Struberg <st...@yahoo.de>.
I'm +1 for keep em.
Reason is that this allows quicker digging for some history info. I'm e.g. not sure if moves and stuff gets fully resolved with git-svn. Structure changes are another candidate of loosing history in git-svn (that would hit the maven-3 module).
LieGrue,
strub
----- Original Message -----
> From: Kristian Rosenvold <kr...@gmail.com>
> To: Maven Developers List <de...@maven.apache.org>
> Cc:
> Sent: Wednesday, September 12, 2012 2:47 PM
> Subject: Re: Plan for git migration
>
> Are you thinking about the svn references etched into each commit ?
>
> The current git-svn repos all have this information appended at the
> end of each commit:
> git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
> 13f79535-47bb-0310-9956-ffa450edef68
>
> Personally I think we should keep them, since they contain the
> historical reference to the SVN commit number. And technically we have
> a lot
> of jiras referencing "r990909" so removing them is not a good idea wrt
> traceability of changes.
>
> I know some projects (spring-framework) removed them and others kept
> them. But they have value for us; at least the revision number. We
> could consider rewriting it to just "r900900" although personally I
> think it's just uneccesary work.
>
> Kristian
>
>
>
>
>
>
> 2012/9/12 Nord, James <JN...@nds.com>:
>> The existing ones will likely have a lot of svn metadata which would tnhen
> be broken / wrong and then could cause issues/confusion in the future
>>
>> I have migrated svn repos using the scrips at
> https://github.com/nirvdrum/svn2git which tidies up this extra info and does
> some extra housekeeping.
>>
>> Should you wish to split the svn structure then this allows you to do that.
>>
>> YMMV - but also something that you may not have been aware of.
>>
>> /James
>>
>>> -----Original Message-----
>>> From: Olivier Lamy [mailto:olamy@apache.org]
>>> Sent: 12 September 2012 13:26
>>> To: Maven Developers List
>>> Subject: Re: Plan for git migration
>>>
>>> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>:
>>> > Just to clarify additionally: There are existing read-only clones
> of a
>>> > lot of our projects (i'm sure infra can make the rest if they
> have
>>> > value)
>>> >
>>> > Some of these are excellent and of high quality (surefire, m3 +
> it's
>>> > are the ones I know of) while at least maven-plugins is useless
> (due
>>> > to a strange interpretation of tags - try checking out a tag in
> the
>>> > current maven-plugins git clone !!!). So we need to collect the
>>> > assessments of which repos are "migration ready" and
> which are not.
>>> > Any community input on this would be great! (If you've used
> the clone
>>> > and find that tags/branches etc work according to expectations
> we're
>>> > cool)
>>> >
>>> > For those that are migration ready the process is is something
> like this:
>>> >
>>> > 1. Have infra make the existing read-only mirror the official
> master.
>>> > 2. Change scm url in pom
>>> > 3. Update github mirroring url (file issue with github)
>>> that's something we maintain @asf infra.
>>> I recommend you lurking on infra@ mailing list (if you don't
> already) as some
>>> discussions will start here. (see
>>> http://www.apache.org/dev/infra-mail.html)
>>>
>>> > 4. Celebrate
>>> >
>>> >
>>> > For those that for /some/ reason are not ready, we need to resolve
>>> > what needs to be done.
>>> >
>>> > Kristian
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>>> >> Hi,
>>> >>
>>> >> +1.
>>> >> Though I'm volunteering to help, as I'm not Maven
> committer, I don't
>>> >> know if I'm really allowed to help.
>>> >> I could help on some projects if needed (I can see maybe
> enforcer &
>>> >> release for example).
>>> >>
>>> >> By the way, I'm not sure how this is supposed to work.
> After reading
>>> >> Kristian comment, I discovered there's actually already
> many (if not
>>> >> all) Maven projects that seem migrated (?).
>>> >> http://git.apache.org/ Is this something that was done by
> someone
>>> >> during the night? :-).
>>> >>
>>> >> Or maybe that repos are not correct in some way
> (Kristian's comment
>>> >> say some are already usable as-is)?
>>> >>
>>> >> What makes a repo correct or not to be used as-is?
>>> >>
>>> >> Looking at the repo structure from the HTTP interface, I'm
> under the
>>> >> impression this is a git repo created by git svn (or
> svn2git?), .
>>> >> My naive first guess understanding is that there already may
> be a
>>> >> batch of "maven git scripts" running on the
> infrastructure that would
>>> >> git-svn the main repo, then filter-branch this repo for a
> bunch of
>>> >> directories (release, enforcer, etc.).
>>> >>
>>> >> If this is so, not totally sure what would be left?
>>> >>
>>> >> Thanks.
>>> >>
>>> >> 2012/9/12 Benson Margulies <bi...@gmail.com>
>>> >>
>>> >>> Who is going to open the initial negotiation with INFRA?
>>> >>>
>>> >>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy
> <ol...@apache.org>
>>> wrote:
>>> >>> > Hi Folks,
>>> >>> > So the vote passed, now it's time for volunteers
> to use their
>>> >>> > fingers
>>> >>> :-).
>>> >>> > I have started a page [1] for ETA of migration (note
> the Volunteer
>>> >>> > column :-) ) and for discussion on some stuff
> (plugins shared)
>>> >>> >
>>> >>> >
>>> >>> > Thanks
>>> >>> > --
>>> >>> > Olivier Lamy
>>> >>> > Talend: http://coders.talend.com
>>> >>> > http://twitter.com/olamy |
> http://linkedin.com/in/olamy [1]
>>> >>> >
> https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>> >>>
>>> >>> --
>>> >>> Baptiste <Batmat> MATHUS - http://batmat.net Sauvez
> un arbre, Mangez
>>> >>> un castor !
>>> >>> nbsp;!
>>> >>>
> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
>>> >>>
>>> >
>>> >
> ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>>> > additional commands, e-mail: dev-help@maven.apache.org
>>> >
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
>>> commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ________________________________
>>
>>
>>
> **************************************************************************************
>> This message is confidential and intended only for the addressee. If you
> have received this message in error, please immediately notify the
> postmaster@nds.com and delete it from your system as well as any copies. The
> content of e-mails as well as traffic data may be monitored by NDS for
> employment and security purposes. To protect the environment please do not print
> this e-mail unless necessary.
>>
>> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18
> 4EX, United Kingdom. A company registered in England and Wales. Registered no.
> 3080780. VAT no. GB 603 8808 40-00
>>
> **************************************************************************************
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Benson Margulies <bi...@gmail.com>.
I don't think we get control of this, but I think you'll be happy with
what we do get. Infra has a repeatable process for converting svn
repos to git.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Baptiste MATHUS <ml...@batmat.net>.
For the record, I just tested a fresh clean install using the svn
repository for git failing tags maven-release-3, 4 & 5: that's almost good
news, they're also failing there.
Cheers
2012/9/13 Baptiste MATHUS <ml...@batmat.net>
> Hi,
> Don't know if we need more complete verifications, but here's what I just
> found for the release repo at git://git.apache.org/maven-release.git:
> Using my current box (m3.0.4 / jdk 1.6.0_33), I wrote a simple script<https://gist.github.com/3713444> and
> ran it on the maven-release repo.
>
> Summary:
> Only maven-release-3, maven-release-4 & maven-release-5 tags (respectively
> 2.0-beta6, 7 & 8) cannot be built (tests failed). The others build just
> fine.
> Full builds result can be found here:
> https://dl.dropbox.com/u/6790263/result-mrelease-build.log
>
> So that repo seems to be usable. The failing tags above are for quite old
> versions (2007) and I guess nobody will ever want to start patching an beta
> version? If you want, I can also check if svn tags have the same behaviour.
>
> Do you think some more checks should be done? If so, just let me know:
> * building with other JDK versions? other Maven versions?
> * what else?
>
> I think I'll do the same with menforcer repo in the week-end.
>
> Cheers
>
> 2012/9/12 Kristian Rosenvold <kr...@zenior.no>
>
>> We still need some verification that the individual repos are ok.
>> (build an old tag, just look at file trees to see nothing strange
>> happens)
>>
>> You can post that here.
>>
>> Kristian
>>
>> Den 12. s. 2012 kl. 15:55 skrev Olivier Lamy <ol...@apache.org>:
>>
>> > 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>> >> I can try and take care of enforcer & release to begin with if no-one
>> >> objects. But I cannot add myself to the wiki even logged in. I guess
>> the
>> >> pages are protected to spammers.
>> > Thanks for the help.
>> > But the task will be "relatively easy" as we have already clones
>> > available for some parts of the svn tree.
>> >
>> > It's just a question of available time from ASF infra folks (normally
>> > already existed volunteers from the project will help too at least I
>> > hope :P )
>> >>
>> >> Cheers
>> >>
>> >> 2012/9/12 Olivier Lamy <ol...@apache.org>
>> >>
>> >>> +1 for keep svn references.
>> >>>
>> >>> FYI I will start migration with moving the following repositories:
>> >>> * surefire
>> >>> * wagon
>> >>> * scm
>> >>>
>> >>> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>> >>>> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>
>> >>>>
>> >>>>> Are you thinking about the svn references etched into each commit ?
>> >>>>>
>> >>>>> The current git-svn repos all have this information appended at the
>> >>>>> end of each commit:
>> >>>>> git-svn-id:
>> >>> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
>> >>>>> 13f79535-47bb-0310-9956-ffa450edef68
>> >>>>>
>> >>>>> Personally I think we should keep them, since they contain the
>> >>>>> historical reference to the SVN commit number. And technically we
>> have
>> >>>>> a lot
>> >>>>> of jiras referencing "r990909" so removing them is not a good idea
>> wrt
>> >>>>> traceability of changes.
>> >>>>>
>> >>>>
>> >>>> +1000. I was about to answer in the same vein.
>> >>>> I really think that storing as much information of where a gives path
>> >>> comes
>> >>>> from will be very valuable in the future.
>> >>>>
>> >>>> I cannot understand how one could want to get rid of that
>> informations.
>> >>>> Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
>> >>> some
>> >>>> revisions and it's always very useful to be able to find that very
>> >>> revision
>> >>>> in the Git history.
>> >>>>
>> >>>> Cheers
>> >>>>
>> >>>> --
>> >>>> Baptiste <Batmat> MATHUS - http://batmat.net
>> >>>> Sauvez un arbre,
>> >>>> Mangez un castor !
>> >>>> nbsp;!
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Olivier Lamy
>> >>> Talend: http://coders.talend.com
>> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>
>> >>> --
>> >>> Baptiste <Batmat> MATHUS - http://batmat.net
>> >>> Sauvez un arbre,
>> >>> Mangez un castor !
>> >>> nbsp;!
>> >>> <de...@maven.apache.org>
>> >>>
>> >
>> >
>> >
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: dev-help@maven.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> --
>> Baptiste <Batmat> MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> nbsp;!
>> <de...@maven.apache.org>
>>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: Plan for git migration
Posted by Baptiste MATHUS <ml...@batmat.net>.
Hi,
Don't know if we need more complete verifications, but here's what I just
found for the release repo at git://git.apache.org/maven-release.git:
Using my current box (m3.0.4 / jdk 1.6.0_33), I wrote a simple
script<https://gist.github.com/3713444> and
ran it on the maven-release repo.
Summary:
Only maven-release-3, maven-release-4 & maven-release-5 tags (respectively
2.0-beta6, 7 & 8) cannot be built (tests failed). The others build just
fine.
Full builds result can be found here:
https://dl.dropbox.com/u/6790263/result-mrelease-build.log
So that repo seems to be usable. The failing tags above are for quite old
versions (2007) and I guess nobody will ever want to start patching an beta
version? If you want, I can also check if svn tags have the same behaviour.
Do you think some more checks should be done? If so, just let me know:
* building with other JDK versions? other Maven versions?
* what else?
I think I'll do the same with menforcer repo in the week-end.
Cheers
2012/9/12 Kristian Rosenvold <kr...@zenior.no>
> We still need some verification that the individual repos are ok.
> (build an old tag, just look at file trees to see nothing strange
> happens)
>
> You can post that here.
>
> Kristian
>
> Den 12. s. 2012 kl. 15:55 skrev Olivier Lamy <ol...@apache.org>:
>
> > 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
> >> I can try and take care of enforcer & release to begin with if no-one
> >> objects. But I cannot add myself to the wiki even logged in. I guess the
> >> pages are protected to spammers.
> > Thanks for the help.
> > But the task will be "relatively easy" as we have already clones
> > available for some parts of the svn tree.
> >
> > It's just a question of available time from ASF infra folks (normally
> > already existed volunteers from the project will help too at least I
> > hope :P )
> >>
> >> Cheers
> >>
> >> 2012/9/12 Olivier Lamy <ol...@apache.org>
> >>
> >>> +1 for keep svn references.
> >>>
> >>> FYI I will start migration with moving the following repositories:
> >>> * surefire
> >>> * wagon
> >>> * scm
> >>>
> >>> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
> >>>> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>
> >>>>
> >>>>> Are you thinking about the svn references etched into each commit ?
> >>>>>
> >>>>> The current git-svn repos all have this information appended at the
> >>>>> end of each commit:
> >>>>> git-svn-id:
> >>> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
> >>>>> 13f79535-47bb-0310-9956-ffa450edef68
> >>>>>
> >>>>> Personally I think we should keep them, since they contain the
> >>>>> historical reference to the SVN commit number. And technically we
> have
> >>>>> a lot
> >>>>> of jiras referencing "r990909" so removing them is not a good idea
> wrt
> >>>>> traceability of changes.
> >>>>>
> >>>>
> >>>> +1000. I was about to answer in the same vein.
> >>>> I really think that storing as much information of where a gives path
> >>> comes
> >>>> from will be very valuable in the future.
> >>>>
> >>>> I cannot understand how one could want to get rid of that
> informations.
> >>>> Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
> >>> some
> >>>> revisions and it's always very useful to be able to find that very
> >>> revision
> >>>> in the Git history.
> >>>>
> >>>> Cheers
> >>>>
> >>>> --
> >>>> Baptiste <Batmat> MATHUS - http://batmat.net
> >>>> Sauvez un arbre,
> >>>> Mangez un castor !
> >>>> nbsp;!
> >>>
> >>>
> >>>
> >>> --
> >>> Olivier Lamy
> >>> Talend: http://coders.talend.com
> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>> --
> >>> Baptiste <Batmat> MATHUS - http://batmat.net
> >>> Sauvez un arbre,
> >>> Mangez un castor !
> >>> nbsp;!
> >>> <de...@maven.apache.org>
> >>>
> >
> >
> >
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!
> <de...@maven.apache.org>
>
Re: Plan for git migration
Posted by Kristian Rosenvold <kr...@zenior.no>.
We still need some verification that the individual repos are ok.
(build an old tag, just look at file trees to see nothing strange
happens)
You can post that here.
Kristian
Den 12. s. 2012 kl. 15:55 skrev Olivier Lamy <ol...@apache.org>:
> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>> I can try and take care of enforcer & release to begin with if no-one
>> objects. But I cannot add myself to the wiki even logged in. I guess the
>> pages are protected to spammers.
> Thanks for the help.
> But the task will be "relatively easy" as we have already clones
> available for some parts of the svn tree.
>
> It's just a question of available time from ASF infra folks (normally
> already existed volunteers from the project will help too at least I
> hope :P )
>>
>> Cheers
>>
>> 2012/9/12 Olivier Lamy <ol...@apache.org>
>>
>>> +1 for keep svn references.
>>>
>>> FYI I will start migration with moving the following repositories:
>>> * surefire
>>> * wagon
>>> * scm
>>>
>>> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>>>> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>
>>>>
>>>>> Are you thinking about the svn references etched into each commit ?
>>>>>
>>>>> The current git-svn repos all have this information appended at the
>>>>> end of each commit:
>>>>> git-svn-id:
>>> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
>>>>> 13f79535-47bb-0310-9956-ffa450edef68
>>>>>
>>>>> Personally I think we should keep them, since they contain the
>>>>> historical reference to the SVN commit number. And technically we have
>>>>> a lot
>>>>> of jiras referencing "r990909" so removing them is not a good idea wrt
>>>>> traceability of changes.
>>>>>
>>>>
>>>> +1000. I was about to answer in the same vein.
>>>> I really think that storing as much information of where a gives path
>>> comes
>>>> from will be very valuable in the future.
>>>>
>>>> I cannot understand how one could want to get rid of that informations.
>>>> Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
>>> some
>>>> revisions and it's always very useful to be able to find that very
>>> revision
>>>> in the Git history.
>>>>
>>>> Cheers
>>>>
>>>> --
>>>> Baptiste <Batmat> MATHUS - http://batmat.net
>>>> Sauvez un arbre,
>>>> Mangez un castor !
>>>> nbsp;!
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> --
>>> Baptiste <Batmat> MATHUS - http://batmat.net
>>> Sauvez un arbre,
>>> Mangez un castor !
>>> nbsp;!
>>> <de...@maven.apache.org>
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Olivier Lamy <ol...@apache.org>.
2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
> I can try and take care of enforcer & release to begin with if no-one
> objects. But I cannot add myself to the wiki even logged in. I guess the
> pages are protected to spammers.
Thanks for the help.
But the task will be "relatively easy" as we have already clones
available for some parts of the svn tree.
It's just a question of available time from ASF infra folks (normally
already existed volunteers from the project will help too at least I
hope :P )
>
> Cheers
>
> 2012/9/12 Olivier Lamy <ol...@apache.org>
>
>> +1 for keep svn references.
>>
>> FYI I will start migration with moving the following repositories:
>> * surefire
>> * wagon
>> * scm
>>
>> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>> > 2012/9/12 Kristian Rosenvold <kr...@gmail.com>
>> >
>> >> Are you thinking about the svn references etched into each commit ?
>> >>
>> >> The current git-svn repos all have this information appended at the
>> >> end of each commit:
>> >> git-svn-id:
>> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
>> >> 13f79535-47bb-0310-9956-ffa450edef68
>> >>
>> >> Personally I think we should keep them, since they contain the
>> >> historical reference to the SVN commit number. And technically we have
>> >> a lot
>> >> of jiras referencing "r990909" so removing them is not a good idea wrt
>> >> traceability of changes.
>> >>
>> >
>> > +1000. I was about to answer in the same vein.
>> > I really think that storing as much information of where a gives path
>> comes
>> > from will be very valuable in the future.
>> >
>> > I cannot understand how one could want to get rid of that informations.
>> > Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
>> some
>> > revisions and it's always very useful to be able to find that very
>> revision
>> > in the Git history.
>> >
>> > Cheers
>> >
>> > --
>> > Baptiste <Batmat> MATHUS - http://batmat.net
>> > Sauvez un arbre,
>> > Mangez un castor !
>> > nbsp;!
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> --
>> Baptiste <Batmat> MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> nbsp;!
>> <de...@maven.apache.org>
>>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Baptiste MATHUS <ml...@batmat.net>.
I can try and take care of enforcer & release to begin with if no-one
objects. But I cannot add myself to the wiki even logged in. I guess the
pages are protected to spammers.
Cheers
2012/9/12 Olivier Lamy <ol...@apache.org>
> +1 for keep svn references.
>
> FYI I will start migration with moving the following repositories:
> * surefire
> * wagon
> * scm
>
> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
> > 2012/9/12 Kristian Rosenvold <kr...@gmail.com>
> >
> >> Are you thinking about the svn references etched into each commit ?
> >>
> >> The current git-svn repos all have this information appended at the
> >> end of each commit:
> >> git-svn-id:
> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
> >> 13f79535-47bb-0310-9956-ffa450edef68
> >>
> >> Personally I think we should keep them, since they contain the
> >> historical reference to the SVN commit number. And technically we have
> >> a lot
> >> of jiras referencing "r990909" so removing them is not a good idea wrt
> >> traceability of changes.
> >>
> >
> > +1000. I was about to answer in the same vein.
> > I really think that storing as much information of where a gives path
> comes
> > from will be very valuable in the future.
> >
> > I cannot understand how one could want to get rid of that informations.
> > Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
> some
> > revisions and it's always very useful to be able to find that very
> revision
> > in the Git history.
> >
> > Cheers
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> > nbsp;!
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!
> <de...@maven.apache.org>
>
Re: Plan for git migration
Posted by Olivier Lamy <ol...@apache.org>.
+1 for keep svn references.
FYI I will start migration with moving the following repositories:
* surefire
* wagon
* scm
2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>
>
>> Are you thinking about the svn references etched into each commit ?
>>
>> The current git-svn repos all have this information appended at the
>> end of each commit:
>> git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
>> 13f79535-47bb-0310-9956-ffa450edef68
>>
>> Personally I think we should keep them, since they contain the
>> historical reference to the SVN commit number. And technically we have
>> a lot
>> of jiras referencing "r990909" so removing them is not a good idea wrt
>> traceability of changes.
>>
>
> +1000. I was about to answer in the same vein.
> I really think that storing as much information of where a gives path comes
> from will be very valuable in the future.
>
> I cannot understand how one could want to get rid of that informations.
> Exactly as Kristian said: you have JIRAs, mails, whatever pointing to some
> revisions and it's always very useful to be able to find that very revision
> in the Git history.
>
> Cheers
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Baptiste MATHUS <ml...@batmat.net>.
2012/9/12 Kristian Rosenvold <kr...@gmail.com>
> Are you thinking about the svn references etched into each commit ?
>
> The current git-svn repos all have this information appended at the
> end of each commit:
> git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
> 13f79535-47bb-0310-9956-ffa450edef68
>
> Personally I think we should keep them, since they contain the
> historical reference to the SVN commit number. And technically we have
> a lot
> of jiras referencing "r990909" so removing them is not a good idea wrt
> traceability of changes.
>
+1000. I was about to answer in the same vein.
I really think that storing as much information of where a gives path comes
from will be very valuable in the future.
I cannot understand how one could want to get rid of that informations.
Exactly as Kristian said: you have JIRAs, mails, whatever pointing to some
revisions and it's always very useful to be able to find that very revision
in the Git history.
Cheers
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
nbsp;!
Re: Plan for git migration
Posted by Kristian Rosenvold <kr...@gmail.com>.
Are you thinking about the svn references etched into each commit ?
The current git-svn repos all have this information appended at the
end of each commit:
git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
13f79535-47bb-0310-9956-ffa450edef68
Personally I think we should keep them, since they contain the
historical reference to the SVN commit number. And technically we have
a lot
of jiras referencing "r990909" so removing them is not a good idea wrt
traceability of changes.
I know some projects (spring-framework) removed them and others kept
them. But they have value for us; at least the revision number. We
could consider rewriting it to just "r900900" although personally I
think it's just uneccesary work.
Kristian
2012/9/12 Nord, James <JN...@nds.com>:
> The existing ones will likely have a lot of svn metadata which would tnhen be broken / wrong and then could cause issues/confusion in the future
>
> I have migrated svn repos using the scrips at https://github.com/nirvdrum/svn2git which tidies up this extra info and does some extra housekeeping.
>
> Should you wish to split the svn structure then this allows you to do that.
>
> YMMV - but also something that you may not have been aware of.
>
> /James
>
>> -----Original Message-----
>> From: Olivier Lamy [mailto:olamy@apache.org]
>> Sent: 12 September 2012 13:26
>> To: Maven Developers List
>> Subject: Re: Plan for git migration
>>
>> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>:
>> > Just to clarify additionally: There are existing read-only clones of a
>> > lot of our projects (i'm sure infra can make the rest if they have
>> > value)
>> >
>> > Some of these are excellent and of high quality (surefire, m3 + it's
>> > are the ones I know of) while at least maven-plugins is useless (due
>> > to a strange interpretation of tags - try checking out a tag in the
>> > current maven-plugins git clone !!!). So we need to collect the
>> > assessments of which repos are "migration ready" and which are not.
>> > Any community input on this would be great! (If you've used the clone
>> > and find that tags/branches etc work according to expectations we're
>> > cool)
>> >
>> > For those that are migration ready the process is is something like this:
>> >
>> > 1. Have infra make the existing read-only mirror the official master.
>> > 2. Change scm url in pom
>> > 3. Update github mirroring url (file issue with github)
>> that's something we maintain @asf infra.
>> I recommend you lurking on infra@ mailing list (if you don't already) as some
>> discussions will start here. (see
>> http://www.apache.org/dev/infra-mail.html)
>>
>> > 4. Celebrate
>> >
>> >
>> > For those that for /some/ reason are not ready, we need to resolve
>> > what needs to be done.
>> >
>> > Kristian
>> >
>> >
>> >
>> >
>> >
>> > 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>> >> Hi,
>> >>
>> >> +1.
>> >> Though I'm volunteering to help, as I'm not Maven committer, I don't
>> >> know if I'm really allowed to help.
>> >> I could help on some projects if needed (I can see maybe enforcer &
>> >> release for example).
>> >>
>> >> By the way, I'm not sure how this is supposed to work. After reading
>> >> Kristian comment, I discovered there's actually already many (if not
>> >> all) Maven projects that seem migrated (?).
>> >> http://git.apache.org/ Is this something that was done by someone
>> >> during the night? :-).
>> >>
>> >> Or maybe that repos are not correct in some way (Kristian's comment
>> >> say some are already usable as-is)?
>> >>
>> >> What makes a repo correct or not to be used as-is?
>> >>
>> >> Looking at the repo structure from the HTTP interface, I'm under the
>> >> impression this is a git repo created by git svn (or svn2git?), .
>> >> My naive first guess understanding is that there already may be a
>> >> batch of "maven git scripts" running on the infrastructure that would
>> >> git-svn the main repo, then filter-branch this repo for a bunch of
>> >> directories (release, enforcer, etc.).
>> >>
>> >> If this is so, not totally sure what would be left?
>> >>
>> >> Thanks.
>> >>
>> >> 2012/9/12 Benson Margulies <bi...@gmail.com>
>> >>
>> >>> Who is going to open the initial negotiation with INFRA?
>> >>>
>> >>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org>
>> wrote:
>> >>> > Hi Folks,
>> >>> > So the vote passed, now it's time for volunteers to use their
>> >>> > fingers
>> >>> :-).
>> >>> > I have started a page [1] for ETA of migration (note the Volunteer
>> >>> > column :-) ) and for discussion on some stuff (plugins shared)
>> >>> >
>> >>> >
>> >>> > Thanks
>> >>> > --
>> >>> > Olivier Lamy
>> >>> > Talend: http://coders.talend.com
>> >>> > http://twitter.com/olamy | http://linkedin.com/in/olamy [1]
>> >>> > https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>> >>>
>> >>> --
>> >>> Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez
>> >>> un castor !
>> >>> nbsp;!
>> >>> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
>> >>>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> > additional commands, e-mail: dev-help@maven.apache.org
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
>> commands, e-mail: dev-help@maven.apache.org
>
>
> ________________________________
>
>
> **************************************************************************************
> This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
>
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
> **************************************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Plan for git migration
Posted by "Nord, James" <JN...@nds.com>.
The existing ones will likely have a lot of svn metadata which would tnhen be broken / wrong and then could cause issues/confusion in the future
I have migrated svn repos using the scrips at https://github.com/nirvdrum/svn2git which tidies up this extra info and does some extra housekeeping.
Should you wish to split the svn structure then this allows you to do that.
YMMV - but also something that you may not have been aware of.
/James
> -----Original Message-----
> From: Olivier Lamy [mailto:olamy@apache.org]
> Sent: 12 September 2012 13:26
> To: Maven Developers List
> Subject: Re: Plan for git migration
>
> 2012/9/12 Kristian Rosenvold <kr...@gmail.com>:
> > Just to clarify additionally: There are existing read-only clones of a
> > lot of our projects (i'm sure infra can make the rest if they have
> > value)
> >
> > Some of these are excellent and of high quality (surefire, m3 + it's
> > are the ones I know of) while at least maven-plugins is useless (due
> > to a strange interpretation of tags - try checking out a tag in the
> > current maven-plugins git clone !!!). So we need to collect the
> > assessments of which repos are "migration ready" and which are not.
> > Any community input on this would be great! (If you've used the clone
> > and find that tags/branches etc work according to expectations we're
> > cool)
> >
> > For those that are migration ready the process is is something like this:
> >
> > 1. Have infra make the existing read-only mirror the official master.
> > 2. Change scm url in pom
> > 3. Update github mirroring url (file issue with github)
> that's something we maintain @asf infra.
> I recommend you lurking on infra@ mailing list (if you don't already) as some
> discussions will start here. (see
> http://www.apache.org/dev/infra-mail.html)
>
> > 4. Celebrate
> >
> >
> > For those that for /some/ reason are not ready, we need to resolve
> > what needs to be done.
> >
> > Kristian
> >
> >
> >
> >
> >
> > 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
> >> Hi,
> >>
> >> +1.
> >> Though I'm volunteering to help, as I'm not Maven committer, I don't
> >> know if I'm really allowed to help.
> >> I could help on some projects if needed (I can see maybe enforcer &
> >> release for example).
> >>
> >> By the way, I'm not sure how this is supposed to work. After reading
> >> Kristian comment, I discovered there's actually already many (if not
> >> all) Maven projects that seem migrated (?).
> >> http://git.apache.org/ Is this something that was done by someone
> >> during the night? :-).
> >>
> >> Or maybe that repos are not correct in some way (Kristian's comment
> >> say some are already usable as-is)?
> >>
> >> What makes a repo correct or not to be used as-is?
> >>
> >> Looking at the repo structure from the HTTP interface, I'm under the
> >> impression this is a git repo created by git svn (or svn2git?), .
> >> My naive first guess understanding is that there already may be a
> >> batch of "maven git scripts" running on the infrastructure that would
> >> git-svn the main repo, then filter-branch this repo for a bunch of
> >> directories (release, enforcer, etc.).
> >>
> >> If this is so, not totally sure what would be left?
> >>
> >> Thanks.
> >>
> >> 2012/9/12 Benson Margulies <bi...@gmail.com>
> >>
> >>> Who is going to open the initial negotiation with INFRA?
> >>>
> >>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org>
> wrote:
> >>> > Hi Folks,
> >>> > So the vote passed, now it's time for volunteers to use their
> >>> > fingers
> >>> :-).
> >>> > I have started a page [1] for ETA of migration (note the Volunteer
> >>> > column :-) ) and for discussion on some stuff (plugins shared)
> >>> >
> >>> >
> >>> > Thanks
> >>> > --
> >>> > Olivier Lamy
> >>> > Talend: http://coders.talend.com
> >>> > http://twitter.com/olamy | http://linkedin.com/in/olamy [1]
> >>> > https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
> >>>
> >>> --
> >>> Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez
> >>> un castor !
> >>> nbsp;!
> >>> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
> commands, e-mail: dev-help@maven.apache.org
________________________________
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Olivier Lamy <ol...@apache.org>.
2012/9/12 Kristian Rosenvold <kr...@gmail.com>:
> Just to clarify additionally: There are existing read-only clones of a
> lot of our projects (i'm sure infra can make the rest if they have
> value)
>
> Some of these are excellent and of high quality (surefire, m3 + it's
> are the ones I know of) while at least maven-plugins is useless (due
> to a strange interpretation of tags - try checking out a tag in the
> current maven-plugins git clone !!!). So we need to collect the
> assessments of which repos are "migration ready" and which are not.
> Any community input on this would be great! (If you've used the clone
> and find that tags/branches etc work according to expectations we're
> cool)
>
> For those that are migration ready the process is is something like this:
>
> 1. Have infra make the existing read-only mirror the official master.
> 2. Change scm url in pom
> 3. Update github mirroring url (file issue with github)
that's something we maintain @asf infra.
I recommend you lurking on infra@ mailing list (if you don't already)
as some discussions will start here. (see
http://www.apache.org/dev/infra-mail.html)
> 4. Celebrate
>
>
> For those that for /some/ reason are not ready, we need to resolve
> what needs to be done.
>
> Kristian
>
>
>
>
>
> 2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
>> Hi,
>>
>> +1.
>> Though I'm volunteering to help, as I'm not Maven committer, I don't know
>> if I'm really allowed to help.
>> I could help on some projects if needed (I can see maybe enforcer & release
>> for example).
>>
>> By the way, I'm not sure how this is supposed to work. After reading
>> Kristian comment, I discovered there's actually already many (if not all)
>> Maven projects that seem migrated (?).
>> http://git.apache.org/ Is this something that was done by someone during
>> the night? :-).
>>
>> Or maybe that repos are not correct in some way (Kristian's comment say
>> some are already usable as-is)?
>>
>> What makes a repo correct or not to be used as-is?
>>
>> Looking at the repo structure from the HTTP interface, I'm under the
>> impression this is a git repo created by git svn (or svn2git?), .
>> My naive first guess understanding is that there already may be a batch of
>> "maven git scripts" running on the infrastructure that would git-svn the
>> main repo, then filter-branch this repo for a bunch of directories
>> (release, enforcer, etc.).
>>
>> If this is so, not totally sure what would be left?
>>
>> Thanks.
>>
>> 2012/9/12 Benson Margulies <bi...@gmail.com>
>>
>>> Who is going to open the initial negotiation with INFRA?
>>>
>>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> wrote:
>>> > Hi Folks,
>>> > So the vote passed, now it's time for volunteers to use their fingers
>>> :-).
>>> > I have started a page [1] for ETA of migration (note the Volunteer
>>> > column :-) ) and for discussion on some stuff (plugins shared)
>>> >
>>> >
>>> > Thanks
>>> > --
>>> > Olivier Lamy
>>> > Talend: http://coders.talend.com
>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>>
>>> --
>>> Baptiste <Batmat> MATHUS - http://batmat.net
>>> Sauvez un arbre,
>>> Mangez un castor !
>>> nbsp;!
>>> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Kristian Rosenvold <kr...@gmail.com>.
Just to clarify additionally: There are existing read-only clones of a
lot of our projects (i'm sure infra can make the rest if they have
value)
Some of these are excellent and of high quality (surefire, m3 + it's
are the ones I know of) while at least maven-plugins is useless (due
to a strange interpretation of tags - try checking out a tag in the
current maven-plugins git clone !!!). So we need to collect the
assessments of which repos are "migration ready" and which are not.
Any community input on this would be great! (If you've used the clone
and find that tags/branches etc work according to expectations we're
cool)
For those that are migration ready the process is is something like this:
1. Have infra make the existing read-only mirror the official master.
2. Change scm url in pom
3. Update github mirroring url (file issue with github)
4. Celebrate
For those that for /some/ reason are not ready, we need to resolve
what needs to be done.
Kristian
2012/9/12 Baptiste MATHUS <ml...@batmat.net>:
> Hi,
>
> +1.
> Though I'm volunteering to help, as I'm not Maven committer, I don't know
> if I'm really allowed to help.
> I could help on some projects if needed (I can see maybe enforcer & release
> for example).
>
> By the way, I'm not sure how this is supposed to work. After reading
> Kristian comment, I discovered there's actually already many (if not all)
> Maven projects that seem migrated (?).
> http://git.apache.org/ Is this something that was done by someone during
> the night? :-).
>
> Or maybe that repos are not correct in some way (Kristian's comment say
> some are already usable as-is)?
>
> What makes a repo correct or not to be used as-is?
>
> Looking at the repo structure from the HTTP interface, I'm under the
> impression this is a git repo created by git svn (or svn2git?), .
> My naive first guess understanding is that there already may be a batch of
> "maven git scripts" running on the infrastructure that would git-svn the
> main repo, then filter-branch this repo for a bunch of directories
> (release, enforcer, etc.).
>
> If this is so, not totally sure what would be left?
>
> Thanks.
>
> 2012/9/12 Benson Margulies <bi...@gmail.com>
>
>> Who is going to open the initial negotiation with INFRA?
>>
>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> wrote:
>> > Hi Folks,
>> > So the vote passed, now it's time for volunteers to use their fingers
>> :-).
>> > I have started a page [1] for ETA of migration (note the Volunteer
>> > column :-) ) and for discussion on some stuff (plugins shared)
>> >
>> >
>> > Thanks
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>
>> --
>> Baptiste <Batmat> MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> nbsp;!
>> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Baptiste MATHUS <ml...@batmat.net>.
Hi,
+1.
Though I'm volunteering to help, as I'm not Maven committer, I don't know
if I'm really allowed to help.
I could help on some projects if needed (I can see maybe enforcer & release
for example).
By the way, I'm not sure how this is supposed to work. After reading
Kristian comment, I discovered there's actually already many (if not all)
Maven projects that seem migrated (?).
http://git.apache.org/ Is this something that was done by someone during
the night? :-).
Or maybe that repos are not correct in some way (Kristian's comment say
some are already usable as-is)?
What makes a repo correct or not to be used as-is?
Looking at the repo structure from the HTTP interface, I'm under the
impression this is a git repo created by git svn (or svn2git?), .
My naive first guess understanding is that there already may be a batch of
"maven git scripts" running on the infrastructure that would git-svn the
main repo, then filter-branch this repo for a bunch of directories
(release, enforcer, etc.).
If this is so, not totally sure what would be left?
Thanks.
2012/9/12 Benson Margulies <bi...@gmail.com>
> Who is going to open the initial negotiation with INFRA?
>
> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> wrote:
> > Hi Folks,
> > So the vote passed, now it's time for volunteers to use their fingers
> :-).
> > I have started a page [1] for ETA of migration (note the Volunteer
> > column :-) ) and for discussion on some stuff (plugins shared)
> >
> >
> > Thanks
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!
> <https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration>
>
Re: Plan for git migration
Posted by Olivier Lamy <ol...@apache.org>.
2012/9/12 Benson Margulies <bi...@gmail.com>:
> Who is going to open the initial negotiation with INFRA?
looks to be one of my task :-)
>
> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> wrote:
>> Hi Folks,
>> So the vote passed, now it's time for volunteers to use their fingers :-).
>> I have started a page [1] for ETA of migration (note the Volunteer
>> column :-) ) and for discussion on some stuff (plugins shared)
>>
>>
>> Thanks
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Benson Margulies <bi...@gmail.com>.
Who is going to open the initial negotiation with INFRA?
On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <ol...@apache.org> wrote:
> Hi Folks,
> So the vote passed, now it's time for volunteers to use their fingers :-).
> I have started a page [1] for ETA of migration (note the Volunteer
> column :-) ) and for discussion on some stuff (plugins shared)
>
>
> Thanks
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Olivier Lamy <ol...@apache.org>.
Hi
See https://issues.apache.org/jira/browse/INFRA-5266
Those tree svn paths will be readonly now for migration.
2012/9/12 Olivier Lamy <ol...@apache.org>:
> Hi Folks,
> So the vote passed, now it's time for volunteers to use their fingers :-).
> I have started a page [1] for ETA of migration (note the Volunteer
> column :-) ) and for discussion on some stuff (plugins shared)
>
>
> Thanks
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Plan for git migration
Posted by Mark Derricutt <ma...@talios.com>.
I see mention of the current git-mirros of the svn tree. I recommended caution in just using these, or just looking at these as currently they're not used for releases, and there's well known issues with maven/git releases ( single tag/branch repository wide, maven releases only from the root etc. )
With that in mind - is there a document/plan for how the svn repository will be carved up into smaller git repositories for the various different release cadences of projects?
On 12/09/2012, at 8:44 PM, Olivier Lamy <ol...@apache.org> wrote:
> Hi Folks,
> So the vote passed, now it's time for volunteers to use their fingers :-).
> I have started a page [1] for ETA of migration (note the Volunteer
> column :-) ) and for discussion on some stuff (plugins shared)
>
>
> Thanks
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org