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

Versioning strategy? #14

Closed
CoburnJoe opened this issue May 4, 2021 · 2 comments
Closed

Versioning strategy? #14

CoburnJoe opened this issue May 4, 2021 · 2 comments

Comments

@CoburnJoe
Copy link

Hi,

What's the versioning strategy for new releases? I ask as the project appears to use Semantic Versioning, but the latest release 0.3.0 contains breaking changes.
@cak
Copy link
Owner

cak commented May 4, 2021

Thank you for asking! We are trying our best to follow semantic versioning, however since secure.py is still in initial development (pre-1.0.0 release, see #4 and #5) the minor version may contain breaking changes. We hope to take feedback from the 0.3.0 release and work towards 1.0.0 in the near future.

@CoburnJoe
Copy link
Author

Thanks for the information @cak

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CoburnJoe @cak