Re: are mesos package version names predictable?

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

Re: are mesos package version names predictable?

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

Re: are mesos package version names predictable?

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

Move implementations of Framework struct functions out of master.hpp

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

[ANNOUNCE] Deprecating non JSON credentials

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

Re: are mesos package version names predictable?

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

Re: are mesos package version names predictable?

+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)

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

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: >

Re: Questions about release process

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 >

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

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

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

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

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

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

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

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

Re: Questions about release process

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 > >

Re: Questions about release process

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

Re: Questions about release process

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

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

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

Questions about release process

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

Re: Questions about release process

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

Re: Questions about release process

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