-
We open sourced testnet last week, but only provide instructions to build a node and a Dockerfile.
As there can be a host of unforeseen issues with it, I think it'll be better to provide both a tagge…
-
Thanks for bumpversion, usually works great.
Trying to create a beta version for [hamster](https://github.com/projecthamster/hamster).
```bash
$ bump2version --new-version 3.0-beta
bumpversion: …
-
Hello,
I have reported already the same question on the original project but then found this one which seems to be actively maintained.
We are using semantic versioning (semver.org) in our proje…
-
We should consider moving pathpy3 to an automatic versioning scheme, with a build number that is automatically incremented with each commit. Candidate libraries include [this](https://github.com/twist…
-
I'm currently working on the 3.0.2 release.
The full release process should be documented somewhere. For now, I'll use this issue to keep notes, this should probably move into the repo somewhere (C…
-
While the crate itself has a version, other places are lacking proper versioning:
- [x] GitHub releases
- [x] Git tags
- [ ] Versioning strategy (especially once there's a v1.0.0)
- [x] Changelo…
-
I have been looking for a project that supports both calver and semver. I'd like to see what the interest would be to add calver features here, similar to those supported in [bumpver](https://github.…
-
Consider [the changes library](https://github.com/michaeljoseph/changes) or `bumpversion` or `bump2version` or even `bump`. Also look at the Azure/GitHub integration for a release (`GithubRelease` tas…
-
Rather than checking versions from a specific commit, consider a keyword / input / envvar to check the dirty status of the repo.
This may not be worth the effort. but is at least worth considering
-
Currently it's impossible to create pre-releases using the [automated release process](https://github.com/ethereum/pyethapp/wiki/Development:-Versions-and-Releases).
Since there currently are a lot…
ulope updated
7 years ago