[pytest-dev] moving to git / issues?

[Bruno Oliveira]

Hi Floris,

> What happens to existing pull requests?  If we don't merge them before
> Sat we have to convert them to git ourself and re-make the PR?

Yes, as there are few PRs and there's no automatic way to do migrate them,
I think that is a reasonable approach. For PRs that; we should ask
submitters to open new PRs in GitHub after the conversion.

> But for #296 I'm preparing a PR at
> https://bitbucket.org/flub/pytest-py35 (because it needed to be
> rebased onto pytest-2.7).  I think I'd prefer to merge that before the
> conversion even if not all tests are fixed by Sat (but hopefully they
> will be!).  Does that sound reasonable?

IMO yes, unless others disagree.

Cheers,


On Wed, Jun 10, 2015 at 8:47 PM Floris Bruynooghe <flub at devork.be> wrote:

> On 10 June 2015 at 14:07, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> > Hi guys,
> >
> > Just wanted to know if everyone is OK with migrating pytest to GitHub
> this
> > Saturday (June 13th).
> > If all agree, I will send an email Saturday when I start the migration
> > process (issues + repository), meanwhile no one should commit to
> BitBucket
> > until the process is complete.
>
> What happens to existing pull requests?  If we don't merge them before
> Sat we have to convert them to git ourself and re-make the PR?
>
> I think I'm happy to decline #271 and #292.
> But for #296 I'm preparing a PR at
> https://bitbucket.org/flub/pytest-py35 (because it needed to be
> rebased onto pytest-2.7).  I think I'd prefer to merge that before the
> conversion even if not all tests are fixed by Sat (but hopefully they
> will be!).  Does that sound reasonable?
>
>
> Floris
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150611/c26794a4/attachment.html>