yes. In all cases I'll be on IRC. ping me if you need me On Wed, Sep 19, 2012 at 8:20 AM, Kristian Rosenvold < [email protected]> wrote:
> You may want to wait with the jenkins reconfiguration until we have renamed > "trunk" to "master" (I'd say anthing in the range of +0..10 minutes > after it goes r/w ;), > to avoid doing it twice. > > Kristian > > 2012/9/18 Arnaud Héritier <[email protected]>: > > On Tue, Sep 18, 2012 at 10:00 PM, Olivier Lamy <[email protected]> wrote: > > > >> 2012/9/18 Kristian Rosenvold <[email protected]>: > >> > According to what I understood by reading infra, the url's will > >> > change. Probably fairly "soon". (0-3 months) > >> yup I hope a rewrite mechanism will be provided. > >> BTW not a trouble, hey it's dvcs now :-) > >> > > >> > I also think we should rename the "trunk" branch to master, which we > >> > can do manually once the repos become RW. > >> yup any volunteer to fix jenkins configuration ? :P > >> > > > > I'll do it if you want :-) > > > > > > > >> > > >> > > >> > > >> > 2012/9/18 Arnaud Héritier <[email protected]>: > >> >> 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 < > [email protected] > >> >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 <[email protected]> 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 <[email protected]>: > >> >>> >> 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 <[email protected]>: > >> >>> >>> 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: [email protected] > >> >>> > For additional commands, e-mail: [email protected] > >> >>> > > >> >>> > >> >> > >> >> > >> >> > >> >> -- > >> >> ----- > >> >> Arnaud Héritier > >> >> 06-89-76-64-24 > >> >> http://aheritier.net > >> >> Mail/GTalk: [email protected] > >> >> Twitter/Skype : aheritier > >> > > >> > --------------------------------------------------------------------- > >> > 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] > >> > >> > > > > > > -- > > ----- > > Arnaud Héritier > > 06-89-76-64-24 > > http://aheritier.net > > Mail/GTalk: [email protected] > > Twitter/Skype : aheritier > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- ----- Arnaud Héritier 06-89-76-64-24 http://aheritier.net Mail/GTalk: [email protected] Twitter/Skype : aheritier
