[Starlingx-discuss] Flock Versioning for packaging

Dean Troyer dtroyer at gmail.com
Thu May 16 17:16:09 UTC 2019

On Wed, May 15, 2019 at 2:22 PM Jones, Bruce E <bruce.e.jones at intel.com> wrote:
> Can we / should we extend our support of semantic versioning to the overall release numbering?  We're already on that track - we are doing our 2.0 release now, which is an API level release from stx.2018.10 which we could consider our 1.0 release.  If we call it 2.0.0, we'd be on track to continue following the versioning requirements going forward.

I would rather not tie the overall integrated STX release to the
individual components.  It may be that the major versions align for a
time but making that assumption is likely to bite us down the road.

> I think clearly communicating API changes to our users would be very helpful.

It is but we really are not talking about APIs here (REST APIs
anyway).  APIs should be versioned separately from their
implementation code.  You ave at least 2 components (at a minimum 1
server and 1 or more clients) to each one and those components will
likely not evolve at the same rate.

The "marketing version" (aka STX 2) we use for announcements, etc is
the version of the "wrapper" or integrated ISO or whatever aggregate
we ship in the future.  It contains a number of versioned components,
some themselves are wrappers (CentOS7.6 for example).


Dean Troyer
dtroyer at gmail.com

More information about the Starlingx-discuss mailing list