Re: 1.0 Release Candidate

> +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me >>> >>> >>> > Date: Sun, 29 May 2016 02:31:47 -0700 >>> > Subject: Re: 1.0 Release Candidate >>> > From: a...@mesosphere.io >>> > To: u...@mesos.apache.org >>&g

Re: 1.0 Release Candidate

t; Platform OpenSource Technology, STG, IBM GCG >> +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me >> >> >> > Date: Sun, 29 May 2016 02:31:47 -0700 >> > Subject: Re: 1.0 Release Candidate >> > From: a...@mesosphere.io >> > To: u...@me

Re: 1.0 Release Candidate

FYI, I made an alternate 1.0 release dashboard with a longer timeframe for the created vs. resolved chart, and added a couple of my favorite widgets. Feel free to use anything you find helpful. https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12328256 On Thu, May 26, 2016 at

Re: 1.0 Release Candidate

This is the release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12328255 *NOTE: *If you have set a Fix Version of 0.29.0 on a ticket that is not a blocker for 0.29.0/1.0 release, please unset the fix version. On Thu, May 26, 2016 at 3:44 PM, Vinod Kone

Re: 1.0 Release Candidate

Thanks for asking the questions Zameer. Wanted to give some clarification regarding the thought process for releasing 1.0. The reason for cutting a 1.0, is because we want to signal that the Mesos project has reached a level of maturity to the wider community. Among other things we are confident

Re: 1.0 Release Candidate

I might be in the minority here, but I think cutting an RC for 1.0 right now is very aggressive. Does there exist even a single framework that uses the Scheduler HTTP API or the Executor HTTP API? Does anyone even use these APIs in production? Is there a single entity that uses the Operator API to

Re: 1.0 Release Candidate

Does this mean the work to deprecate the docker containerizer will be post-1.0, or have those plans changed? On Wednesday, May 25, 2016, Vinod Kone wrote: > Hi folks, > > As discussed in the previous community sync, we plan to cut a release > candidate for our next release

Re: 1.0 Release Candidate

Post 1.0. Jie might be able to shed more light regarding the plans for Docker Containerizer. On Wed, May 25, 2016 at 12:10 PM, Jeff Schroeder wrote: > Does this mean the work to deprecate the docker containerizer will be > post-1.0, or have those plans changed? > >

Re: 1.0 Release Candidate

Jeff, Yes, deprecating the docker containerizer will be post-1.0. The plan has not changed. In fact, we are making very good progress on the unified containerizer side (see this doc ). We'll continue to support Docker

Re: 1.0 Release Candidate

I'm guessing you mean the "medium term" bullet point on the Roadmap ( https://cwiki.apache.org/confluence/display/MESOS/Roadmap): > >- Deprecate Docker containerizer (in favor of Unified containerizer w/ >Docker support) > > This was never meant to be done as part of the 1.0 release. I'm

Re: 1.0 Release Candidate

As part of this, I'm going to: 1) Update configure.ac and CMakeLists to point to 1.0.0 version. Note that if someone is building off master, this might be a little weird because up until this change their builds would've 0.29.0 version and after this change it would be 1.0.0. But I guess it's

1.0 Release Candidate

Hi folks, As discussed in the previous community sync, we plan to cut a release candidate for our next release (1.0) early next week. 1.0 is mainly centered around new APIs for Mesos. Please take a look at MESOS-338 for blocking issues. We got