Moving Core to the incubator

[David Lutterkort]

Hi all,

as you may have heard, Deltacloud Core is moving to the Apache
incubator[1]

There's two key things in that move that I want to get done in the next
few days:

1. Move mailing lists
=====================

Move all mailing list traffic for Deltacloud Core to the Apache list[2]
- from now on, all discoussions, patches, gripes, offers of large
amounts of money etc. concerning the Detlacloud API should go to
[e-mail] (nothing will change for the
aggregator/portal) Please subscribe to that list.

2. Import code into subversion
===============================

Import the code into subversion[3]; a git mirror of the subversion repo
will be available in short order. I've tested the conversion and am
hopeful that I can get it committed 'for reals' today or tomorrow.

The conversion does a few nasty things (filter-branch to get rid of
vendored rails, rebase of the master branch on top of Apache's
subversion), so that the subversion repo will be a new repo, with no
direct connection to the existing git repo, even though the commits will
be (mostly) the same. I will put a tag on the master branch in the
existing repo to mark where exactly I did the import from.

That means that if you are using the current git repo, you will have to
clone the Apache repo as if it were brand new; it's probably easiest to
use git-format-patch and git-am to carry over any private branches you
may have.

I'll post again once I have the code in the Apache repo.

David

[1] http://incubator.apache.org/projects/deltacloud.html
[2] http://mail-archives.apache.org/mod_mbox/incubator-deltacloud-dev/
[3] https://svn.apache.org/repos/asf/incubator/deltacloud/

[Jon Masters]

On Wed, 2010-07-07 at 16:18 -0700, David Lutterkort wrote:
> Move mailing lists
>
> =====================
>
> Move all mailing list traffic for Deltacloud Core to the Apache list[2]
> from now on, all discoussions, patches, gripes, offers of large
>
> amounts of money etc. concerning the Detlacloud API should go to
> [e-mail] (nothing will change for the
> aggregator/portal) Please subscribe to that list.

Please include instructions for subscribing to the list. In this case,
the following is recommended by the apache website but does not seem to
work for this "incubator" project:

Unless otherwise noted, these lists are managed by ezmlm, which means
that if you want to subscribe to

[e-mail]

then you need to send a message to

[e-mail]

To get off a list, send a message to

[e-mail]

Jon.

[David Lutterkort]

On Thu, 2010-07-08 at 03:01 -0400, Jon Masters wrote:
> On Wed, 2010-07-07 at 16:18 -0700, David Lutterkort wrote:
> > Move mailing lists
> >
> > =====================
> >
> > Move all mailing list traffic for Deltacloud Core to the Apache list[2]
> > from now on, all discoussions, patches, gripes, offers of large
> >
> > amounts of money etc. concerning the Detlacloud API should go to
> > [e-mail] (nothing will change for the
> > aggregator/portal) Please subscribe to that list.
>
> Please include instructions for subscribing to the list. In this case,
> the following is recommended by the apache website but does not seem to
> work for this "incubator" project:
>
> Unless otherwise noted, these lists are managed by ezmlm, which means
> that if you want to subscribe to
>
> [e-mail]
>
> then you need to send a message to
>
> [e-mail]
>
> To get off a list, send a message to
>
> [e-mail]

Note that to subscribe, you need to send email to
[e-mail] (there is an 'incubator'
in the email address)

David

[Jon Masters]

On Thu, 2010-07-08 at 11:58 -0700, David Lutterkort wrote:
> Note that to subscribe, you need to send email to
> [e-mail] (there is an 'incubator'
> in the email address)

That works, thanks. Please ask them to make the website more clear, and
add this information to the project webpage.

Jon.

[David Lutterkort]

[ This will be my last cross post to both lists ]

On Wed, 2010-07-07 at 16:18 -0700, David Lutterkort wrote:
> Import the code into subversion[3]; a git mirror of the subversion repo
> will be available in short order. I've tested the conversion and am
> hopeful that I can get it committed 'for reals' today or tomorrow.

