Skip to content
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.

Document Versioning Mechanism #80

Closed
trickeydan opened this issue Feb 14, 2019 · 2 comments
Closed

Document Versioning Mechanism #80

trickeydan opened this issue Feb 14, 2019 · 2 comments
Assignees
@trickeydan
Labels
documentation Documentation
Milestone
v0.2.0

Comments

@trickeydan
Copy link
Contributor

We should decide on the versioning system for j5.

Relevant material: PEP440, PEP396, SemVer.

We need to bear in mind that we may have to maintain multiple major versions at the same time. For example, if the SR competition has deployed version 4.0.1 to kits and we need to deploy a bug fix.
@trickeydan trickeydan mentioned this issue Feb 14, 2019
Closed
@trickeydan trickeydan added the communication requested Extra attention is needed label Feb 15, 2019
@trickeydan trickeydan mentioned this issue Feb 27, 2019
Merged
@trickeydan
Copy link
Contributor Author

Also suggested: https://calver.org/

@trickeydan trickeydan added documentation Documentation and removed communication requested Extra attention is needed labels Mar 11, 2019
@trickeydan
Copy link
Contributor Author

This has been decided as SemVer.

@trickeydan trickeydan changed the title Decide on versioning mechanism Document Versioning Mechanism Mar 11, 2019
@trickeydan trickeydan added this to the v0.2.0 milestone Mar 12, 2019
@trickeydan trickeydan self-assigned this Apr 8, 2019
trickeydan added a commit that referenced this issue Apr 8, 2019
@trickeydan
Add information on versioning
3e7be8d 
Fixes #80
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@trickeydan trickeydan

Labels
documentation Documentation
Projects
None yet
Milestone
v0.2.0
Development

No branches or pull requests
1 participant
@trickeydan