Release 1.0.1

[Thrameos]

• Start from the release branch
  git checkout release
• Make a new branch for the release cycle
  git checkout -b releases/{version}
• Merge the current master with the release
  git pull origin master
• Edit doc/CHANGELOG.rst
• Start a release
  bumpversion release
• Send the release to be evaluated
  git push
• Verify CI on azure
• Manually trigger a jpype.release on azure
  If successful, download the artifacts for publication.
• Advance the release pointer
  git checkout release
git merge releases/<version>
• Publish the release
  • Add draft release on github
  • Attach the artifacts to the release.
• Start master on a new cycle
  • Use a PR to pull release back to master
  • git checkout master
  • git checkout -b cycle
  • git merge release
  • bumpversion patch
  • Use PR to insert the cycle in master

[Thrameos]

@marscher I had a chance to complete this during my groups morning status meeting. (Thank goodness we now have a defined procedure)

[marscher]

That was super fast. The release pipeline is really worth all the effort! Thank you very much!

…

On July 16, 2020 4:43:23 PM UTC, Karl Nelson ***@***.***> wrote: @marscher I had a chance to complete this during my groups morning status meeting. (Thank goodness we now have a defined procedure) -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #790 (comment)

[Thrameos]

@marscher will you have a chance to post to PyPI and anaconda?

[marscher]

Will do it asap. Thanks again!