Re: are mesos package version names predictable?

[Till Toenshoff]

Hey Erik,

those added values (e.g. “-0.2.190") come from Mesosphere's CI system which 
adds build-numbers (the last digit) and some more “noise" 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

 
> On Feb 3, 2016, at 2:23 AM, Erik Weathers  
> wrote:
> 
> 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/

Re: are mesos package version names predictable?

[Till Toenshoff]

Given that the final number (build number) is constantly being raised, I fear 
there is really not much you can do. The “0.2” and “1.0” were originally 
planned for snapshots (0.2) vs. releases (1.0) but as you can see, we changed 
that over time.

The only robust option I see right now is a mapping table as you drafted in 
your initial mail already. You would have to touch that mapping with each new 
release :(

… but hope is in sight, for future releases at least… will keep you updated.

> On Feb 4, 2016, at 11:07 PM, Erik Weathers  
> wrote:
> 
> hey Till, thanks for the response!   Would be great to have those
> CI-build-numbers squelched in the future if possible.  Or some sort of
> alias set up to allow redirecting to the fully expanded build.
> 
> Any suggestions for the short term of how to perform this redirection?  For
> reference, the purpose of this is to allow the storm-on-mesos project's
> Dockerfile to have a configurable mesos version.
> 
>   - https://github.com/mesos/storm/pull/91
> 
> - Erik
> 
> On Thu, Feb 4, 2016 at 1:51 PM, Till Toenshoff  wrote:
> 
>> Hey Erik,
>> 
>> those added values (e.g. “-0.2.190") come from Mesosphere's CI system
>> which adds build-numbers (the last digit) and some more “noise" 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
>> 
>> 
>>> On Feb 3, 2016, at 2:23 AM, Erik Weathers 
>> wrote:
>>> 
>>> 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/
>> 
>> 

Re: are mesos package version names predictable?

[Erik Weathers]

hey Till, thanks for the response!   Would be great to have those
CI-build-numbers squelched in the future if possible.  Or some sort of
alias set up to allow redirecting to the fully expanded build.

Any suggestions for the short term of how to perform this redirection?  For
reference, the purpose of this is to allow the storm-on-mesos project's
Dockerfile to have a configurable mesos version.

   - https://github.com/mesos/storm/pull/91

- Erik

On Thu, Feb 4, 2016 at 1:51 PM, Till Toenshoff  wrote:

> Hey Erik,
>
> those added values (e.g. “-0.2.190") come from Mesosphere's CI system
> which adds build-numbers (the last digit) and some more “noise" 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
>
>
> > On Feb 3, 2016, at 2:23 AM, Erik Weathers 
> wrote:
> >
> > 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/
>
>

Move implementations of Framework struct functions out of master.hpp

[Isabel Jimenez]

Hello everyone,

As part of an effort in reducing tech-debt and tickets that have been
stalling for some time, I'm working on
https://issues.apache.org/jira/browse/MESOS-2633.
As you can read in the ticket the discussion was summarize in this comment:
"... how about we create a master/framework.hpp (and master/slave.hpp
later), much like we did for master/metrics.hpp? Having definitions in
master.hpp that are defined in framework.cpp is a bit unintuitive (I've
seen a number of people get confused about this approach in
master/http.cpp).

Note that originally a master/metrics.cpp file was added on the assumption
that it would speed up build times, which likely didn't hold. Since you
didn't find a compile time decrease from the current approach, I'd suggest
just keeping all the code together in a master/framework.hpp header. Note
also that this lets you forward declare 'Framework"

Any additional thoughts before we move forward?

Isabel

[ANNOUNCE] Deprecating non JSON credentials

[Isabel Jimenez]

Hello everybody,

We introduced support for JSON formatted credentials in Mesos 0.20.0, we
should now deprecate the old 'new line' format.

There has been a discussion around defining and documenting a deprecation
cycle for Mesos and for now there is soft consensus in a six months period
to deprecate a feature.
This means that the deprecation of non JSON formatted credentials will be
documented in 0.28.0 and that this feature will be completely removed in
the release happening six months after 0.28.0.

Please comment any thoughts on the JIRA ticket :
https://issues.apache.org/jira/browse/MESOS-2281

Isabel

Re: are mesos package version names predictable?

[Erik Weathers]

Thanks Till, that is what I expected, and I appreciate the extra historical
insight.  Fingers crossed for future releases!  ;-)

On Thu, Feb 4, 2016 at 2:42 PM, Till Toenshoff  wrote:

> Given that the final number (build number) is constantly being raised, I
> fear there is really not much you can do. The “0.2” and “1.0” were
> originally planned for snapshots (0.2) vs. releases (1.0) but as you can
> see, we changed that over time.
>
> The only robust option I see right now is a mapping table as you drafted
> in your initial mail already. You would have to touch that mapping with
> each new release :(
>
> … but hope is in sight, for future releases at least… will keep you
> updated.
>
> > On Feb 4, 2016, at 11:07 PM, Erik Weathers 
> wrote:
> >
> > hey Till, thanks for the response!   Would be great to have those
> > CI-build-numbers squelched in the future if possible.  Or some sort of
> > alias set up to allow redirecting to the fully expanded build.
> >
> > Any suggestions for the short term of how to perform this redirection?
> For
> > reference, the purpose of this is to allow the storm-on-mesos project's
> > Dockerfile to have a configurable mesos version.
> >
> >   - https://github.com/mesos/storm/pull/91
> >
> > - Erik
> >
> > On Thu, Feb 4, 2016 at 1:51 PM, Till Toenshoff  wrote:
> >
> >> Hey Erik,
> >>
> >> those added values (e.g. “-0.2.190") come from Mesosphere's CI system
> >> which adds build-numbers (the last digit) and some more “noise" 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
> >>
> >>
> >>> On Feb 3, 2016, at 2:23 AM, Erik Weathers
> 
> >> wrote:
> >>>
> >>> 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/
> >>
> >>
>
>

Re: are mesos package version names predictable?

[Shuai Lin]

+1 for removing the build number from the version number of
mesosphere-released deb/rpm pkgs.

On Fri, Feb 5, 2016 at 5:51 AM, Till Toenshoff  wrote:

> Hey Erik,
>
> those added values (e.g. “-0.2.190") come from Mesosphere's CI system
> which adds build-numbers (the last digit) and some more “noise" 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
>
>
> > On Feb 3, 2016, at 2:23 AM, Erik Weathers 
> wrote:
> >
> > 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/
>
>

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

[Niklas Nielsen]

Awesome guys!

Kapil, we usually linked to the user documentation in the blog to the new
features. Do you have a link to the docs on multiple disk resources?

On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya  wrote:

> And here is the blog post:
> http://mesos.apache.org/blog/mesos-0-27-0-released.
>
> On Wed, Feb 3, 2016 at 4:48 PM, Michael Park  wrote:
> > Kapil is currently working on it. We'll publish it shortly :)
> >
> > On 3 February 2016 at 13:41, Benjamin Mahler  wrote:
> >>
> >> Great! Is a blog post on the way?
> >>
> >> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park  wrote:
> >>
> >> > Hi all,
> >> >
> >> > The vote for Mesos 0.27.0 (rc2) has passed with the
> >> > following votes.
> >> >
> >> > +1 (Binding)
> >> > --
> >> > Vinod Kone
> >> > Joris Van Remoortere
> >> > Till Toenshoff
> >> >
> >> > +1 (Non-binding)
> >> > --
> >> > Jörg Schad
> >> > Marco Massenzio
> >> > Greg Mann
> >> >
> >> > There were no 0 or -1 votes.
> >> >
> >> > Please find the release at:
> >> > https://dist.apache.org/repos/dist/release/mesos/0.27.0
> >> >
> >> > It is recommended to use a mirror to download the release:
> >> > http://www.apache.org/dyn/closer.cgi
> >> >
> >> > The CHANGELOG for the release is available at:
> >> >
> >> >
> >> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.0
> >> >
> >> > The mesos-0.27.0.jar has been released to:
> >> > https://repository.apache.org
> >> >
> >> > The website (http://mesos.apache.org) will be updated shortly to
> reflect
> >> > this release.
> >> >
> >> > Thanks,
> >> >
> >> > Tim, Kapil, MPark
> >> >
> >
> >
>



-- 
Niklas

Re: Questions about release process

[Vinod Kone]

yes. fixed!

On Thu, Feb 4, 2016 at 10:51 AM, David Forsythe  wrote:

> Hi Vinod,
>
> Would it be right to assume these tickets should also probably have their
> fix version updated?
>
> https://issues.apache.org/jira/browse/MESOS-4211
> https://issues.apache.org/jira/browse/MESOS-4212
> https://issues.apache.org/jira/browse/MESOS-4251
> https://issues.apache.org/jira/browse/MESOS-4252
>
>
>
> On Thu, Feb 4, 2016 at 10:34 AM Vinod Kone  wrote:
>
> > Looks like this didn't show up in the CHANGELOG because the "Fix version"
> > was not set on the ticket.
> >
> > Typically the release manager(s) ensures all fixed tickets have a Fix
> > version 
> > before cutting the release, but looks like this fell through the cracks
> :(
> >
> > I will fix it for now.
> >
> >
> > On Thu, Feb 4, 2016 at 10:16 AM, haosdent  wrote:
> >
> > > Hi, David. I could saw you commit in 0.27
> > >
> > >
> >
> https://github.com/apache/mesos/blob/0.27.0/3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > > Why you said it is missing?
> > >
> > > On Fri, Feb 5, 2016 at 2:11 AM, David Forsythe 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > A few changes for FreeBSD support landed in this release (at least
> > > > partially), but they don't seem to have made it into CHANGELOG. More
> > > > concerning is that a file in stout seems to be missing[1].
> > > >
> > > > For CHANGELOG, I assume I did something wrong in JIRA (example
> ticket:
> > > [2]
> > > > -- if something is wrong there, please let me know), but I'm not sure
> > > what
> > > > do about getting new files included. What can I do to make sure that
> > > > included changes are complete in future releases?
> > > >
> > > > Thanks!
> > > >
> > > > [1] 3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > > > [2] https://issues.apache.org/jira/browse/MESOS-1563
> > > >
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > Haosdent Huang
> > >
> >
>

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

[Niklas Nielsen]

Thanks Jie and Kapil! Looking forward to it.

I did read the proposal, but playing the devils advocate for a bit; how can
we ship a 'major feature' without bundled user documentation? Referring to
tickets and design docs (which may/or may not be the way things ended up
getting implemented) or to code is not good enough, in my mind.

Should we line up some expectations to available user docs, example
framework code, etc. before announcing the availability of a feature?

Niklas

On Thu, Feb 4, 2016 at 5:41 PM, Kapil Arya  wrote:

> And here is the ticket tracking the user doc:
> https://issues.apache.org/jira/browse/MESOS-4531. Will link to the
> blog post once the doc is ready :-).
>
> On Thu, Feb 4, 2016 at 11:38 AM, Jie Yu  wrote:
> > Niklas,
> >
> > I think Joris is still working on the user doc for multi-disk support in
> > Mesos.
> >
> > - Jie
> >
> > On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen  wrote:
> >
> >> Awesome guys!
> >>
> >> Kapil, we usually linked to the user documentation in the blog to the
> new
> >> features. Do you have a link to the docs on multiple disk resources?
> >>
> >> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya 
> wrote:
> >>
> >> > And here is the blog post:
> >> > http://mesos.apache.org/blog/mesos-0-27-0-released.
> >> >
> >> > On Wed, Feb 3, 2016 at 4:48 PM, Michael Park 
> wrote:
> >> > > Kapil is currently working on it. We'll publish it shortly :)
> >> > >
> >> > > On 3 February 2016 at 13:41, Benjamin Mahler 
> >> wrote:
> >> > >>
> >> > >> Great! Is a blog post on the way?
> >> > >>
> >> > >> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park 
> >> wrote:
> >> > >>
> >> > >> > Hi all,
> >> > >> >
> >> > >> > The vote for Mesos 0.27.0 (rc2) has passed with the
> >> > >> > following votes.
> >> > >> >
> >> > >> > +1 (Binding)
> >> > >> > --
> >> > >> > Vinod Kone
> >> > >> > Joris Van Remoortere
> >> > >> > Till Toenshoff
> >> > >> >
> >> > >> > +1 (Non-binding)
> >> > >> > --
> >> > >> > Jörg Schad
> >> > >> > Marco Massenzio
> >> > >> > Greg Mann
> >> > >> >
> >> > >> > There were no 0 or -1 votes.
> >> > >> >
> >> > >> > Please find the release at:
> >> > >> > https://dist.apache.org/repos/dist/release/mesos/0.27.0
> >> > >> >
> >> > >> > It is recommended to use a mirror to download the release:
> >> > >> > http://www.apache.org/dyn/closer.cgi
> >> > >> >
> >> > >> > The CHANGELOG for the release is available at:
> >> > >> >
> >> > >> >
> >> > >> >
> >> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.0
> >> > >> >
> >> > >> > The mesos-0.27.0.jar has been released to:
> >> > >> > https://repository.apache.org
> >> > >> >
> >> > >> > The website (http://mesos.apache.org) will be updated shortly to
> >> > reflect
> >> > >> > this release.
> >> > >> >
> >> > >> > Thanks,
> >> > >> >
> >> > >> > Tim, Kapil, MPark
> >> > >> >
> >> > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Niklas
> >>
>



-- 
Niklas

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

[Kapil Arya]

And here is the ticket tracking the user doc:
https://issues.apache.org/jira/browse/MESOS-4531. Will link to the
blog post once the doc is ready :-).

On Thu, Feb 4, 2016 at 11:38 AM, Jie Yu  wrote:
> Niklas,
>
> I think Joris is still working on the user doc for multi-disk support in
> Mesos.
>
> - Jie
>
> On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen  wrote:
>
>> Awesome guys!
>>
>> Kapil, we usually linked to the user documentation in the blog to the new
>> features. Do you have a link to the docs on multiple disk resources?
>>
>> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya  wrote:
>>
>> > And here is the blog post:
>> > http://mesos.apache.org/blog/mesos-0-27-0-released.
>> >
>> > On Wed, Feb 3, 2016 at 4:48 PM, Michael Park  wrote:
>> > > Kapil is currently working on it. We'll publish it shortly :)
>> > >
>> > > On 3 February 2016 at 13:41, Benjamin Mahler 
>> wrote:
>> > >>
>> > >> Great! Is a blog post on the way?
>> > >>
>> > >> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park 
>> wrote:
>> > >>
>> > >> > Hi all,
>> > >> >
>> > >> > The vote for Mesos 0.27.0 (rc2) has passed with the
>> > >> > following votes.
>> > >> >
>> > >> > +1 (Binding)
>> > >> > --
>> > >> > Vinod Kone
>> > >> > Joris Van Remoortere
>> > >> > Till Toenshoff
>> > >> >
>> > >> > +1 (Non-binding)
>> > >> > --
>> > >> > Jörg Schad
>> > >> > Marco Massenzio
>> > >> > Greg Mann
>> > >> >
>> > >> > There were no 0 or -1 votes.
>> > >> >
>> > >> > Please find the release at:
>> > >> > https://dist.apache.org/repos/dist/release/mesos/0.27.0
>> > >> >
>> > >> > It is recommended to use a mirror to download the release:
>> > >> > http://www.apache.org/dyn/closer.cgi
>> > >> >
>> > >> > The CHANGELOG for the release is available at:
>> > >> >
>> > >> >
>> > >> >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.0
>> > >> >
>> > >> > The mesos-0.27.0.jar has been released to:
>> > >> > https://repository.apache.org
>> > >> >
>> > >> > The website (http://mesos.apache.org) will be updated shortly to
>> > reflect
>> > >> > this release.
>> > >> >
>> > >> > Thanks,
>> > >> >
>> > >> > Tim, Kapil, MPark
>> > >> >
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Niklas
>>

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

[Kapil Arya]

That's a good point, Niklas!

IMO, we should be able to ship a major feature as long as we have an
assurance that the user doc will land in the next few days (not
weeks).

On Thu, Feb 4, 2016 at 11:55 AM, Niklas Nielsen  wrote:
> Thanks Jie and Kapil! Looking forward to it.
>
> I did read the proposal, but playing the devils advocate for a bit; how can
> we ship a 'major feature' without bundled user documentation? Referring to
> tickets and design docs (which may/or may not be the way things ended up
> getting implemented) or to code is not good enough, in my mind.
>
> Should we line up some expectations to available user docs, example
> framework code, etc. before announcing the availability of a feature?
>
> Niklas
>
> On Thu, Feb 4, 2016 at 5:41 PM, Kapil Arya  wrote:
>>
>> And here is the ticket tracking the user doc:
>> https://issues.apache.org/jira/browse/MESOS-4531. Will link to the
>> blog post once the doc is ready :-).
>>
>> On Thu, Feb 4, 2016 at 11:38 AM, Jie Yu  wrote:
>> > Niklas,
>> >
>> > I think Joris is still working on the user doc for multi-disk support in
>> > Mesos.
>> >
>> > - Jie
>> >
>> > On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen  wrote:
>> >
>> >> Awesome guys!
>> >>
>> >> Kapil, we usually linked to the user documentation in the blog to the
>> >> new
>> >> features. Do you have a link to the docs on multiple disk resources?
>> >>
>> >> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya 
>> >> wrote:
>> >>
>> >> > And here is the blog post:
>> >> > http://mesos.apache.org/blog/mesos-0-27-0-released.
>> >> >
>> >> > On Wed, Feb 3, 2016 at 4:48 PM, Michael Park 
>> >> > wrote:
>> >> > > Kapil is currently working on it. We'll publish it shortly :)
>> >> > >
>> >> > > On 3 February 2016 at 13:41, Benjamin Mahler 
>> >> wrote:
>> >> > >>
>> >> > >> Great! Is a blog post on the way?
>> >> > >>
>> >> > >> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park 
>> >> wrote:
>> >> > >>
>> >> > >> > Hi all,
>> >> > >> >
>> >> > >> > The vote for Mesos 0.27.0 (rc2) has passed with the
>> >> > >> > following votes.
>> >> > >> >
>> >> > >> > +1 (Binding)
>> >> > >> > --
>> >> > >> > Vinod Kone
>> >> > >> > Joris Van Remoortere
>> >> > >> > Till Toenshoff
>> >> > >> >
>> >> > >> > +1 (Non-binding)
>> >> > >> > --
>> >> > >> > Jörg Schad
>> >> > >> > Marco Massenzio
>> >> > >> > Greg Mann
>> >> > >> >
>> >> > >> > There were no 0 or -1 votes.
>> >> > >> >
>> >> > >> > Please find the release at:
>> >> > >> > https://dist.apache.org/repos/dist/release/mesos/0.27.0
>> >> > >> >
>> >> > >> > It is recommended to use a mirror to download the release:
>> >> > >> > http://www.apache.org/dyn/closer.cgi
>> >> > >> >
>> >> > >> > The CHANGELOG for the release is available at:
>> >> > >> >
>> >> > >> >
>> >> > >> >
>> >> >
>> >>
>> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.0
>> >> > >> >
>> >> > >> > The mesos-0.27.0.jar has been released to:
>> >> > >> > https://repository.apache.org
>> >> > >> >
>> >> > >> > The website (http://mesos.apache.org) will be updated shortly to
>> >> > reflect
>> >> > >> > this release.
>> >> > >> >
>> >> > >> > Thanks,
>> >> > >> >
>> >> > >> > Tim, Kapil, MPark
>> >> > >> >
>> >> > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Niklas
>> >>
>
>
>
>
> --
> Niklas

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

[Jie Yu]

Niklas,

I think Joris is still working on the user doc for multi-disk support in
Mesos.

- Jie

On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen  wrote:

> Awesome guys!
>
> Kapil, we usually linked to the user documentation in the blog to the new
> features. Do you have a link to the docs on multiple disk resources?
>
> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya  wrote:
>
> > And here is the blog post:
> > http://mesos.apache.org/blog/mesos-0-27-0-released.
> >
> > On Wed, Feb 3, 2016 at 4:48 PM, Michael Park  wrote:
> > > Kapil is currently working on it. We'll publish it shortly :)
> > >
> > > On 3 February 2016 at 13:41, Benjamin Mahler 
> wrote:
> > >>
> > >> Great! Is a blog post on the way?
> > >>
> > >> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park 
> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > The vote for Mesos 0.27.0 (rc2) has passed with the
> > >> > following votes.
> > >> >
> > >> > +1 (Binding)
> > >> > --
> > >> > Vinod Kone
> > >> > Joris Van Remoortere
> > >> > Till Toenshoff
> > >> >
> > >> > +1 (Non-binding)
> > >> > --
> > >> > Jörg Schad
> > >> > Marco Massenzio
> > >> > Greg Mann
> > >> >
> > >> > There were no 0 or -1 votes.
> > >> >
> > >> > Please find the release at:
> > >> > https://dist.apache.org/repos/dist/release/mesos/0.27.0
> > >> >
> > >> > It is recommended to use a mirror to download the release:
> > >> > http://www.apache.org/dyn/closer.cgi
> > >> >
> > >> > The CHANGELOG for the release is available at:
> > >> >
> > >> >
> > >> >
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.0
> > >> >
> > >> > The mesos-0.27.0.jar has been released to:
> > >> > https://repository.apache.org
> > >> >
> > >> > The website (http://mesos.apache.org) will be updated shortly to
> > reflect
> > >> > this release.
> > >> >
> > >> > Thanks,
> > >> >
> > >> > Tim, Kapil, MPark
> > >> >
> > >
> > >
> >
>
>
>
> --
> Niklas
>

Re: Questions about release process

[David Forsythe]

Ah!

Thanks!

On Thu, Feb 4, 2016 at 10:34 AM, Neil Conway  wrote:

> freebsd.hpp is missing from the 0.27 release tarball, presumably
> because 3rdparty/libprocess/3rdparty/stout/include/Makefile.am was not
> updated to account for it. I'll send an RR shortly.
>
> Neil
>
> On Thu, Feb 4, 2016 at 10:16 AM, haosdent  wrote:
> > Hi, David. I could saw you commit in 0.27
> >
> https://github.com/apache/mesos/blob/0.27.0/3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > Why you said it is missing?
> >
> > On Fri, Feb 5, 2016 at 2:11 AM, David Forsythe 
> wrote:
> >
> >> Hi,
> >>
> >> A few changes for FreeBSD support landed in this release (at least
> >> partially), but they don't seem to have made it into CHANGELOG. More
> >> concerning is that a file in stout seems to be missing[1].
> >>
> >> For CHANGELOG, I assume I did something wrong in JIRA (example ticket:
> [2]
> >> -- if something is wrong there, please let me know), but I'm not sure
> what
> >> do about getting new files included. What can I do to make sure that
> >> included changes are complete in future releases?
> >>
> >> Thanks!
> >>
> >> [1] 3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> >> [2] https://issues.apache.org/jira/browse/MESOS-1563
> >>
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
>



-- 
David

Re: Questions about release process

[David Forsythe]

Hi Vinod,

Would it be right to assume these tickets should also probably have their
fix version updated?

https://issues.apache.org/jira/browse/MESOS-4211
https://issues.apache.org/jira/browse/MESOS-4212
https://issues.apache.org/jira/browse/MESOS-4251
https://issues.apache.org/jira/browse/MESOS-4252



On Thu, Feb 4, 2016 at 10:34 AM Vinod Kone  wrote:

> Looks like this didn't show up in the CHANGELOG because the "Fix version"
> was not set on the ticket.
>
> Typically the release manager(s) ensures all fixed tickets have a Fix
> version 
> before cutting the release, but looks like this fell through the cracks :(
>
> I will fix it for now.
>
>
> On Thu, Feb 4, 2016 at 10:16 AM, haosdent  wrote:
>
> > Hi, David. I could saw you commit in 0.27
> >
> >
> https://github.com/apache/mesos/blob/0.27.0/3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > Why you said it is missing?
> >
> > On Fri, Feb 5, 2016 at 2:11 AM, David Forsythe 
> > wrote:
> >
> > > Hi,
> > >
> > > A few changes for FreeBSD support landed in this release (at least
> > > partially), but they don't seem to have made it into CHANGELOG. More
> > > concerning is that a file in stout seems to be missing[1].
> > >
> > > For CHANGELOG, I assume I did something wrong in JIRA (example ticket:
> > [2]
> > > -- if something is wrong there, please let me know), but I'm not sure
> > what
> > > do about getting new files included. What can I do to make sure that
> > > included changes are complete in future releases?
> > >
> > > Thanks!
> > >
> > > [1] 3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > > [2] https://issues.apache.org/jira/browse/MESOS-1563
> > >
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
> >
>

Re: Questions about release process

[David Forsythe]

Hi,

Yes, the changes are complete in git. However, the release tarball for 0.27
seems to be missing the file:

dforsyth@fbsd0:~/mesos_extract % md5 mesos-0.27.0.tar.gz
MD5 (mesos-0.27.0.tar.gz) = 54dae5aeed210fbec8c445af1120ccc2
dforsyth@fbsd0:~/mesos_extract % tar tf mesos-0.27.0.tar.gz | grep freebsd
dforsyth@fbsd0:~/mesos_extract %

Thanks!

On Thu, Feb 4, 2016 at 10:17 AM haosdent  wrote:

> Hi, David. I could saw you commit in 0.27
>
> https://github.com/apache/mesos/blob/0.27.0/3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> Why you said it is missing?
>
> On Fri, Feb 5, 2016 at 2:11 AM, David Forsythe 
> wrote:
>
> > Hi,
> >
> > A few changes for FreeBSD support landed in this release (at least
> > partially), but they don't seem to have made it into CHANGELOG. More
> > concerning is that a file in stout seems to be missing[1].
> >
> > For CHANGELOG, I assume I did something wrong in JIRA (example ticket:
> [2]
> > -- if something is wrong there, please let me know), but I'm not sure
> what
> > do about getting new files included. What can I do to make sure that
> > included changes are complete in future releases?
> >
> > Thanks!
> >
> > [1] 3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > [2] https://issues.apache.org/jira/browse/MESOS-1563
> >
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

[Joris Van Remoortere]

If we did feature based releases, we could hold the release for the
documentation.
Since we do time based releases, it so happened that the release went
through before we could get the docs done.

I'll be working on the docs shortly :-)

—
*Joris Van Remoortere*
Mesosphere

On Thu, Feb 4, 2016 at 8:59 AM, Kapil Arya  wrote:

> That's a good point, Niklas!
>
> IMO, we should be able to ship a major feature as long as we have an
> assurance that the user doc will land in the next few days (not
> weeks).
>
> On Thu, Feb 4, 2016 at 11:55 AM, Niklas Nielsen  wrote:
> > Thanks Jie and Kapil! Looking forward to it.
> >
> > I did read the proposal, but playing the devils advocate for a bit; how
> can
> > we ship a 'major feature' without bundled user documentation? Referring
> to
> > tickets and design docs (which may/or may not be the way things ended up
> > getting implemented) or to code is not good enough, in my mind.
> >
> > Should we line up some expectations to available user docs, example
> > framework code, etc. before announcing the availability of a feature?
> >
> > Niklas
> >
> > On Thu, Feb 4, 2016 at 5:41 PM, Kapil Arya  wrote:
> >>
> >> And here is the ticket tracking the user doc:
> >> https://issues.apache.org/jira/browse/MESOS-4531. Will link to the
> >> blog post once the doc is ready :-).
> >>
> >> On Thu, Feb 4, 2016 at 11:38 AM, Jie Yu  wrote:
> >> > Niklas,
> >> >
> >> > I think Joris is still working on the user doc for multi-disk support
> in
> >> > Mesos.
> >> >
> >> > - Jie
> >> >
> >> > On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen  wrote:
> >> >
> >> >> Awesome guys!
> >> >>
> >> >> Kapil, we usually linked to the user documentation in the blog to the
> >> >> new
> >> >> features. Do you have a link to the docs on multiple disk resources?
> >> >>
> >> >> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya 
> >> >> wrote:
> >> >>
> >> >> > And here is the blog post:
> >> >> > http://mesos.apache.org/blog/mesos-0-27-0-released.
> >> >> >
> >> >> > On Wed, Feb 3, 2016 at 4:48 PM, Michael Park 
> >> >> > wrote:
> >> >> > > Kapil is currently working on it. We'll publish it shortly :)
> >> >> > >
> >> >> > > On 3 February 2016 at 13:41, Benjamin Mahler  >
> >> >> wrote:
> >> >> > >>
> >> >> > >> Great! Is a blog post on the way?
> >> >> > >>
> >> >> > >> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park  >
> >> >> wrote:
> >> >> > >>
> >> >> > >> > Hi all,
> >> >> > >> >
> >> >> > >> > The vote for Mesos 0.27.0 (rc2) has passed with the
> >> >> > >> > following votes.
> >> >> > >> >
> >> >> > >> > +1 (Binding)
> >> >> > >> > --
> >> >> > >> > Vinod Kone
> >> >> > >> > Joris Van Remoortere
> >> >> > >> > Till Toenshoff
> >> >> > >> >
> >> >> > >> > +1 (Non-binding)
> >> >> > >> > --
> >> >> > >> > Jörg Schad
> >> >> > >> > Marco Massenzio
> >> >> > >> > Greg Mann
> >> >> > >> >
> >> >> > >> > There were no 0 or -1 votes.
> >> >> > >> >
> >> >> > >> > Please find the release at:
> >> >> > >> > https://dist.apache.org/repos/dist/release/mesos/0.27.0
> >> >> > >> >
> >> >> > >> > It is recommended to use a mirror to download the release:
> >> >> > >> > http://www.apache.org/dyn/closer.cgi
> >> >> > >> >
> >> >> > >> > The CHANGELOG for the release is available at:
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >
> >> >> >
> >> >>
> >> >>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.0
> >> >> > >> >
> >> >> > >> > The mesos-0.27.0.jar has been released to:
> >> >> > >> > https://repository.apache.org
> >> >> > >> >
> >> >> > >> > The website (http://mesos.apache.org) will be updated
> shortly to
> >> >> > reflect
> >> >> > >> > this release.
> >> >> > >> >
> >> >> > >> > Thanks,
> >> >> > >> >
> >> >> > >> > Tim, Kapil, MPark
> >> >> > >> >
> >> >> > >
> >> >> > >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Niklas
> >> >>
> >
> >
> >
> >
> > --
> > Niklas
>

Questions about release process

[David Forsythe]

Hi,

A few changes for FreeBSD support landed in this release (at least
partially), but they don't seem to have made it into CHANGELOG. More
concerning is that a file in stout seems to be missing[1].

For CHANGELOG, I assume I did something wrong in JIRA (example ticket: [2]
-- if something is wrong there, please let me know), but I'm not sure what
do about getting new files included. What can I do to make sure that
included changes are complete in future releases?

Thanks!

[1] 3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
[2] https://issues.apache.org/jira/browse/MESOS-1563

Re: Questions about release process

[Vinod Kone]

Looks like this didn't show up in the CHANGELOG because the "Fix version"
was not set on the ticket.

Typically the release manager(s) ensures all fixed tickets have a Fix
version 
before cutting the release, but looks like this fell through the cracks :(

I will fix it for now.


On Thu, Feb 4, 2016 at 10:16 AM, haosdent  wrote:

> Hi, David. I could saw you commit in 0.27
>
> https://github.com/apache/mesos/blob/0.27.0/3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> Why you said it is missing?
>
> On Fri, Feb 5, 2016 at 2:11 AM, David Forsythe 
> wrote:
>
> > Hi,
> >
> > A few changes for FreeBSD support landed in this release (at least
> > partially), but they don't seem to have made it into CHANGELOG. More
> > concerning is that a file in stout seems to be missing[1].
> >
> > For CHANGELOG, I assume I did something wrong in JIRA (example ticket:
> [2]
> > -- if something is wrong there, please let me know), but I'm not sure
> what
> > do about getting new files included. What can I do to make sure that
> > included changes are complete in future releases?
> >
> > Thanks!
> >
> > [1] 3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > [2] https://issues.apache.org/jira/browse/MESOS-1563
> >
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: Questions about release process

[Neil Conway]

freebsd.hpp is missing from the 0.27 release tarball, presumably
because 3rdparty/libprocess/3rdparty/stout/include/Makefile.am was not
updated to account for it. I'll send an RR shortly.

Neil

On Thu, Feb 4, 2016 at 10:16 AM, haosdent  wrote:
> Hi, David. I could saw you commit in 0.27
> https://github.com/apache/mesos/blob/0.27.0/3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> Why you said it is missing?
>
> On Fri, Feb 5, 2016 at 2:11 AM, David Forsythe  wrote:
>
>> Hi,
>>
>> A few changes for FreeBSD support landed in this release (at least
>> partially), but they don't seem to have made it into CHANGELOG. More
>> concerning is that a file in stout seems to be missing[1].
>>
>> For CHANGELOG, I assume I did something wrong in JIRA (example ticket: [2]
>> -- if something is wrong there, please let me know), but I'm not sure what
>> do about getting new files included. What can I do to make sure that
>> included changes are complete in future releases?
>>
>> Thanks!
>>
>> [1] 3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
>> [2] https://issues.apache.org/jira/browse/MESOS-1563
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang