blurb won't let me create a NEWS entry without a bpo issue number

[gpshead]

When I'm making a minor enhancement to something am I required to file a bugs.python.org issue?!?

What a waste.

Please support the less common news blurbs that do not have an associated bpo issue.

[larryhastings]

This was dictated by @brettcannon

[gpshead]

A valid way to close this would be to document the requirement in the devguide. I looked for something saying that but didn't find it. Granted i also didn't see blurb mentioned their either so I may not have found the right place.

[Mariatta]

I don't remember the whole conversation, but I recall the decision is that unless it is trivial typo fixes, then everything else should need an issue number in bpo.
In the quick start guide, creating an issue is the first step. https://devguide.python.org/pullrequest/#quick-guide

[brettcannon]

The decision was if it requires a news entry then we need a place to track anything related to the change, and that place is bugs.python.org.

As for where to mention this, there's https://devguide.python.org/pullrequest/ for how to create a pull request and https://devguide.python.org/committing/ on accepting a pull request. It's the latter that explicitly mentions blurb. It seems that the former needs a touch-up for blurb and the required issue number bit if something calls for a news entry.