-
Notifications
You must be signed in to change notification settings - Fork 0
Implement semantic versioning #40
Copy link
Copy link
Open
Labels
clientIssues from client human reviewIssues from client human reviewdocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestoptionalOnly a nice-to-have feature, can be skipped (especially if it conflicts with a non-optional issue)Only a nice-to-have feature, can be skipped (especially if it conflicts with a non-optional issue)
Description
Activity
Metadata
Metadata
Assignees
Labels
clientIssues from client human reviewIssues from client human reviewdocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestoptionalOnly a nice-to-have feature, can be skipped (especially if it conflicts with a non-optional issue)Only a nice-to-have feature, can be skipped (especially if it conflicts with a non-optional issue)
GitHub CI Actions should probably run on version changes rather than every push to
main.Ahead of that, implement versioning as described in Semantic Versioning (it's more complicated than it looks, really you'll be in 0.y.z until the end of the semester, where you should aim for a 1.0.0, and then each week can update the y or z while checking that the test suite passes)
In case anyone asks, semantic versioning is stricter than the Python package versioning standards.