You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
@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.
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
The text was updated successfully, but these errors were encountered: