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.

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

Releases #25

Closed
dimqua opened this issue Nov 9, 2018 · 3 comments
Closed

Releases #25

dimqua opened this issue Nov 9, 2018 · 3 comments

Comments

@dimqua
Copy link

dimqua commented Nov 9, 2018

Please consider to create at least one stable release.

@ThunderEX
Copy link
Owner

Hi @dimqua , why do you think we need a release? what's the benefit of release instead of using latest version directly?

@dimqua
Copy link
Author

dimqua commented Nov 12, 2018

For users:

  • You can easily figure out which version of the software you already have (latest or not).
  • It's easy to decide to update to the latest version or not (yet), thanks to semantic versioning.
  • You can check the status of each release, and (for example) update to major releases only if you want.
  • You have access to more detailed changelogs (commit history is not enough in some cases).

As a developer, you can make ground-breaking changes and provide stable releases at the same time (although you can use separate branches for that).


But I'm not compeltly sure that any of these reasons are applicable to such a small project like this one. So if you think they are not, feel free to close this issue.

@ThunderEX
Copy link
Owner

Hi @dimqua ,
Thanks and I fully agree with the explanation. I think py-kms itself is not mature yet, especially for #6. I will try to tag for release when it's mature enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants