<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, 3 Feb 2017 at 16:06 Ned Deily <<a href="mailto:nad@python.org">nad@python.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Feb 3, 2017, at 18:24, Brett Cannon <<a href="mailto:brett@python.org" class="gmail_msg" target="_blank">brett@python.org</a>> wrote:<br class="gmail_msg">
> It looks like people in general prefer "bpo-NNNN" (sorry, Ned and MAL).<br class="gmail_msg">
<br class="gmail_msg">
I'll live. :)<br class="gmail_msg">
<br class="gmail_msg">
> Maciej, can we update the requisite regexes so that bpo-NNNN is acceptable in PR titles, PR comments, and commit messages?<br class="gmail_msg">
<br class="gmail_msg">
Two things:<br class="gmail_msg">
<br class="gmail_msg">
1. What about Maciej's earlier comment:<br class="gmail_msg">
<br class="gmail_msg">
On Feb 2, 2017, at 16:20, Maciej Szulik <<a href="mailto:soltysh@gmail.com" class="gmail_msg" target="_blank">soltysh@gmail.com</a>> wrote:<br class="gmail_msg">
> Hmm... for all the #NNN in commits we'll get quite a few false links in github, so maybe removing the # would<br class="gmail_msg">
> be valuable, or replacing it with issue/bpo.<br class="gmail_msg">
<br class="gmail_msg">
I'm guessing that's gonna be a ugly usability issue if all the old github commit pages offer invalid links for all of the old #nnnnn references. Or am I missing something there?<br class="gmail_msg"></blockquote><div><br></div><div>See Senthil's comment. It seems doable if we want to do it and can agree on the regex to use to transform them.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="gmail_msg">
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. <a href="https://docs.python.org/3.6/whatsnew/changelog.html" rel="noreferrer" class="gmail_msg" target="_blank">https://docs.python.org/3.6/whatsnew/changelog.html</a>.<br class="gmail_msg"></blockquote><div><br></div><div>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. </div></div></div>