Olivier,
I'm not checked yet ( not thru lazyness, but thru buzyness, and shooting this
email just as I think of it ), in all my local maven/git projects I set in the
maven-release-plugin configuration:
<pushChanges>false</pushChanges>
<localCheckout>true</localCheckout>
to prevent any upstream/origin pushes during release ( there may not BE an
origin/remote yet ). There was some discussion either on here, or in JIRA ( not
sure off hand which ) about making these options the default for any of the
supported distributed version control systems.
Does anyone know if this was done? Should these options be mandated as a
standard practise for maven+git conversion?
Mark
On 20/09/2012, at 1:40 AM, Olivier Lamy <ol...@apache.org> wrote:
> BTW I have started a page here:
> http://maven.apache.org/developers/conventions/git.html
>
> we could put some git tips and more conventions.
>
>
> 2012/9/18 Arnaud Héritier <aherit...@gmail.com>:
>> My remarks about these repos :
>> * trunk will have to be renamed master (I'm not sure if we'll go further
>> like using the git workflow with the develop branch to keep master as
>> stable as possible - In any case I would recommand to follow a convention
>> fix/XXXX, stable/A.B.C, feature/ZZZZ to organize branches)
>> * A strange thing I didn't have in my company repositories I recently
>> migrated is the commit/tag (copy for tag) for each release done by the
>> release plugin. I don't know if it is a different setting in the plugin or
>> something cleaned by filters I applied in the SVN -> GIT migration we did
>> * Some strange branches to cleanup ? ASF, APACHE or by user (trygvis,
>> evenisse ...)
>>
>> That's all what I see for now.
>>
>> Cheers
>>
>>
>> On Tue, Sep 18, 2012 at 8:29 PM, Arnaud Héritier <aherit...@gmail.com>wrote:
>>
>>> I Will test them. Will they keep these ugly URLs git-wip-us in the
>>> future ? I'm not a fanatic but I would prefer to have something stable
>>> to put in our POMs for releases. I know that we don't use often scm
>>> infos after the release but it is sad if we know that they'll be
>>> discontinued in a near future. No ?
>>>
>>> Le 18 sept. 2012 à 19:23, Olivier Lamy <ol...@apache.org> a écrit :
>>>
>>>> Repositories has been migrated to:
>>>> * https://git-wip-us.apache.org/repos/asf/maven-surefire.git
>>>> * https://git-wip-us.apache.org/repos/asf/maven-wagon.git
>>>> * https://git-wip-us.apache.org/repos/asf/maven-scm.git
>>>> They are currently read only.
>>>> Content looks good.
>>>> If nobody complains, I will ask to move to rw mode tomorrow. (in 24H)
>>>>
>>>> 2012/9/18 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
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend: http://coders.talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>>
>>>
>>
>>
>>
>> --
>> -----
>> Arnaud Héritier
>> 06-89-76-64-24
>> http://aheritier.net
>> Mail/GTalk: aherit...@gmail.com
>> Twitter/Skype : aheritier
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
