Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Automate release process #1

Open
fornellas opened this issue Oct 3, 2018 · 0 comments
Open

Automate release process #1

fornellas opened this issue Oct 3, 2018 · 0 comments
Assignees
@deathowl
Labels
Build enhancement New feature or request help wanted Extra attention is needed
Milestone
Improve Build

Comments

@fornellas
Copy link
Contributor

This is mostly manual as described at RELEASE.md. We need to:

  • Using semantic versioning, be able to do major, minor and patch releases, calculating the new version based on the previous.
  • Unify version at setup.py and docs/conf.py.
  • Ensure Travis CI build is OK for new release.
  • Ensure readthedocs.org build is OK for each release.
@fornellas fornellas added bug Something isn't working enhancement New feature or request help wanted Extra attention is needed and removed bug Something isn't working labels Apr 16, 2019
@fornellas fornellas added this to the Build milestone Apr 9, 2020
@fornellas fornellas added the Build label Apr 9, 2020
@deathowl deathowl self-assigned this Aug 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@deathowl deathowl

Labels
Build enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
Improve Build
Development

No branches or pull requests
2 participants
@deathowl @fornellas