Ahhhh. Thanks Tommy. So I see that the Apache community doesn't release binary packages, just versioned source code tarballs:
- https://mesos.apache.org/downloads/ I'll follow up with Mesosphere directly, thanks! - Erik On Wednesday, February 3, 2016, tommy xiao <xia...@gmail.com> wrote: > it belong to mesosphere concerns, not apache community's scope. > > 2016-02-03 9:23 GMT+08:00 Erik Weathers <eweath...@groupon.com.invalid>: > > > I've noticed that in the published mesos packages [1] & docker images [2] > > that the version name isn't simply: > > > > - mesos_0.27.0.ubuntu1404_amd64 > > > > Instead it has the form of: > > > > - mesos_0.27.0*-0.2.190*.ubuntu1404_amd64 > > > > Here are a few more examples of this numeric suffix: > > > > - 0.27.0 -> 0.27.0-0.2.190 > > - 0.26.0 -> 0.26.0-0.2.145 > > - 0.25.0 -> 0.25.0-0.2.70 > > - 0.24.1 -> 0.24.1-0.2.35 > > - 0.24.0 -> 0.24.0-1.0.27 > > > > It is not clear to me what these suffixes represent, and it makes it hard > > to write code that can download or install the mesos package for a > > particular version given just the simple version name (e.g., 0.27.0). I > > tried searching for what might be generating this version suffix, or for > > documentation of the release process for mesos, but I have failed. > > > > So my question is really 2-fold: > > (1) Where does this extra suffix come from? Does it represent something > > specific? What is its purpose? Why isn't the version simply the > version? > > (I'm sure there *is* a reason, but I haven't found it on my own.) > > (2) What is the "right" way to handle this seeming unpredictability? > > > > Thanks! > > > > - Erik > > > > References: > > [1] http://open.mesosphere.com/downloads/mesos/ > > [2] https://hub.docker.com/r/mesosphere/mesos/tags/ > > > > > > -- > Deshi Xiao > Twitter: xds2000 > E-mail: xiaods(AT)gmail.com >
