As Dotscience developers, we'd like all the parts of our product to use the same versioning/release process, so we don't need to remember two.
Therefore, we should make Dotmesh use the lightweight semver process like the other repos.
ACs
[ ] We put a semver tag in Dotmesh every time we finish something.
[ ] The build system, when it sees a semver tag appear (and tests have passed), builds the docker images with that semver tag as the image tag, and uploads the binaries to get.dotmesh.io/release-X.Y.Z
[ ] There is still a manual mark_release_as_stable step to update the "current" symlinks
[ ] We no longer worry about posting the release on Github
[ ] We do something sensible about the "what's the latest release" feature - rather than polling the Github API, just poll a text file on got.dotmesh.io that the mark_release_as_stable step sets to the current semver?
alaric-dotmesh
commented
5 years ago
As Dotscience developers, we'd like all the parts of our product to use the same versioning/release process, so we don't need to remember two.
Therefore, we should make Dotmesh use the lightweight semver process like the other repos.
ACs
get.dotmesh.io/release-X.Y.Zmark_release_as_stablestep to update the "current" symlinksgot.dotmesh.iothat themark_release_as_stablestep sets to the current semver?