[core-workflow] Migration PEP started

[Brett Cannon]

On Mon, 11 Jan 2016 at 23:52 Oleg Broytman <phd at phdru.name> wrote:

> Hi!
>
> On Tue, Jan 12, 2016 at 12:25:06AM +0000, Brett Cannon <brett at python.org>
> wrote:
> > PEP is still not done, but I have at least fleshed out the parts required
> > to migrate the code-only and web-related repositories:
> >
> https://github.com/brettcannon/github-transition-pep/blob/master/pep-NNNN.rst
> .
>
> > Continuous integration per pull request
> > XXX https://travis-ci.org/ https://codeship.com/ https://circleci.com/
>
>    No buildbot?
>

Buildbot serves a different purpose. This unfinished item is for CI for
every submitted pull request while Buildbot is for verifying that the
repository on key branches is in a good state.


>
> > Tools and commands to move from Mercurial to Git
> > A decision needs to be made on exactly what tooling and what commands
> > involving those tools will be used to convert a Mercurial repository to
> > Git. Currently a suggestion has been made to use
> > https://github.com/frej/fast-export.
>
>    My personal experience with fast-export was a bit negative when I
> tried to convert a repository for a complex project with a number of
> branches and a lot of tags. I switched to git-remote-hg [1] and found it
> much better for my needs. See Comparison [2].
>
> 1. https://github.com/felipec/git-remote-hg
> 2.
> https://github.com/felipec/git/wiki/Comparison-of-git-remote-hg-alternatives


I'll add it to the list of options.

-Brett


>
>
> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            phd at phdru.name
>            Programmers don't die, they just GOSUB without RETURN.
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160112/292da9e5/attachment.html>