Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: are mesos package version names predictable?
From: Till Toenshoff <toenshoff@me.com>
In-reply-to: 
 <CAO5KYW8=WQ2Rd1obyA6_9yzaSrDZE___Bd7g41FjgK4gcJrKFw@mail.gmail.com>
Date: Thu, 04 Feb 2016 22:51:42 +0100
Content-transfer-encoding: quoted-printable
Message-id: <D516AE40-B525-40F7-A524-8DF0D95605BC@me.com>
References: 
 <CAO5KYW8=WQ2Rd1obyA6_9yzaSrDZE___Bd7g41FjgK4gcJrKFw@mail.gmail.com>
To: dev@mesos.apache.org

Hey Erik,

those added values (e.g. =E2=80=9C-0.2.190") come from Mesosphere's CI =
system which adds build-numbers (the last digit) and some more =E2=80=9Cno=
ise" for those distribution packages.

I will raise this issue internally and get back to you - hoping that we =
can get rid of these not so useful extensions in a not too distant =
future.

hth,
Till

=20
> On Feb 3, 2016, at 2:23 AM, Erik Weathers =
<eweathers@groupon.com.INVALID> wrote:
>=20
> I've noticed that in the published mesos packages [1] & docker images =
[2]
> that the version name isn't simply:
>=20
>   -  mesos_0.27.0.ubuntu1404_amd64
>=20
> Instead it has the form of:
>=20
>   - mesos_0.27.0*-0.2.190*.ubuntu1404_amd64
>=20
> Here are a few more examples of this numeric suffix:
>=20
>   - 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
>=20
> 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.
>=20
> 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?
>=20
> Thanks!
>=20
> - Erik
>=20
> References:
> [1] http://open.mesosphere.com/downloads/mesos/
> [2] https://hub.docker.com/r/mesosphere/mesos/tags/