I've finally imported the code from
git://git.fedorahosted.org/git/deltacloud/core.git into the Apache
subversion repository at
https://svn.apache.org/repos/asf/incubator/deltacloud/trunk
> From now on, all development will happen against this subversion

repository. We’re still waiting for the official readonly git mirror to
be set up — for now, you will have to make do with git svn. If you have
an existing git checkout, you will unfortunately have to throw that
away, and check out from scratch:

mkdir deltacloud
        cd deltacloud
        git svn init -s https://svn.apache.org/repos/asf/incubator/deltacloud
        git svn fetch

I've tagged the commit up to which the conversion went with
'repo-closed' - I might, in the next few days, go and git rm everything
in that repo, leaving only a text file pointing to the svn repo.

David

[Michal Fojtik]

On 08/07/10 17:29 -0700, David Lutterkort wrote:
> From now on, all development will happen against this subversion
> repository. We’re still waiting for the official readonly git mirror to
> be set up — for now, you will have to make do with git svn. If you have
> an existing git checkout, you will unfortunately have to throw that
> away, and check out from scratch:
>    mkdir deltacloud
>    cd deltacloud
>    git svn init -s https://svn.apache.org/repos/asf/incubator/deltacloud
>    git svn fetch

I'm not sure if I not doing something wrong, but last step is taking about
one hour for me ;-)

mfojtik ~/code $ mkdir core
mfojtik ~/code $ cd core/
mfojtik ~/code/core $ git svn init -s
https://svn.apache.org/repos/asf/incubator/deltacloud
Initialized empty Git repository in /home/mfojtik/code/core/.git/
Using higher level of URL:
https://svn.apache.org/repos/asf/incubator/deltacloud =>
https://svn.apache.org/repos/asf
mfojtik ~/code/core $ git svn fetch
W: Ignoring error from SVN, path probably does not exist: (160013):
Filesystem has no item: File not found: revision 100, path
'/incubator/deltacloud'
W: Do not be alarmed at the above message git-svn is just searching
aggressively for old history.
This may take a while on large repositories
Checked through r643600
> I've tagged the commit up to which the conversion went with
> 'repo-closed' - I might, in the next few days, go and git rm everything
> in that repo, leaving only a text file pointing to the svn repo.
>
> David

[Chris Lalancette]

On 07/12/10 - 10:57:44AM, Michal Fojtik wrote:
> On 08/07/10 17:29 -0700, David Lutterkort wrote:
> > From now on, all development will happen against this subversion
> > repository. We’re still waiting for the official readonly git mirror to
> > be set up — for now, you will have to make do with git svn. If you have
> > an existing git checkout, you will unfortunately have to throw that
> > away, and check out from scratch:
> >   mkdir deltacloud
> >   cd deltacloud
> >   git svn init -s https://svn.apache.org/repos/asf/incubator/deltacloud
> >   git svn fetch
>
> I'm not sure if I not doing something wrong, but last step is taking about
> one hour for me ;-)
>
> mfojtik ~/code $ mkdir core
> mfojtik ~/code $ cd core/
> mfojtik ~/code/core $ git svn init -s
> https://svn.apache.org/repos/asf/incubator/deltacloud
> Initialized empty Git repository in /home/mfojtik/code/core/.git/
> Using higher level of URL:
> https://svn.apache.org/repos/asf/incubator/deltacloud =>
> https://svn.apache.org/repos/asf
> mfojtik ~/code/core $ git svn fetch
> W: Ignoring error from SVN, path probably does not exist: (160013):
> Filesystem has no item: File not found: revision 100, path
> '/incubator/deltacloud'
> W: Do not be alarmed at the above message git-svn is just searching
> aggressively for old history.
> This may take a while on large repositories
> Checked through r643600

Yeah, it took an hour for me as well.  It did eventually complete, though.
It would be nice to see if we can make this faster, since an hour is a bit
ridiculous :).

--
Chris Lalancette