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

[Brett Cannon]

On Fri, 3 Feb 2017 at 16:25 Ned Deily <nad at python.org> wrote:

> On Feb 3, 2017, at 19:16, Brett Cannon <brett at python.org> wrote:
> > On Fri, 3 Feb 2017 at 16:06 Ned Deily <nad at python.org> wrote:
> >> 2. What about Misc/NEWS entries?  Are we going to continue to ask
> committers to use the old format (Issue #nnnnn) there?  Note these are
> currently auto-linked in the docs builds, e.g.
> https://docs.python.org/3.6/whatsnew/changelog.html.
> > Don't know. My expectation is that long term we won't even specify them
> in the entry itself and it will be part of the filename when we move to a
> file-per-entry solution.
>
> That would be nice long-term.  I guess we just need to be clear during the
> immediate transition what the expectation for committers are about what
> forms they need to use in the commit messages and in Misc/NEWS.  That needs
> to be spelled out in transition announcements and in the devguide to
> minimize confusion, especially if they will no longer be the same, e.g
> "bpo-NNNNN" in the commit message but "Issue #NNNNN" in Misc/NEWS.
>

I checked how the changelog is automatically linked for
https://docs.python.org/3/whatsnew/changelog.html and it looks like it
would be easy to add support for both the old format and the new one (as
well as unifying the format in the output so they all say "bpo-NNNN"; see
https://github.com/python/cpython/blob/master/Doc/tools/extensions/pyspecific.py#L226).
Between that and updating the hooks on bugs.python.org for making the
connection we should be able to use the new prefix from day 1.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20170206/bec6ecfb/attachment.html>