I actually committed the migration scripts to trunk in the scripts/
folder just in case of emergency.  There's lots of references
to /home/owen in them -- I left those unedited on purpose.  I didn't
want to put the scripts there and have people think they could just run
the scripts blind.  But feel free to look at them to see how the import
process works.

No, it doesn't make sense to migrate all of the branches. I actually did
migrate a whole raft of them under the mixxxdj/community repo, but we
should probably delete them because github doesn't know that they were
forked from mixxxdj/mixxx.  (RJ, should I go ahead and delete that
repo?)

I would prefer to just migrate on demand -- file a bug in launchpad
saying you want a branch moved over and I'll do it.  You can then fork
that repo on github and start working on it.

RJ, go ahead and create a new mixxxcommunity user on github.  I think
that's the way to go.  

Owen


On Thu, 2013-06-13 at 00:45 +0200, Daniel Schürmann wrote:
> Hi RJ, 
> 
> 
> Fine news!
> 
> Mixxx has 122 active Launchpad branches. Does it really make sense to
> convert all of them to git? In which condition is the Owens converter?
> Is it possible to provide it, so that we can convert branches when
> required by ourselves? 
> 
> 
> The normal git workflow is to clone the repository and then maintain
> private branches inside the cloned repository. It would be nice to
> have a way to put the private bzr branches into the private Git
> clone. 
> 
> 
> If I understand it right, git has user credentials per repository
> while bzr has it per branch, we should deal with it.  
> 
> --
> 
> 
> How is the solution for the bug references? Is there a special trick
> or should put them into the commit message only?
> 
> 
> 
> Kind regards, 
> 
> 
> Daniel 
> 
> 
> 
> 
> 
> 
> 2013/6/12 RJ Ryan <rr...@mixxx.org>
>         Hi all,
>         
>         
>         Just wanted to give a status update on the Git migration.
>         We're almost done!
>         
>         
>         https://github.com/mixxxdj/mixxx
>         
>         
>         tl:dr -- stop committing to Launchpad. Make a GitHub account
>         and fork the Mixxx repo. Push changes and personal branches to
>         your forks and make pull requests to get them merged into the
>         master Mixxx branch.
>         
>         
>         We've been using GitHub to discuss a few recent branch merges
>         and the result has been outstanding. It is much easier to
>         discuss and review branch merge proposals. The number of
>         comments the recent merges have received has far outpaced the
>         comments merge proposals on Launchpad received. 
>         
>         
>         * Build system / Build server
>         
>         
>         The build system and build server now produces packages using
>         Git. 
>         
>         
>         * Website 
>         
>         
>         Some references to Bazaar need to be updated.
>         
>         
>         * Wiki 
>         
>         
>         I've updated various pages on the wiki to remove
>         non-historical references to Bazaar from the wiki. The
>         compilation instructions (though not tested) are updated and
>         we have a new Using Git
>         article: http://mixxx.org/wiki/doku.php/using_git
>         
>         
>         * Branch migration, author rewrites 
>         
>         
>         Owen has whipped up a quite fancy branch migration system that
>         automatically does the author rewriting we discussed
>         previously. Unfortunately, due to author rewriting you cannot
>         convert your branch yourself using git-bzr-ng or a similar
>         tool! 
>         
>         
>         We are going to copy every branch on
>         http://code.launchpad.net/mixxx to GitHub but we are still
>         figuring out where they should go. I think they will clutter
>         up the mixxxdj/mixxx branch list so we may create a
>         mixxxcommunity/mixxx repo to put them all in. You will have to
>         clone that repo to get your branch. We'll announce details
>         once Owen decides how to do it.
>         
>         
>         Please clone the Mixxx GitHub repo and give it a try. If you
>         have never used Git before, there are tons of great resources
>         for learning out there. I've linked some of them at the bottom
>         of http://mixxx.org/wiki/doku.php/using_git
>         
>         
>         Please stop committing to Bazaar and push all of your latest
>         changes to Bazaar branches you would like converted. Contact
>         either Owen or I if you have any problems. 
>         
>         
>         Also, please help me in updating out of date or wrong
>         information about Bzr / Git on the wiki. If you find the
>         compilation instructions are not working, please update them.
>         
>         
>         This would not have happened if Owen hadn't stepped up to take
>         charge of the migration. Thanks Owen!
>         
>         
>         Best regards,
>         RJ
>         
>         
>         
> ------------------------------------------------------------------------------
>         This SF.net email is sponsored by Windows:
>         
>         Build for Windows Store.
>         
>         http://p.sf.net/sfu/windows-dev2dev
>         _______________________________________________
>         Get Mixxx, the #1 Free MP3 DJ Mixing software Today
>         http://mixxx.org
>         
>         
>         Mixxx-devel mailing list
>         Mixxx-devel@lists.sourceforge.net
>         https://lists.sourceforge.net/lists/listinfo/mixxx-devel
> 
> 



------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org


Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to