-
### 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…
-
We need to support a [semantic versioning](http://semver.org/) update system for homshick in order to mitigate the risk of breaking user's castles with a major release (i.e. **potential** breaking cha…
-
Right now hug only supports versioning on a straight numeric value, this works fairly well in most cases where no breaking changes happen between major releases, however it can occasionally fall apart…
-
Please consider semantic/numeric versioning:
- http://semver.org/
- https://en.wikipedia.org/wiki/Software_versioning
See also [Debian Upstream Guide](https://wiki.debian.org/UpstreamGuide#Releases_a…
-
The swift package manager requires that packages use semantic versioning to automatically pull files. It would be nice if Git2Swift followed this scheme for it's releases:
MAJOR.MINOR.PATCH
MAJOR v…
-
### Willingness to contribute
Yes. I would be willing to contribute this feature with guidance from the MLflow community.
### Proposal Summary
For registered model versions allow user-specifi…
-
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…
-
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…
-
If this project can be changed to use semantic versioning (http://semver.org) then we can properly make use of it via Bower.
Bower example file below:
```
{
"name": "responsiveslides",
"version"…
-
**The problem**
The current package.json for [@emotion/react](https://github.com/emotion-js/emotion/blob/main/packages/react/package.json) and [@emotion/styled](https://github.com/emotion-js/emotion/…