2012/9/12 Kristian Rosenvold <[email protected]>:
> 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 <[email protected]>:
>> 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 <[email protected]>
>>
>>> Who is going to open the initial negotiation with INFRA?
>>>
>>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy <[email protected]> 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: [email protected]
> For additional commands, e-mail: [email protected]
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to