Publish a new version to PYPI

[Powersource]

It would be nice to have a release with #40 included so I'd stop getting the warnings 😄

[lskillen]

@sigmavirus24 Sorry, I know you're busy, but "hear hear" to the above too. :-) We've been using a branch to get a release with accepted PRs, but an official release would be just that bit nicer. Thank you!

[tacaswell]

Is there anything I can do to help with this?

[brettcannon]

I'm also willing to help with @tacaswell to create a new release as the collections.abc issue is becoming a bit more pressing.

[sigmavirus24]

@brettcannon what's your PyPI username? You're already a hyper member so I can just add you to PyPI so you can release it

[brettcannon]

@sigmavirus24 brettcannon

[tacaswell]

@brettcannon Ping me on email if you want me to do anything.

[brettcannon]

@tacaswell Thanks! I'll let you know if I need anything after @sigmavirus24 gives me a copy of the keys. 😄

[sigmavirus24]

@brettcannon you should have been given the ability to craft releases.

[brettcannon]

Things to do for the release:

• Update LICENSE to say uritemplate instead of uritemplate.py (PR Update the project name in the LICENSE #44)
• Update tox.ini for Python 3.7 and 3.8 (PR Update support for Python 3.7 & 3.8 #45)
• Update .travis.yml for Python 3.7 and 3.8 (PR Update support for Python 3.7 & 3.8 #45)
• Update trove classifiers (PR Update support for Python 3.7 & 3.8 #45)
• Update HISTORY.rst (PR Update history #46 )
• Bump version number appropriately based on what has changed (PR Bump version number to 3.0.1 #47 )
• Verify CI is passing
• Go over everything once more with @tacaswell to make sure nothing has been missed
• Create a PR updating the publish date in HISTORY.rst (Update HISTORY.rst for planned 3.0.1 release #49 )
• Push a new release to PyPI
• Merge the change to HISTORY.rst
• Ask @sigmavirus24 to tag a new release here on the repo

[sigmavirus24]

Do we actually want to block a release on that list or do we want to do a release now and address that afterwards as a fast follow?

[brettcannon]

@sigmavirus24 I personally don't need a release that badly, and at least the first three + trove classifiers seem important to fix for the release itself (especially if there won't be a release that often).

[brettcannon]

Just a quick update for folks: coding is done so that uritemplate has support through Python 3.8. Next bit is updating the the history/changelog and then bumping the version number appropriately based on what the history suggests. After that it's administrative release stuff.