-
When submitting a new dictionary, only `x.xx` versions are allowed.,
We have run into issues with this in the ARGO implementation - three levels of version would help with dictionary version manag…
-
### Feature request
Transformers is an incredibly popular library used by many folks. It would be great if Transformers would adopt semantic versioning (https://semver.org/) and follow best practic…
-
We should implement a workflow for semantic versioning of the BACK stack components to clarify the differences between releases and targets for end users.
Suggested workflow:
- Changes to the `mai…
-
Originally, I wanted to start the same versioning scheme here I had initiated for bitte cli, which was the semver semantic. At the time, it was argued that calendar version may be more appropriate, an…
nrdxp updated
2 years ago
-
Figure out how to do semantic versioning
**Ideas:**
- semantic versioning on PR merge based on branch prefix (Github Action?)
- fix - patch
- patch - patch
- feature/feature - min…
-
specially: increase major number when a new version is not backwards compatible.
https://semver.org/
example: make_json_input now is called gnssir_input.
-
## Background
Currently, the project is not version as a whole (clientLibrary is). Let's extend the versioning to the whole project.
Ideally, these tags should then be used for particular docker ima…
-
[Semver](http://semver.org) would help to keep track in e.g. [glide](https://glide.sh).
-
I was unable to find a commitment to a specific versioning scheme. Wouldn't it make sense to commit to one so other tools know what to expect? e.g. https://github.com/fabianegli/proteomicslfq/blob/dev…
-
**Is your feature request related to a problem? Please describe.**
The project uses a strange versioning scheme currently
**Describe the solution you'd like**
Use [semantic versioning](https://se…