Hi, I noticed Bruno created an issue to say that they should now be reported on github instead. I was wondering if we should maybe simply disable issue tracking completely? I've just experimented with this in a test repo and it seems you can no longer access issues when you disable it, however if you then re-enable the issues they are all still there.
Also related, do we leave the code there? Why not fully delete the repo and redirect? On 16 June 2015 at 00:25, Bruno Oliveira <nicodde...@gmail.com> wrote: > Hi everyone, > > Here's the list of the tasks done for the move to GitHub: > https://github.com/pytest-dev/pytest/issues/769 > > If you see any obsolete link or documentation piece that needs to be > updated, please don't refrain to point it out or creating a PR. > > Cheers, > > On Mon, Jun 15, 2015 at 6:07 PM Bruno Oliveira <nicodde...@gmail.com> wrote: >> >> Hi everyone, >> >> We have our new repository ready: >> >> https://github.com/pytest-dev/pytest >> >> Issues and commits may now continue on the new repository. >> >> The few remaining tasks to fully complete the move are listed here: >> https://github.com/pytest-dev/pytest/issues/769 >> >> Thanks everyone for your patience! >> >> Cheers, >> >> >> >> On Mon, Jun 15, 2015 at 5:31 PM Bruno Oliveira <nicodde...@gmail.com> >> wrote: >>> >>> Hi everyone, >>> >>> The migration process has started now. I will send an email once the >>> first steps are complete. >>> >>> Cheers, >>> >>> On Mon, Jun 15, 2015 at 9:59 AM Bruno Oliveira <nicodde...@gmail.com> >>> wrote: >>>> >>>> Hi everyone, >>>> >>>> Today we will migrate the pytest repository from bitbucket (Hg) to >>>> GitHub (Git), sometime after 6pm (GMT -03:00). >>>> >>>> Until then feel free to commit and handle issues as usual, but when the >>>> process starts please refrain to make any changes to issues or new commits >>>> until the process finishes. I will send an email to this list when the >>>> process officially starts, and it is expected to take no longer than 1 hour >>>> before normal work, now on the new repository, can resume. >>>> >>>> For those interested, here are the steps for the migration: >>>> >>>> 1. Create github.com/pytest-dev/pytest and move current issues; >>>> 2. Convert pytest Hg repository to Git and upload to GitHub; >>>> 3. Add to bitbucket's README a notice about the move to GitHub, and that >>>> new issues/PRs should be posted there; >>>> >>>> (At this point, work on the new repository can resume) >>>> >>>> 4. Ask submitters to re-create PRs at the new repository; >>>> 5. Update all links in the documentation and PyPI; >>>> 6. Update "how to contribute" docs; >>>> 7. Upload new docs to pytest.org; >>>> 8. Send an email to all relevant mailing lists about the migration; >>>> >>>> Suggestions and comments are welcome! >>>> >>>> Cheers, > > > _______________________________________________ > pytest-dev mailing list > pytest-dev@python.org > https://mail.python.org/mailman/listinfo/pytest-dev > _______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
