[ANNOUNCE] Apache Commons Collections moved to git

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

[ANNOUNCE] Apache Commons Collections moved to git

Rob Tompkins-2
Hello all,

The Apache Commons Collections component has been moved to git. The new source repository location is:

https://git-wip-us.apache.org/repos/asf/commons-collections.git <https://git-wip-us.apache.org/repos/asf/commons-collections.git>

The old SVN source tree has been moved to an archive location:

https://svn.apache.org/repos/asf/commons/_moved_to_git/collections <https://svn.apache.org/repos/asf/commons/_moved_to_git/collections>

Cheers,
-Rob
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

Stefan Bodewig
On 2017-07-19, Rob Tompkins wrote:

> The Apache Commons Collections component has been moved to git.

Many thanks for doing that, Rob!

Are you following some kind of playbook with the git migration? If so,
we should add one point:

* edit the svn:externals property of
  https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
  entry for the component just migrated.

Cheers

        Stefan

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

Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

Rob Tompkins

> On Jul 19, 2017, at 8:13 AM, Stefan Bodewig <[hidden email]> wrote:
>
> On 2017-07-19, Rob Tompkins wrote:
>
>> The Apache Commons Collections component has been moved to git.
>
> Many thanks for doing that, Rob!
>
> Are you following some kind of playbook with the git migration? If so,
> we should add one point:
>
> * edit the svn:externals property of
>  https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
>  entry for the component just migrated.

Good point, and no playbook here. I suppose we should either: 1. create such a playbook, or 2. do the remainder of the repos so that such a playbook is no longer needed. :-)

>
> Cheers
>
>        Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

garydgregory
In reply to this post by Stefan Bodewig
On Jul 19, 2017 05:13, "Stefan Bodewig" <[hidden email]> wrote:

On 2017-07-19, Rob Tompkins wrote:

> The Apache Commons Collections component has been moved to git.

Many thanks for doing that, Rob!


+1 👍

Gary


Are you following some kind of playbook with the git migration? If so,
we should add one point:

* edit the svn:externals property of
  https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
  entry for the component just migrated.

Cheers

        Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

garydgregory
In reply to this post by Rob Tompkins
On Jul 19, 2017 05:16, "Rob Tompkins" <[hidden email]> wrote:


> On Jul 19, 2017, at 8:13 AM, Stefan Bodewig <[hidden email]> wrote:
>
> On 2017-07-19, Rob Tompkins wrote:
>
>> The Apache Commons Collections component has been moved to git.
>
> Many thanks for doing that, Rob!
>
> Are you following some kind of playbook with the git migration? If so,
> we should add one point:
>
> * edit the svn:externals property of
>  https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
>  entry for the component just migrated.

Good point, and no playbook here. I suppose we should either: 1. create
such a playbook, or 2. do the remainder of the repos so that such a
playbook is no longer needed. :-)


It would be good to put that in our wiki, other folks might want to pitch
in.

Gary


>
> Cheers
>
>        Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

Stefan Bodewig
In reply to this post by Rob Tompkins
On 2017-07-19, Rob Tompkins wrote:

>> On Jul 19, 2017, at 8:13 AM, Stefan Bodewig <[hidden email]> wrote:

>> On 2017-07-19, Rob Tompkins wrote:

>>> The Apache Commons Collections component has been moved to git.

>> Many thanks for doing that, Rob!

>> Are you following some kind of playbook with the git migration? If so,
>> we should add one point:

>> * edit the svn:externals property of
>>  https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
>>  entry for the component just migrated.

> Good point, and no playbook here. I suppose we should either:
> 1. create such a playbook, or 2. do the remainder of the repos so that
> such a playbook is no longer needed. :-)

True.

I'm all for option 1 and may find some time over the weekend to start a
page inside the wiki, based on what I recall doing back when I migrated
Compress. Given that a few things have changed since then (the
self-service stuff didn't exist) and you've done it a few times now, I
wouldn't feel bad if you beat me to it and started the page ;-)

Cheers

        Stefan

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

Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

Amey Jadiye
In reply to this post by Rob Tompkins
BTW, I just sorted all proper components and below is the list of component
still using svn, seems quit a lot work still remaining ;-)

