Replies: 1 comment 5 replies
-
Sadly this is against our release pipeline. So I'm -1 on this as I'd rather not add GitHub as release dependency. Changes are part of the changelog section in our documentation and I'd rather not duplicate it in GitHub release page. We don't use GitHub releases in general. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Please use only github release page to create new released (and tags) instead of pushing tags directly. This allow you to include some release notes and more importantly it gives you the option to start a discussion thread for each release, where you can receive feedback from that particular release.
For example
4.0.0b1
was created using git push, so is not visible on https://github.com/tox-dev/tox/releases and it is much harder to provide feedback on it. Keep in mind that having one thread per release is a very good way to gather feedback on how good or bad it was. Anyone visiting github will only see4.0.0a10
as last release, today's beta being hidden from view due to the way it was released.A hint: you can still create that release even if the tag was already created before it.
Digging the issue tracker in order to find out bugs related to particular release is difficult and imprecise. Also that approach does not make it possible to identify positive feedback on that release. Discussions threads sorts both.
Beta Was this translation helpful? Give feedback.
All reactions