Thanks, I'll have a look. This should definitely save us some time :)
On Fri, Jun 14, 2013 at 6:29 PM, Koper, Dies <[email protected]>wrote: > Hi Tomaz, > > > change slightly. I will work on writing a new committer and > contributor > > guide this weekend. > > You may be aware of it but in case you weren't, Deltacloud has their > workflow described here [1] and jclouds, which recently joined the ASF, > is using it too. Maybe you can use it as a starting point. > > [1] https://github.com/deltacloud/deltacloud-core/wiki/GIT-Workflow > > Regards, > Dies Koper > > > > -----Original Message----- > > From: Tomaz Muraus [mailto:[email protected]] > > Sent: Saturday, 15 June 2013 9:18 AM > > To: [email protected] > > Subject: Re: [dev] Migrating from svn to git (svn tree will be read > only > > until migration has completed, need help with auditing the new git > > repository) > > > > I just wanted to let everyone know that the migration has been > successfully > > completed. > > > > Our new writable git repository url is now available at > > https://git-wip-us.apache.org/repos/asf/libcloud.git ( > > https://git-wip-us.apache.org/repos/asf?p=libcloud.git). Old svn code > > repository is now read-only and deprecated. > > > > Using git means that workflow for both, committers and contributors > will > > change slightly. I will work on writing a new committer and > contributor > > guide this weekend. > > > > One of the more important changes is that we can now preserve the > original > > commit author. Committer who is merging the patch will just need to > sign > > it > > off. More details about signing off and other things will be available > > in > > the new committer guide. > > > > On Wed, Jun 12, 2013 at 3:35 PM, Tomaz Muraus <[email protected]> > wrote: > > > > > Thanks for the cross check. > > > > > > I'm not sure if and how this will affect Github mirror, but I will > ask > > > this in the INFRA ticket. > > > > > > > > > On Wed, Jun 12, 2013 at 3:03 PM, John Carr <[email protected]> > wrote: > > > > > >> +1, looks good to me. > > >> > > >> Will this affect the GitHub mirror? > > >> > > >> Cheers, > > >> > > >> > > >> On 12 Jun 2013, at 22:30, Tomaz Muraus <[email protected]> wrote: > > >> > > >> > I've created a new infrastructure ticket to migrate main Libcloud > > code > > >> > repository from svn to git. ( > > >> > https://issues.apache.org/jira/browse/INFRA-6383). > > >> > > > >> > David Nalley has already started working on it and as a > consequence > > svn > > >> > tree will be read only until the migration has been completed. > > >> > > > >> > David has created a new git repository which is located at > > >> > https://git-wip-us.apache.org/repos/asf/libcloud.git. Until the > > >> migration > > >> > has finished this new repository will also be read-only. > > >> > > > >> > Our job is to verify / audit that everything looks correct (all > the > > >> > commits, branch and tags are present). I already verified it > myself, > > >> but it > > >> > would be great if couple of more people cross-check it. > > >> > > > >> > I did the following and cross-checked it with the svn repository: > > >> > > > >> > git clone https://git-wip-us.apache.org/repos/asf/libcloud.git > > lc-git > > >> > cd lc-git > > >> > git branch -a > > >> > git tag > > >> > git log remotes/origin/0.12.x > > >> > git log 0.12.3 > > >> > ... > > >> > > > >> > As soon as I get a couple of more +1's / look good to me I will > update > > >> the > > >> > ticket and new Git repository will be made writable. > > >> > > > >> > Thanks! > > >> > > >> > > > > >
