Hello devs and users,
The vote for Mesos 1.2.0 (rc2) has passed with the following votes:
+1 (Binding)
--
*** Adam B
*** Vinod Kone
*** Joseph Wu
-0
--
*** Jie Yu, for MESOS-7208
There were no -1 votes.
Please find the release at:
https
se,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.
> >>> 04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> >>> > [image: Failed]
> >>> > <https://builds.apach
amp;(!ubuntu-us1)&&(!ubuntu-eu2)/>
>>> > cmake
>>> > [image: Success]
>>> > <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel
>>> ease/30/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--verbose
>>> ,ENVIRONMENT=GLOG_v=1%20MESOS_VERBO
t; now treats recovered frameworks very similarly to frameworks
>> that are
>> >> > registered
>> >> > but currently disconnected. For example, recovered frameworks
>> will be
>> >> > reported
>> >> > via the normal "frameworks" key when querying HTTP endpoints.
>
1)&&(!ubuntu-eu2)/>
> >
> > On Wed, Mar 1, 2017 at 9:24 AM, Greg Mann <g...@mesosphere.io> wrote:
> >
> >> I wanted to give a heads up on a flaky test failure I've encountered
> while
&
RC: 'DockerRuntimeIsolatorTest.ROO
>> T_INTERNET_CURL_DockerDefaultEntryptRegistryPuller'. One issue related to
>> this test was resolved recently (https://issues.apache.org/
>> jira/browse/MESOS-6001), but this seems to be a separate issue (
>>
gt; triage yet so I'm not sure if this represents a legitimate bug, but I
> thought I'd email here to increase visibility while the vote is out.
>
> Cheers,
> Greg
>
>
> On Fri, Feb 24, 2017 at 1:14 AM, Adam Bordelon <a...@mesosphere.io> wrote:
>
> > Dear Mes
<a...@mesosphere.io> wrote:
> Dear Mesos developers and users,
>
> Please vote on releasing the following candidate as Apache Mesos 1.2.0.
>
> 1.2.0 includes the following:
>
>
> *
Dear Mesos developers and users,
Please vote on releasing the following candidate as Apache Mesos 1.2.0.
1.2.0 includes the following:
* [MESOS-5931] - **Experimental** Support auto backend in Mesos
Containerizer
sos 1.2,0
> ?
>
> 发件人: Adam Bordelon <a...@mesosphere.io>
> 答复: "user@mesos.apache.org" <user@mesos.apache.org>
> 日期: 2017年2月10日 星期五 上午9:56
> 至: dev <d...@mesos.apache.org>, "user@mesos.apache.org" <
> user@mesos.apache.org>
> 主题: Re: Meso
>
日期: 2017年2月10日 星期五 上午9:56
至: dev <d...@mesos.apache.org<mailto:d...@mesos.apache.org>>,
"user@mesos.apache.org<mailto:user@mesos.apache.org>"
<user@mesos.apache.org<mailto:user@mesos.apache.org>>
主题: Re: Mesos 1.2.0
Good news, everyone!
Mesos 1.2.0-rc
Good news, everyone!
Mesos 1.2.0-rc1 has been cut, the `1.2.x` branch has been created, and the
version in `master` was bumped to 1.3.0!
This was delayed due to last-minute blockers and personal issues with the
mvn gpg plugin. :(
As of now, please set fixVersion to 1.3.0 for any newly resolved
Mesos 1.2.0 now has *0 blockers left*! I'll cut the 1.2.0-rc1 from master
tomorrow.
There are still 6 Critical issues and 16 Major issues with
targetVersion/fixVersion set to 1.2.0 though.
Finish them before the cut tomorrow, or you'll have to beg me to
cherry-pick them instead of deferring them
Mesos 1.2.0 status update:
- We have 12 blockers
<https://issues.apache.org/jira/issues/?jql=filter%20%3D%20%22Mesos%201.2%22%20AND%20status%20!%3D%20Resolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20status%20ASC%2C%20assignee%20DESC>
left, 7 of which are not yet "In Progress&
It's about time for Mesos 1.2.0, given our two-month release cadence. I
volunteer to be release manager, and I'd like to get a new committer or two
to help out. Any volunteers?
I expect to cut rc1 in early January, once all Blockers (and most Critical
issues) have been resolved/deferred. Here's
15 matches
Mail list logo