<p dir="ltr">Sounds like a good plan!<br>
It's easier to implement it by one person I think and that person is you! :)</p>
<br><div class="gmail_quote">On 05:46, Sat, Jun 6, 2015 Bruno Oliveira <<a href="mailto:nicoddemus@gmail.com">nicoddemus@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Implemented the last suggestions by Florian, I think issue migration looks good now.<br><br>What would be the next steps? I suggest the following list (from the top of my head):<div><br></div><div>1. Create <a href="http://github.com/pytest-dev/pytest" target="_blank">github.com/pytest-dev/pytest</a> and move issues (better do this first so the migrated issues have the same id as the original ones);</div><div>2. Convert pytest Hg repository to Git and upload to GitHub;</div><div><span style="line-height:1.5;font-size:13.1999998092651px">3. Add to bitbucket's README a notice about the move to GitHub, and that new issues/PRs should be posted there;</span></div><div><span style="line-height:1.5;font-size:13.1999998092651px">4. Update all links in the documentation and PyPI;</span></div><div><span style="line-height:1.5;font-size:13.1999998092651px">5. Update "how to contribute" docs;</span></div><div><span style="line-height:1.5;font-size:13.1999998092651px">6. Upload new docs to <a href="http://pytest.org" target="_blank">pytest.org</a>;</span></div><div><span style="font-size:13.1999998092651px;line-height:1.5">7. Ask </span>submitters<span style="font-size:13.1999998092651px;line-height:1.5"> to re-create PRs at the new repository;</span></div><div><span style="line-height:1.5;font-size:13.1999998092651px">8. Send an email to all relevant mailing lists about the migration;</span></div><div><br></div><div>After the migration process is complete, we can start to take advantage of GitHub's ecosystem, for example start using Travis for CI, code coverage with <a href="http://coveralls.io" target="_blank">coveralls.io</a>, etc.</div><div><span style="line-height:1.5;font-size:13.1999998092651px"><br></span></div><div><span style="line-height:1.5;font-size:13.1999998092651px">IMO all this must be done in a short time, because if we start the migration process and stall without completing it, links, issues, PRs etc might get out of sync, so it it is better to gather a few contributors and choose a "Migration Sprint" day to start and finish all the steps required for a full migration.</span></div><div><span style="line-height:1.5;font-size:13.1999998092651px"><br></span></div><div><span style="line-height:1.5;font-size:13.1999998092651px">Cheers,</span></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jun 5, 2015 at 12:33 PM Bruno Oliveira <<a href="mailto:nicoddemus@gmail.com" target="_blank">nicoddemus@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Fri, Jun 5, 2015 at 1:19 AM Florian Bruhin <<a href="mailto:me@the-compiler.org" target="_blank">me@the-compiler.org</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> When doing the final migration, which user should we use?<br>
<br>
I suggest creating a new user for the migration so it's immediately<br>
apparent that's not the real issue author. </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For example, a pytest-dev/pytest-bot/pytest-issue-migration/... user<br>
with the pytest logo as avatar.<br></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>Yes, that seems like a good solution. :)</div><div><br></div><div>About your other suggestions, I agree with most of them and created an issue with your points here: <a href="https://github.com/nicoddemus/bitbucket_issue_migration/issues/2" target="_blank">https://github.com/nicoddemus/bitbucket_issue_migration/issues/2</a></div><div><br></div><div>There are only two which I don't think are worth the effort:</div><div><br></div><div>- Porting PRs seems to be tricky, since we would have to port the patches as well; </div><div>- Update the changesets that appear in issues/comments: since those changesets will be different when we convert from Mercurial to Git, there's no easy way to map them;</div><div><br></div><div>If others have any more suggestions, feel free to comment here or at <a href="https://github.com/nicoddemus/bitbucket_issue_migration/issues/2" target="_blank">https://github.com/nicoddemus/bitbucket_issue_migration/issues/2</a>.</div><div><br></div><div>Cheers,</div></div></div><div dir="ltr"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think the "Bitbucket / originally reported by" footer should be at<br>
the top (before the issue text) instead - again so it's immediately<br>
apparent what's going on.<br>
<br>
Also, stuff inside <> seems to be removed?<br>
See <a href="https://github.com/nicoddemus/pytest-issues-migration/issues/6#issuecomment-109143858" target="_blank">https://github.com/nicoddemus/pytest-issues-migration/issues/6#issuecomment-109143858</a><br>
for example.<br>
<br>
Some other ideas which might or might not be worth the effort:<br>
<br>
- Rewrite full links to an issue (as opposed to #nnn identifiers) to<br>
point to the correct/new location (or to use #nnn instead)<br>
<br>
- Rewrite links to PRs, if PRs will be migrated<br>
<br>
- Rewrite those "-> <<cset ...>>" comments to point at git commits<br>
(when the repo is migrated) instead of hg changesets).<br>
(See link above for a [broken] example)<br>
<br>
Florian<br>
<br>
--<br>
<a href="http://www.the-compiler.org" target="_blank">http://www.the-compiler.org</a> | <a href="mailto:me@the-compiler.org" target="_blank">me@the-compiler.org</a> (Mail/XMPP)<br>
GPG: 916E B0C8 FD55 A072 | <a href="http://the-compiler.org/pubkey.asc" target="_blank">http://the-compiler.org/pubkey.asc</a><br>
I love long mails! | <a href="http://email.is-not-s.ms/" target="_blank">http://email.is-not-s.ms/</a><br>
</blockquote></div></div></blockquote></div>
_______________________________________________<br>
pytest-dev mailing list<br>
<a href="mailto:pytest-dev@python.org" target="_blank">pytest-dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/pytest-dev" target="_blank">https://mail.python.org/mailman/listinfo/pytest-dev</a><br>
</blockquote></div>