Release 0.9.0

[aldenpeterson-wf]

Resolves #842

This also adds the automatic generation of the Changelog using github_changelog_generator. This will mean a few things:

1. We will want to be more clear about having detailed PR descriptions as they are automatically added
2. We could choose to not include closed issues without labels to have less clutter. I left (allthethings) here since this is the first changelog generation
3. In the future, releases will be much easier and can happen more frequently because this tool makes it trivial to generate release notes
4. We could replace the entire web changelog with the autogenerated one - I left it as a highlights and link to the full changelog. Thoughts?

When this is merged, someone with pypi access will have to publish the package (as well as tag; I'm not doing so until this is merged and someone else might beat me to it).

[codecov]

Codecov Report

Merging #867 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #867   +/-   ##
=======================================
  Coverage   66.55%   66.55%           
=======================================
  Files          14       14           
  Lines        1438     1438           
  Branches      226      226           
=======================================
  Hits          957      957           
  Misses        430      430           
  Partials       51       51

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6701f70...24a52c3. Read the comment docs.

[mbeacom]

lgtm - 🚢 ?

[cgoldberg]

this is great. Can you add a target to the Makefile for this, so we can make changelog?

[cgoldberg]

we can remove this.

[cgoldberg]

this can be removed.

[aldenpeterson-wf]

Well right now that changelog is still cherry picked - I could update it and say "this is the last release with a changelog manually curated" though and then leave a link to the autogenerated one.

[aldenpeterson-wf]

@cgoldberg I didn't add a Makefile target since right now it's still requiring a manual update step for the curated changelog.

If that ends up being archived, it'd be easier (could literally do make release 0.9.0 type of syntax).

[aldenpeterson-wf]

@heyman @cgoldberg @mbeacom

Anything we can do to speed this along? A ton of people have been asking about the next release and it'd be nice to get this released.

[anhpham1509]

Ping @heyman and @cgoldberg if you have time to do the release this week?

[aldenpeterson-wf]

Can we please have someone with pypi access release this?

We want to use this functionality internally and I don't really want to have to fork/mirror Locust just to be able to let people use functionality that has been in master for almost a year at this point.

I don't even know who to ping at this point to get this released.

[cgoldberg]

i'm going to try to do it tomorrow.

[cgoldberg]

just released 0.9.0 to PyPI:
https://pypi.org/project/locustio/0.9.0/

🎉

done:

• updated Makefile
• landed this PR
• tagged 0.9.0
• built source and wheel distributions
• uploaded dists to PyPI