bcel | http://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0
bcel
beanUtils |http://svn.apache.org/viewvc/commons/proper/beanutils/trunk/
bsf|http://svn.apache.org/repos/asf/commons/proper/bsf/trunk
build-plugin|
http://svn.apache.org/viewvc/commons/proper/commons-build-plugin/trunk
chain|http://svn.apache.org/viewvc/commons/proper/chain/trunk
codec|http://svn.apache.org/viewvc/commons/proper/codec/trunk
configuration|
http://svn.apache.org/viewvc/commons/proper/configuration/trunk
daemon|http://svn.apache.org/viewvc/commons/proper/daemon/trunk
digester|http://svn.apache.org/viewvc/commons/proper/digester/trunk
discovery|http://svn.apache.org/viewvc/commons/proper/discovery/trunk
email|http://svn.apache.org/viewvc/commons/proper/email/trunk
exec|http://svn.apache.org/viewvc/commons/proper/exec/trunk
functor|http://svn.apache.org/viewvc/commons/proper/functor/trunk/
jci|http://svn.apache.org/viewvc/commons/proper/jci/trunk/
jcs|http://svn.apache.org/viewvc/commons/proper/jcs/tags/commons-jcs-2.1
jexl|http://svn.apache.org/viewvc/commons/proper/jexl/tags/COMMONS_JEXL_3_1
jxpath|http://svn.apache.org/repos/asf/commons/proper/jxpath/trunk
launcher|http://svn.apache.org/repos/asf/commons/proper/jxpath/trunk
logging|http://svn.apache.org/repos/asf/commons/proper/logging/trunk
net|http://svn.apache.org/viewvc/commons/proper/net/tags/NET_3_6
ognl|http://svn.apache.org/viewvc/commons/proper/ognl/trunk/
pool|http://svn.apache.org/viewvc/commons/proper/pool/trunk
proxy|http://svn.apache.org/repos/asf/commons/proper/proxy/trunk/
transaction|http://svn.apache.org/viewvc/commons/proper/transaction/trunk
validator|
http://svn.apache.org/viewvc/commons/proper/validator/tags/VALIDATOR_1_6/
vfs|
http://svn.apache.org/viewvc/commons/proper/vfs/tags/commons-vfs2-project-2.1
weaver|http://svn.apache.org/viewvc/commons/proper/weaver/trunk/


Regards,
Amey


On Wed, Jul 19, 2017 at 5:46 PM, Rob Tompkins <[hidden email]> wrote:

>
>
> > On Jul 19, 2017, at 8:13 AM, Stefan Bodewig <[hidden email]> wrote:
> >
> > On 2017-07-19, Rob Tompkins wrote:
> >
> >> The Apache Commons Collections component has been moved to git.
> >
> > Many thanks for doing that, Rob!
> >
> > Are you following some kind of playbook with the git migration? If so,
> > we should add one point:
> >
> > * edit the svn:externals property of
> >  https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
> >  entry for the component just migrated.
>
> Good point, and no playbook here. I suppose we should either: 1. create
such a playbook, or 2. do the remainder of the repos so that such a
playbook is no longer needed. :-)

>
> >
> > Cheers
> >
> >        Stefan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

garydgregory
I suspect we will do these on a one off basis... but some might stay put
since they are not seeing much activity if any.

Gary

On Fri, Jul 21, 2017 at 11:15 AM, Amey Jadiye <[hidden email]> wrote:

> BTW, I just sorted all proper components and below is the list of component
> still using svn, seems quit a lot work still remaining ;-)
>
> bcel | http://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_0
> bcel
> beanUtils |http://svn.apache.org/viewvc/commons/proper/beanutils/trunk/
> bsf|http://svn.apache.org/repos/asf/commons/proper/bsf/trunk
> build-plugin|
> http://svn.apache.org/viewvc/commons/proper/commons-build-plugin/trunk
> chain|http://svn.apache.org/viewvc/commons/proper/chain/trunk
> codec|http://svn.apache.org/viewvc/commons/proper/codec/trunk
> configuration|
> http://svn.apache.org/viewvc/commons/proper/configuration/trunk
> daemon|http://svn.apache.org/viewvc/commons/proper/daemon/trunk
> digester|http://svn.apache.org/viewvc/commons/proper/digester/trunk
> discovery|http://svn.apache.org/viewvc/commons/proper/discovery/trunk
> email|http://svn.apache.org/viewvc/commons/proper/email/trunk
> exec|http://svn.apache.org/viewvc/commons/proper/exec/trunk
> functor|http://svn.apache.org/viewvc/commons/proper/functor/trunk/
> jci|http://svn.apache.org/viewvc/commons/proper/jci/trunk/
> jcs|http://svn.apache.org/viewvc/commons/proper/jcs/tags/commons-jcs-2.1
> jexl|http://svn.apache.org/viewvc/commons/proper/jexl/
> tags/COMMONS_JEXL_3_1
> jxpath|http://svn.apache.org/repos/asf/commons/proper/jxpath/trunk
> launcher|http://svn.apache.org/repos/asf/commons/proper/jxpath/trunk
> logging|http://svn.apache.org/repos/asf/commons/proper/logging/trunk
> net|http://svn.apache.org/viewvc/commons/proper/net/tags/NET_3_6
> ognl|http://svn.apache.org/viewvc/commons/proper/ognl/trunk/
> pool|http://svn.apache.org/viewvc/commons/proper/pool/trunk
> proxy|http://svn.apache.org/repos/asf/commons/proper/proxy/trunk/
> transaction|http://svn.apache.org/viewvc/commons/proper/transaction/trunk
> validator|
> http://svn.apache.org/viewvc/commons/proper/validator/tags/VALIDATOR_1_6/
> vfs|
> http://svn.apache.org/viewvc/commons/proper/vfs/tags/
> commons-vfs2-project-2.1
> weaver|http://svn.apache.org/viewvc/commons/proper/weaver/trunk/
>
>
> Regards,
> Amey
>
>
> On Wed, Jul 19, 2017 at 5:46 PM, Rob Tompkins <[hidden email]> wrote:
> >
> >
> > > On Jul 19, 2017, at 8:13 AM, Stefan Bodewig <[hidden email]>
> wrote:
> > >
> > > On 2017-07-19, Rob Tompkins wrote:
> > >
> > >> The Apache Commons Collections component has been moved to git.
> > >
> > > Many thanks for doing that, Rob!
> > >
> > > Are you following some kind of playbook with the git migration? If so,
> > > we should add one point:
> > >
> > > * edit the svn:externals property of
> > >  https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
> > >  entry for the component just migrated.
> >
> > Good point, and no playbook here. I suppose we should either: 1. create
> such a playbook, or 2. do the remainder of the repos so that such a
> playbook is no longer needed. :-)
> >
> > >
> > > Cheers
> > >
> > >        Stefan
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

