[core-workflow] Choosing a prefix/label for issue numbers

[Brett Cannon]

On Wed, 1 Feb 2017 at 15:45 Ned Deily <nad at python.org> wrote:

> On Feb 1, 2017, at 18:14, Brett Cannon <brett at python.org> wrote:
> > On Wed, 1 Feb 2017 at 14:34 Ned Deily <nad at python.org> wrote:
> >> On Feb 1, 2017, at 16:35, Brett Cannon <brett at python.org> wrote:
> >> > On Wed, 1 Feb 2017 at 12:23 Ned Deily <nad at python.org> wrote:
> >> >> Perhaps I'm misunderstanding something. Are we planning to alter
> existing commit messages as part of the hg to fit transition?
> >> > No, we are not mucking with the history as part of the transition.
> >>
> >> Sorry, I don't mean to resurrect any old discussions that I've
> forgotten about here but, just to be clear, that means that we will no
> longer be able to click through from the web pages of the tens of thousands
> of old commits back to their corresponding bug web pages as we can do today?
>
>
> > Correct. You will have to copy-and-paste the issue number into a URL.
>
> > For example, https://hg.python.org/cpython/rev/aa7ac93d23b2
> (eventually) links back to https://bugs.python.org/issue20185 (at least
> it should if the SSL certificate weren't expired today), whereas the
> corresponding git commit (
> https://github.com/python/cpython/commit/9f889393ab0362229c42bc31056f3ef9735a1d27)
> does not
> > and will not provide a link back?  That's ... unfortunate.
> >
> > For old issues that won't be a possibility, but for new issues it can be
> done. E.g.
> https://github.com/python/the-knights-who-say-ni/commit/aa82ec527570f8cf1b6ae13037ba6535afe26e5a
> links to the PR that the commit came from and the PR can have a link back
> to the referenced issue(s). If you really miss this then someone could
> always volunteer to stand up their own web server to server commit history
> with the desired functionality, but I don't think this is important enough
> to block the migration over as you're now asking that we figure out how to
> hack the migrated git history to embed URLs to a non-existent reflector
> like hg.python.org/lookup but for issue numbers. If we were also
> migrating the issue tracker then it would be possible as they would
> probably link to the GitHub issue number.
>
> Understood.  And I'm not asking that this block the migration; now that it
> is about to happen, I (and the rest of the community) have to wrap our
> brains around the way things will work.  It was easier to avoid doing that
> earlier and let you and the others doing all the hard work figure it all
> out.  I deeply appreciate your efforts!
>

I'm sure you do and if I implied I thought otherwise I apologize. It's just
a bit late to find something "unfortunate" unless it's so bad as to require
stopping the process.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20170202/fd0054b5/attachment-0001.html>