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

Versioning schema #183

Open
tylerbarna opened this issue Jul 30, 2023 · 1 comment
Open

Versioning schema #183

tylerbarna opened this issue Jul 30, 2023 · 1 comment
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@tylerbarna
Copy link
Collaborator

Do we have an established schema for version numbers/releases? Are we targeting a minimum change over the previous version number to create a new version?

It might be useful to implement some type of schema that delineates between bug fixes and minor updates and updates that change existing functionality and/or add new functionality. For example, something like the update to Zenodo or the change to the names used for filters would probably fall into the latter category, whereas fixing a flag that wasn't functioning as intended or removing a redundancy in the code would fall into the former category

@tylerbarna tylerbarna added documentation Improvements or additions to documentation question Further information is requested labels Jul 30, 2023
@mcoughlin
Copy link
Member

@tylerbarna At least for now, my priority is that folks who pip install things are almost always getting the very latest version of things. We can probably claim we are at 0.1.X at this stage, so maybe we will tag one of the releases as such soon. Some kind of CHANGENOTES would be great in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants