Re: [Hyperledger Project TSC] Hyperledger Release Taxonomy v0.1
toggle quoted message Show quoted text
Won't make the TSC meeting, but some thoughts.
For our python modules, we are doing something similar to the openstack project where we have X.Y.Z-devN where N is the number of commits since X.Y.Z-1. This makes sure that we don't produce artifacts with the same version as the tagged version. This uses get describe and all the setup.py files in sawtooth repos implement this. If you are on a tagged version, then it properly uses X.Y.Z. This has worked well for Jenkins builds.
It would be nice to use 0.99.x instead of 0.9.x, in case we want to have 0.8.x, 0.9.x, 0.10.x, 0.11.x, etc. within our individual projects. Unlikely to use 0.99.x in that sequence.
We are considering abandoning our current use of 1.1.x for Sawtooth Lake components and bump back down to the 0.x range to conform to this spec. (As we only have very few tags anyway.)
On Thu, Jul 14, 2016 at 7:15 AM, Brian Behlendorf via hyperledger-tsc <hyperledger-tsc@...> wrote:
On 06/23/2016 01:58 AM, Baohua Yang wrote: