Streamlining the Release process

[andrewgy8]

Boy oh boy, that release process was a doozy. Anybody have experience with making the release process easier to compose?

To create 0.4.0, I had to,

• Bump the __version__
• Create the changelog
• Create the release on github which was basically a copy/pasta of the changelog
• make release on my machine.

Needless to say, there was a lot of room for error and improvement.

What would be nice to have is a:

• more automated process that bumps, tags and creates the release on github
• a release notes section in the docs

This for sphinx documentation https://releases.readthedocs.io/en/latest/ This for versioning https://github.com/c4urself/bump2version This for changelog generation https://github.com/vaab/gitchangelog

Any other sources? Experiences?

[daniel-ruiz]

I see the guys maintaining marshmallow have a releasing guide that seems pretty simple to follow. Maybe we can learn a few things from them 😄

[andrewgy8]

Good source @daniel-ruiz ! They also have fairly simple travis build which does use tox. https://github.com/marshmallow-code/marshmallow/blob/dev/.travis.yml

[andrewgy8]

Just because they have removed it from their repo, here is the travis file https://github.com/marshmallow-code/marshmallow/commit/ead95c2624b66ec9ab2fa9c83b55e60929599c2a

Curious that they migrated from travis to azure pipelines. Seems to be the number of parallel jobs for OS projects. The azure pipelines yaml also looks very simple.