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

[M.-A. Lemburg]

On 01.02.2017 20:02, Ned Deily wrote:
> On Feb 1, 2017, at 12:43, Brett Cannon <brett at python.org> wrote:
>> Historically commit messages for CPython have had the form of "Issue #NNNN: did something". The problem is that Github automatically links "#NNNN" to GitHub issues (which includes pull requests). To prevent incorrect linking we need to change how we reference issue numbers.
>>
>> The current candidates are:
>>
>>    issue NNNN (notice the lack of #)
> 
> +1 
> 
> That form, as well as issueNNNN (no space), is already recognized in comments on bugs.python.org and autogenerates a link to the bug.

+1

> https://docs.python.org/devguide/triaging.html#generating-special-links-in-a-comment

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Feb 01 2017)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
                      http://www.malemburg.com/