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 :
> On Tue, Sep 18, 2012 at 10:00 PM, Olivier Lamy wrote:
>
>> 2012/9/
Hi,
We solved 12 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=17249&styleName=Html&projectId=11138
There are still a bevy of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MJAVADOC+AND+status+%3D+Open+ORDER+BY+prior
On Tue, Sep 18, 2012 at 10:00 PM, Olivier Lamy wrote:
> 2012/9/18 Kristian Rosenvold :
> > 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 :-)
2012/9/18 Kristian Rosenvold :
> 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, w
According to what I understood by reading infra, the url's will
change. Probably fairly "soon". (0-3 months)
I also think we should rename the "trunk" branch to master, which we
can do manually once the repos become RW.
2012/9/18 Arnaud Héritier :
> My remarks about these repos :
> * trunk will
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/, stable/A.B.C, feature/ to organize br
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 futur
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
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 :
> 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
>
Yes, and sorry again for a bit of hectic handling of this.
After I triggered the vote on Friday, over the weekend I realised I want
https://jira.codehaus.org/browse/MINDEXER-62
in too, but was unable to sit in front of my machine (kids and family
programme). As MINDEXER-62 it introduces a new art
+1
Two minor points:
* please add your key here: http://svn.apache.org/repos/asf/maven/project/KEYS
* even if we don't have a lot of documentation in the website, don't
miss to publish website (at least for javadoc)
Thanks to take care of releasing !
2012/9/17 Tamás Cservenák :
> Hi,
>
> We solv
11 matches
Mail list logo