Stefan Bodewig
In reply to this post by Stefan Bodewig
On 2017-07-21, Stefan Bodewig wrote:

> On 2017-07-19, Rob Tompkins wrote:

>>> On Jul 19, 2017, at 8:13 AM, Stefan Bodewig <[hidden email]> wrote:

>>> On 2017-07-19, Rob Tompkins wrote:

>>>> The Apache Commons Collections component has been moved to git.

>>> Many thanks for doing that, Rob!

>>> Are you following some kind of playbook with the git migration? If so,
>>> we should add one point:

>>> * edit the svn:externals property of
>>>  https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
>>>  entry for the component just migrated.

>> Good point, and no playbook here. I suppose we should either:
>> 1. create such a playbook, or 2. do the remainder of the repos so that
>> such a playbook is no longer needed. :-)

> True.

> I'm all for option 1 and may find some time over the weekend to start a
> page inside the wiki, based on what I recall doing back when I migrated
> Compress.

Not really weekend anymore. :-)

When I wanted to begin a new page I found this one

https://wiki.apache.org/commons/MovingToGit

Not sure whether everything on it is still accurate, but at least it
contains all the data points that I remembered myself.

Cheers

        Stefan

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

Reply | Threaded
Open this post in threaded view
|

Re: [ANNOUNCE] Apache Commons Collections moved to git

Rob Tompkins

> On Jul 25, 2017, at 5:04 AM, Stefan Bodewig <[hidden email]> wrote:
>
> On 2017-07-21, Stefan Bodewig wrote:
>
>> On 2017-07-19, Rob Tompkins wrote:
>
>>>> On Jul 19, 2017, at 8:13 AM, Stefan Bodewig <[hidden email]> wrote:
>
>>>> On 2017-07-19, Rob Tompkins wrote:
>
>>>>> The Apache Commons Collections component has been moved to git.
>
>>>> Many thanks for doing that, Rob!
>
>>>> Are you following some kind of playbook with the git migration? If so,
>>>> we should add one point:
>
>>>> * edit the svn:externals property of
>>>> https://svn.apache.org/repos/asf/commons/trunks-proper and remove the
>>>> entry for the component just migrated.
>
>>> Good point, and no playbook here. I suppose we should either:
>>> 1. create such a playbook, or 2. do the remainder of the repos so that
>>> such a playbook is no longer needed. :-)
>
>> True.
>
>> I'm all for option 1 and may find some time over the weekend to start a
>> page inside the wiki, based on what I recall doing back when I migrated
>> Compress.
>
> Not really weekend anymore. :-)

Ha….fair point :-)

If I recall correctly Benedikt was the last to update this page when he migrated [cli] over (even as late as last month on 6/28). So I think that it’s fairly up to date, aside from the bit that you did with “trunks-proper” in svn.

I unfortunately don’t have permissions to edit out pages on the wiki (I think that I need some one with the karma to add me). I would guess that it would be a subset of these folks https://wiki.apache.org/commons/ContributorsGroup <https://wiki.apache.org/commons/ContributorsGroup>. I suppose I’ll request access now.

Cheers,
-Rob


>
> When I wanted to begin a new page I found this one
>
> https://wiki.apache.org/commons/MovingToGit <https://wiki.apache.org/commons/MovingToGit>
>
> Not sure whether everything on it is still accurate, but at least it
> contains all the data points that I remembered myself.
>
> Cheers
>
>        Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email] <mailto:[hidden email]>
> For additional commands, e-mail: [hidden email] <mailto:[hidden email]>
Reply | Threaded
Open this post in threaded view
|

git migration guide (was Re: [ANNOUNCE] Apache Commons Collections moved to git)

Stefan Bodewig
On 2017-07-25, Rob Tompkins wrote:

>> When I wanted to begin a new page I found this one

>> https://wiki.apache.org/commons/MovingToGit

> If I recall correctly Benedikt was the last to update this page when
> he migrated [cli] over (even as late as last month on 6/28). So I
> think that it’s fairly up to date, aside from the bit that you did
> with “trunks-proper” in svn.

That's been present already as well.

> I unfortunately don’t have permissions to edit out pages on the wiki
> (I think that I need some one with the karma to add me).

I should be able to do so. What is your account name?

Stefan

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