-
I often find the API has been broken within the same major version.
Would it make sense to start using [semantic versioning](https://semver.org/) to give the user indication - "broken API ahead"?
-
**Is your feature request related to a problem? Please describe.**
i would like to see regular version updates
**Describe the solution you'd like**
we currently regularly rebuild but the versioni…
-
### Pre-requisites:
- [x] Yes, I looked through both [open and closed issues](../../../issues?utf8=✓&q=is%3Aissue) looking for what I needed
## Feature Description
We need to add a new GitHub…
-
How do we want to employ semantic versioning for this library?
Thrust for instance updates the release version by hand by setting new values in [thrust/version.h](https://github.com/NVIDIA/thrust/b…
-
### Problem Statement
Breaking changes without proper versioning
### Proposed Solution
Usage of Semantic Versioning as mentioned in https://semver.org/
### Additional Context
If sem ver…
-
So many numbers are in the release version... Let's consider using standard Semantic Versioning practice please: https://semver.org/
-
Via Will: http://semver.org/
Current system looks like this:
1. Tag `1.x` following last tag used when doing a build. Example: `1.27` follows `1.26`.
2. Choose cosmetic version number. Example: `1.…
-
> Originally https://github.com/eHealthAfrica/data_model/issues/4 from @janl
danse updated
8 years ago
-
Warning is produced on "composer validate", alpha or dev versioning should be set up.
```
See http://getcomposer.org/doc/04-schema.md for details on the schema
require.trifs/jsonrpc : unbound version…
ghost updated
10 years ago
-
Catapult should be released with proper versioning/changelog/etc. To bump a catapult version in our CI one would need to know what each release brings. Following semantic versioning will create some c…