You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by "Jan Matèrne (jhm)" <ap...@materne.de> on 2014/04/29 08:00:42 UTC
migration to git / intermediate summary
My summary of this intermediate time for the migration-to-git-thread (not
dividing into binding/non-binding votes):
Ant
+1: antoine, jhm, bodewig, Per Arnold Blaasmo, boudart, conor, Michael
Clarke, Charles Duffy (8)
+0: ddevienne, Nicolas Lalevee, Matt (3)
Ivy
+1: antoine, Per Arnold Blaasmo, boudart, conor, Charles Duffy (5)
+0: jhm, bodewig, ddevienne, Nicolas Lalevee, Michael Clarke, Matt (6)
IvyDE
+1: antoine, Per Arnold Blaasmo, boudart, conor (4)
+0: jhm, bodewig, ddevienne, Nicolas Lalevee, Michael Clarke, Matt, Charles
Duffy (7)
EasyAnt
+1: antoine, Per Arnold Blaasmo, boudart, conor (4)
+0: jhm, bodewig, ddevienne, Nicolas Lalevee, Michael Clarke, Matt, Charles
Duffy (7)
Antlibs
+1: antoine, jhm, bodewig, Per Arnold Blaasmo, boudart, conor (6)
+0: ddevienne, Nicolas Lalevee, Michael Clarke, Matt, Charles Duffy (5)
Sandbox
Keeps in SVN for saving the work of migration and because there were only a
few projects in the past which promoted to "real projects".
Migration to git will be done when the project is promoted.
Having on git repo for the whole sandbox will be difficult if one project
will be promoted: "extract only a part of the project with its history".
Homepage
Keeps in SVN as svnpubsub is the only supported mechanism (besides CMS).
gitpubsub is not supported.
Help
Michael Clarke would be "happy to help with any migration or post migration
cleanup of docs/processes, but is only properly familiar with the Ant core
so may not be much help with the likes of Ivy but can give it a shot if
needed."
Infra is providing their own migration tool.
Jan
Re: migration to git : next steps
Posted by Antoine Levy Lambert <an...@gmx.de>.
Hi,
if someone has some spare cycles, you can contact infra to see whether people have questions about the jira
and whether they need help.
Apache infra has a chat channel on freenode.net called #asfinfra where committers can join.
Antoine
On May 19, 2014, at 12:34 AM, Antoine Levy Lambert <an...@gmx.de> wrote:
> I just created an issue in JIRA : https://issues.apache.org/jira/browse/INFRA-7759
>
> Antoine
> On May 14, 2014, at 10:54 PM, Antoine Levy Lambert <an...@gmx.de> wrote:
>
>> Migration of the Ant project and subprojects to Git
>>
>> vote : http://ant.1045680.n5.nabble.com/VOTE-migration-to-git-tt5715081.html#none
>>
>> vote-result : http://ant.1045680.n5.nabble.com/migration-to-git-intermediate-summary-tc5715104.html#none
>>
>> here are the GIT Modules that we need to create
>>
>> ant : http://svn.apache.org/repos/asf/ant/core/
>> ivy : http://svn.apache.org/repos/asf/ant/ivy/core/
>> ivyde : http://svn.apache.org/repos/asf/ant/ivy/ivyde/
>> easyant-buildtypes : http://svn.apache.org/repos/asf/ant/easyant/buildtypes/
>> easyant-core : http://svn.apache.org/repos/asf/ant/easyant/core/
>> easyant-easyant4e : http://svn.apache.org/repos/asf/ant/easyant/easyant4e/
>> easyant-plugins : http://svn.apache.org/repos/asf/ant/easyant/plugins/
>> easyant-skeletons : http://svn.apache.org/repos/asf/ant/easyant/skeletons/
>> easyant-tasks : http://svn.apache.org/repos/asf/ant/easyant/tasks/
>> antlibs-antunit : http://svn.apache.org/repos/asf/ant/antlibs/antunit/
>> antlibs-common : http://svn.apache.org/repos/asf/ant/antlibs/common/
>> antlibs-compress : http://svn.apache.org/repos/asf/ant/antlibs/compress/
>> antlibs-dotnet : http://svn.apache.org/repos/asf/ant/antlibs/dotnet/
>> antlibs-props : http://svn.apache.org/repos/asf/ant/antlibs/props/
>> antlibs-svn : http://svn.apache.org/repos/asf/ant/antlibs/svn/
>> antlibs-vss : http://svn.apache.org/repos/asf/ant/antlibs/vss/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: migration to git : next steps
Posted by Antoine Levy Lambert <an...@gmx.de>.
I just created an issue in JIRA : https://issues.apache.org/jira/browse/INFRA-7759
Antoine
On May 14, 2014, at 10:54 PM, Antoine Levy Lambert <an...@gmx.de> wrote:
> Migration of the Ant project and subprojects to Git
>
> vote : http://ant.1045680.n5.nabble.com/VOTE-migration-to-git-tt5715081.html#none
>
> vote-result : http://ant.1045680.n5.nabble.com/migration-to-git-intermediate-summary-tc5715104.html#none
>
> here are the GIT Modules that we need to create
>
> ant : http://svn.apache.org/repos/asf/ant/core/
> ivy : http://svn.apache.org/repos/asf/ant/ivy/core/
> ivyde : http://svn.apache.org/repos/asf/ant/ivy/ivyde/
> easyant-buildtypes : http://svn.apache.org/repos/asf/ant/easyant/buildtypes/
> easyant-core : http://svn.apache.org/repos/asf/ant/easyant/core/
> easyant-easyant4e : http://svn.apache.org/repos/asf/ant/easyant/easyant4e/
> easyant-plugins : http://svn.apache.org/repos/asf/ant/easyant/plugins/
> easyant-skeletons : http://svn.apache.org/repos/asf/ant/easyant/skeletons/
> easyant-tasks : http://svn.apache.org/repos/asf/ant/easyant/tasks/
> antlibs-antunit : http://svn.apache.org/repos/asf/ant/antlibs/antunit/
> antlibs-common : http://svn.apache.org/repos/asf/ant/antlibs/common/
> antlibs-compress : http://svn.apache.org/repos/asf/ant/antlibs/compress/
> antlibs-dotnet : http://svn.apache.org/repos/asf/ant/antlibs/dotnet/
> antlibs-props : http://svn.apache.org/repos/asf/ant/antlibs/props/
> antlibs-svn : http://svn.apache.org/repos/asf/ant/antlibs/svn/
> antlibs-vss : http://svn.apache.org/repos/asf/ant/antlibs/vss/
Re: migration to git : next steps
Posted by Antoine Levy Lambert <an...@gmx.de>.
I was about to enter an INFRA JIRA for the migration.
see below the suggested text. Let me know your thoughts.
———————————————————————————————————————
Migration of the Ant project and subprojects to Git
vote : http://ant.1045680.n5.nabble.com/VOTE-migration-to-git-tt5715081.html#none
vote-result : http://ant.1045680.n5.nabble.com/migration-to-git-intermediate-summary-tc5715104.html#none
here are the GIT Modules that we need to create
ant : http://svn.apache.org/repos/asf/ant/core/
ivy : http://svn.apache.org/repos/asf/ant/ivy/core/
ivyde : http://svn.apache.org/repos/asf/ant/ivy/ivyde/
easyant-buildtypes : http://svn.apache.org/repos/asf/ant/easyant/buildtypes/
easyant-core : http://svn.apache.org/repos/asf/ant/easyant/core/
easyant-easyant4e : http://svn.apache.org/repos/asf/ant/easyant/easyant4e/
easyant-plugins : http://svn.apache.org/repos/asf/ant/easyant/plugins/
easyant-skeletons : http://svn.apache.org/repos/asf/ant/easyant/skeletons/
easyant-tasks : http://svn.apache.org/repos/asf/ant/easyant/tasks/
antlibs-antunit : http://svn.apache.org/repos/asf/ant/antlibs/antunit/
antlibs-common : http://svn.apache.org/repos/asf/ant/antlibs/common/
antlibs-compress : http://svn.apache.org/repos/asf/ant/antlibs/compress/
antlibs-dotnet : http://svn.apache.org/repos/asf/ant/antlibs/dotnet/
antlibs-props : http://svn.apache.org/repos/asf/ant/antlibs/props/
antlibs-svn : http://svn.apache.org/repos/asf/ant/antlibs/svn/
antlibs-vss : http://svn.apache.org/repos/asf/ant/antlibs/vss/
———————————————————————————————————————
Regards,
Antoine
On May 13, 2014, at 9:17 AM, Matt Sicker <bo...@gmail.com> wrote:
> On Tuesday, 13 May 2014, Antoine Levy Lambert <an...@gmx.de> wrote:
>
>> Hello Matt,
>>
>> this is interesting - thanks for pointing this out since I am a newbie in
>> git land.
>>
>> does one need to do some advance planning to make a module become a
>> submodule of
>> another repository aggregating the submodules ?
>>
>> Nope! You use it somewhat like svn:external, but you manually keep the
> commit ID in sync to whatever you want. I find it useful to use a tag for
> that commit. Otherwise you end up with a history like "update submodule"
> over and over again.
>
>
>> there would be a use case for an aggregation of the complete ant family,
>> maybe for an aggregation of the antlibs too …
>>
>> If there's a master build.xml or similar that can just iterate through all
> the projects and build them in order, that's a neat use case.
>
>
> --
> Matt Sicker <bo...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: migration to git : next steps
Posted by Matt Sicker <bo...@gmail.com>.
On Tuesday, 13 May 2014, Antoine Levy Lambert <an...@gmx.de> wrote:
> Hello Matt,
>
> this is interesting - thanks for pointing this out since I am a newbie in
> git land.
>
> does one need to do some advance planning to make a module become a
> submodule of
> another repository aggregating the submodules ?
>
> Nope! You use it somewhat like svn:external, but you manually keep the
commit ID in sync to whatever you want. I find it useful to use a tag for
that commit. Otherwise you end up with a history like "update submodule"
over and over again.
> there would be a use case for an aggregation of the complete ant family,
> maybe for an aggregation of the antlibs too …
>
> If there's a master build.xml or similar that can just iterate through all
the projects and build them in order, that's a neat use case.
--
Matt Sicker <bo...@gmail.com>
Re: migration to git : next steps
Posted by Antoine Levy Lambert <an...@gmx.de>.
Hello Matt,
this is interesting - thanks for pointing this out since I am a newbie in git land.
does one need to do some advance planning to make a module become a submodule of
another repository aggregating the submodules ?
there would be a use case for an aggregation of the complete ant family, maybe for an aggregation of the antlibs too …
Antoine
On May 12, 2014, at 11:03 PM, Matt Sicker <bo...@gmail.com> wrote:
> Something I've been experimenting with is using git submodules. You
> basically have a repository for each "submodule", then you can have another
> repository that groups them all together for convenience. It's handy for
> making a sort of stable master that points to the latest tag or something
> similar. It's kind of confusing, but I think it works well for when people
> want to check out a project corresponding to the latest stable rather than
> the trunk (which would normally be stable anyway).
>
>
> On 12 May 2014 21:19, Antoine Levy Lambert <an...@gmx.de> wrote:
>
>>
>> Hi,
>>
>> resending a message which I sent on May 7th but might have been lost
>> completely due to our infrastructure problems last week :
>>
>>>
>>>
>>> To actually migrate to git, we could either make one INFRA JIRA for all
>> the ant family of projects, or do this one step at a time.
>>>
>>> Concerning the antlibs, I suppose we want one git module for each antlib
>> - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a
>> common folder which ought to be on its own.
>>>
>>> If we do it one step at a time we could start with ant proper, then move
>> to ivy, ivyde, easyant and the antlibs.
>>>
>>> What do you think ?
>>>
>>> Antoine
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: migration to git : next steps
Posted by Antoine Levy Lambert <an...@gmx.de>.
Hi,
moving to actual action.
jfarrell from infra is setting our svn repo http://svn.apache.org/repos/asf/ant read-only to prepare for the import.
The ant site will remain in svn and stay RW during the process.
Antoine
On May 20, 2014, at 10:25 PM, Matt Sicker <bo...@gmail.com> wrote:
> I'm going to have to look into subtree as I've been using submodule at work
> lately and it's becoming a huge mess.
>
>
> On 20 May 2014 13:39, Charles Duffy <ch...@dyfis.net> wrote:
>
>> I'd suggest looking into git-subtree as well, if we wanted to maintain a
>> single-development-tree experience. Submodules have a reputation
>> (well-deserved, IMHO) of being somewhat unwieldy to work with; using
>> git-subtree to manage linked trees can be a bit more automation/setup work,
>> but can also provide a much smoother user experience.
>>
>>
>> On Mon, May 12, 2014 at 8:03 PM, Matt Sicker <bo...@gmail.com> wrote:
>>
>>> Something I've been experimenting with is using git submodules. You
>>> basically have a repository for each "submodule", then you can have
>> another
>>> repository that groups them all together for convenience. It's handy for
>>> making a sort of stable master that points to the latest tag or something
>>> similar. It's kind of confusing, but I think it works well for when
>> people
>>> want to check out a project corresponding to the latest stable rather
>> than
>>> the trunk (which would normally be stable anyway).
>>>
>>>
>>> On 12 May 2014 21:19, Antoine Levy Lambert <an...@gmx.de> wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> resending a message which I sent on May 7th but might have been lost
>>>> completely due to our infrastructure problems last week :
>>>>
>>>>>
>>>>>
>>>>> To actually migrate to git, we could either make one INFRA JIRA for
>> all
>>>> the ant family of projects, or do this one step at a time.
>>>>>
>>>>> Concerning the antlibs, I suppose we want one git module for each
>>> antlib
>>>> - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a
>>>> common folder which ought to be on its own.
>>>>>
>>>>> If we do it one step at a time we could start with ant proper, then
>>> move
>>>> to ivy, ivyde, easyant and the antlibs.
>>>>>
>>>>> What do you think ?
>>>>>
>>>>> Antoine
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: migration to git : next steps
Posted by Matt Sicker <bo...@gmail.com>.
I'm going to have to look into subtree as I've been using submodule at work
lately and it's becoming a huge mess.
On 20 May 2014 13:39, Charles Duffy <ch...@dyfis.net> wrote:
> I'd suggest looking into git-subtree as well, if we wanted to maintain a
> single-development-tree experience. Submodules have a reputation
> (well-deserved, IMHO) of being somewhat unwieldy to work with; using
> git-subtree to manage linked trees can be a bit more automation/setup work,
> but can also provide a much smoother user experience.
>
>
> On Mon, May 12, 2014 at 8:03 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> > Something I've been experimenting with is using git submodules. You
> > basically have a repository for each "submodule", then you can have
> another
> > repository that groups them all together for convenience. It's handy for
> > making a sort of stable master that points to the latest tag or something
> > similar. It's kind of confusing, but I think it works well for when
> people
> > want to check out a project corresponding to the latest stable rather
> than
> > the trunk (which would normally be stable anyway).
> >
> >
> > On 12 May 2014 21:19, Antoine Levy Lambert <an...@gmx.de> wrote:
> >
> > >
> > > Hi,
> > >
> > > resending a message which I sent on May 7th but might have been lost
> > > completely due to our infrastructure problems last week :
> > >
> > > >
> > > >
> > > > To actually migrate to git, we could either make one INFRA JIRA for
> all
> > > the ant family of projects, or do this one step at a time.
> > > >
> > > > Concerning the antlibs, I suppose we want one git module for each
> > antlib
> > > - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a
> > > common folder which ought to be on its own.
> > > >
> > > > If we do it one step at a time we could start with ant proper, then
> > move
> > > to ivy, ivyde, easyant and the antlibs.
> > > >
> > > > What do you think ?
> > > >
> > > > Antoine
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > For additional commands, e-mail: dev-help@ant.apache.org
> > >
> > >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: migration to git : next steps
Posted by Charles Duffy <ch...@dyfis.net>.
I'd suggest looking into git-subtree as well, if we wanted to maintain a
single-development-tree experience. Submodules have a reputation
(well-deserved, IMHO) of being somewhat unwieldy to work with; using
git-subtree to manage linked trees can be a bit more automation/setup work,
but can also provide a much smoother user experience.
On Mon, May 12, 2014 at 8:03 PM, Matt Sicker <bo...@gmail.com> wrote:
> Something I've been experimenting with is using git submodules. You
> basically have a repository for each "submodule", then you can have another
> repository that groups them all together for convenience. It's handy for
> making a sort of stable master that points to the latest tag or something
> similar. It's kind of confusing, but I think it works well for when people
> want to check out a project corresponding to the latest stable rather than
> the trunk (which would normally be stable anyway).
>
>
> On 12 May 2014 21:19, Antoine Levy Lambert <an...@gmx.de> wrote:
>
> >
> > Hi,
> >
> > resending a message which I sent on May 7th but might have been lost
> > completely due to our infrastructure problems last week :
> >
> > >
> > >
> > > To actually migrate to git, we could either make one INFRA JIRA for all
> > the ant family of projects, or do this one step at a time.
> > >
> > > Concerning the antlibs, I suppose we want one git module for each
> antlib
> > - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a
> > common folder which ought to be on its own.
> > >
> > > If we do it one step at a time we could start with ant proper, then
> move
> > to ivy, ivyde, easyant and the antlibs.
> > >
> > > What do you think ?
> > >
> > > Antoine
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> >
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: migration to git : next steps
Posted by Matt Sicker <bo...@gmail.com>.
Something I've been experimenting with is using git submodules. You
basically have a repository for each "submodule", then you can have another
repository that groups them all together for convenience. It's handy for
making a sort of stable master that points to the latest tag or something
similar. It's kind of confusing, but I think it works well for when people
want to check out a project corresponding to the latest stable rather than
the trunk (which would normally be stable anyway).
On 12 May 2014 21:19, Antoine Levy Lambert <an...@gmx.de> wrote:
>
> Hi,
>
> resending a message which I sent on May 7th but might have been lost
> completely due to our infrastructure problems last week :
>
> >
> >
> > To actually migrate to git, we could either make one INFRA JIRA for all
> the ant family of projects, or do this one step at a time.
> >
> > Concerning the antlibs, I suppose we want one git module for each antlib
> - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a
> common folder which ought to be on its own.
> >
> > If we do it one step at a time we could start with ant proper, then move
> to ivy, ivyde, easyant and the antlibs.
> >
> > What do you think ?
> >
> > Antoine
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
--
Matt Sicker <bo...@gmail.com>
migration to git : next steps
Posted by Antoine Levy Lambert <an...@gmx.de>.
Hi,
resending a message which I sent on May 7th but might have been lost completely due to our infrastructure problems last week :
>
>
> To actually migrate to git, we could either make one INFRA JIRA for all the ant family of projects, or do this one step at a time.
>
> Concerning the antlibs, I suppose we want one git module for each antlib - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a common folder which ought to be on its own.
>
> If we do it one step at a time we could start with ant proper, then move to ivy, ivyde, easyant and the antlibs.
>
> What do you think ?
>
> Antoine
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
migration to git : next steps
Posted by Antoine Levy Lambert <an...@gmx.de>.
To actually migrate to git, we could either make one INFRA JIRA for all the ant family of projects, or do this one step at a time.
Concerning the antlibs, I suppose we want one git module for each antlib - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a common folder which ought to be on its own.
If we do it one step at a time we could start with ant proper, then move to ivy, ivyde, easyant and the antlibs.
What do you think ?
Antoine
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
[VOTE-RESULT] migration to git
Posted by Antoine Levy Lambert <an...@gmx.de>.
Hi,
see below the detailed results of the vote.
I have looked at our bylaws [1]. The Code Change category seems to be the one which corresponds most and requires “Lazy Approval and then Lazy Consensus”
There are at least 3 binding +1s to migrate to git each of the Ant subprojects - Ant core, Ivy, Ivyde, EasyAnt and Antlibs.
So the vote result is to migrate everything - except the sandbox which was excluded from the scope of the vote, and the web site which cannot be migrated.
Antoine
[1] http://ant.apache.org/bylaws.html
update on the summary of Jan, without the non-binding votes
On Apr 29, 2014, at 2:00 AM, Jan Matèrne (jhm) <ap...@materne.de> wrote:
> My summary of this intermediate time for the migration-to-git-thread (not
> dividing into binding/non-binding votes):
>
>
>
> Ant
>
> +1: antoine, jhm, bodewig, boudart, conor, Michael
> Clarke, Charles Duffy, Nicolas Lalevée (8)
>
> +0: ddevienne, Nicolas Lalevee, Matt, Maarten (4)
>
>
>
> Ivy
>
> +1: antoine, boudart, conor, Charles Duffy (4)
>
> +0: jhm, bodewig, ddevienne, Nicolas Lalevee, Michael Clarke, Matt,Nicolas Lalevée (7)
> -0 : Maarten (1)
>
>
> IvyDE
>
> +1: antoine, boudart, conor (3)
>
> +0: jhm, bodewig, ddevienne, Nicolas Lalevee, Michael Clarke, Matt, Charles
> Duffy,Nicolas Lalevée (8)
> -0 : Maarten (1)
>
>
>
> EasyAnt
>
> +1: antoine, boudart, conor (3)
>
> +0: jhm, bodewig, ddevienne, Nicolas Lalevee, Michael Clarke, Matt, Charles
> Duffy,Nicolas Lalevée (7)
> -0 : Maarten (1)
>
>
>
> Antlibs
>
> +1: antoine, jhm, bodewig, boudart, conor,Nicolas Lalevée (5)
>
> +0: ddevienne, Nicolas Lalevee, Michael Clarke, Matt, Charles Duffy, Maarten (5)
>
>
>
> Sandbox
>
> Keeps in SVN for saving the work of migration and because there were only a
> few projects in the past which promoted to "real projects".
>
> Migration to git will be done when the project is promoted.
>
> Having on git repo for the whole sandbox will be difficult if one project
> will be promoted: "extract only a part of the project with its history".
>
>
>
> Homepage
>
> Keeps in SVN as svnpubsub is the only supported mechanism (besides CMS).
>
> gitpubsub is not supported.
>
>
>
> Help
>
> Michael Clarke would be "happy to help with any migration or post migration
> cleanup of docs/processes, but is only properly familiar with the Ant core
> so may not be much help with the likes of Ivy but can give it a shot if
> needed."
>
> Infra is providing their own migration tool.
>
>
>
>
>
> Jan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org