ortere <
> jo...@mesosphere.io
> > >
> > wrote:
> >
> > > +1 (binding)
> > >
> > > On Fri, Oct 9, 2015 at 5:36 PM, Niklas Nielsen <nik...@mesosphere.io>
> > > wrote:
> > >
> > > > Hi all,
> > &
Hi all,
The vote for Mesos 0.25.0 (rc3) has passed with the
following votes.
+1 (Binding)
--
Joris Van Remoortere
Michael Park
Brenden Matthews
+1 (Non-binding)
--
Kapil Arya
There were no 0 or -1 votes.
Please find
> wrote:
> >
> > > Hi all,
> > >
> > > Following up with an RC with the build fix suggested by Kapil:
> > >
> > > Please vote on releasing the following candidate as Apache Mesos
> 0.25.0.
> > >
> > >
> > >
> > > 0
h an RC with the build fix suggested by Kapil:
> >
> > Please vote on releasing the following candidate as Apache Mesos 0.25.0.
> >
> >
> >
> > 0.25.0 includes the following:
> >
> >
> >
>
+1 (binding)
On Fri, Oct 9, 2015 at 5:36 PM, Niklas Nielsen <nik...@mesosphere.io> wrote:
> Hi all,
>
> Following up with an RC with the build fix suggested by Kapil:
>
> Please vote on releasing the following candidate as Apache Mesos 0.25.0.
>
>
>
&
Hi all,
Following up with an RC with the build fix suggested by Kapil:
Please vote on releasing the following candidate as Apache Mesos 0.25.0.
0.25.0 includes the following:
* [MESOS-1474] - Experimental
gt; [17:18:48][Step 4/6]if (expected == actual) {
> >>
> >> [17:18:48][Step 4/6] ^
> >>
> >>
> >> Cherry-picking one commit (bfeb070a2aef52f445e "Fixed compiler warning
t;
>
> On Wed, Oct 7, 2015 at 2:32 AM, Joris Van Remoortere <jo...@mesosphere.io>
> wrote:
>
>> +1 (binding)
>>
>> On Mon, Oct 5, 2015 at 11:12 PM, Niklas Nielsen <nik...@mesosphere.io>
>> wrote:
>>
>>> Hi all,
>>>
>>&
ues test.") resolves this issue.
>>
>>
>>
>> On Wed, Oct 7, 2015 at 2:32 AM, Joris Van Remoortere <jo...@mesosphere.io>
>> wrote:
>>
>>> +1 (binding)
>>>
>>> On Mon, Oct 5, 2015 at 11:12 PM, Niklas Nielsen <nik...@mesosphere.io&
gt; wrote:
>
> > +1 (binding)
> >
> > On Mon, Oct 5, 2015 at 11:12 PM, Niklas Nielsen <nik...@mesosphere.io>
> > wrote:
> >
> >> Hi all,
> >>
> >> Please vote on releasing the following candidate as Apache Mesos 0.25.0.
> >>
&
2015 at 2:32 AM, Joris Van Remoortere <jo...@mesosphere.io>
wrote:
> +1 (binding)
>
> On Mon, Oct 5, 2015 at 11:12 PM, Niklas Nielsen <nik...@mesosphere.io>
> wrote:
>
>> Hi all,
>>
>> Please vote on releasing the following cand
Compare(const char*,
>>> const char*, const T1&, const T2&) [with T1 = int; T2 = long unsigned
>>> int;
>>> bool lhs_is_null_literal = false]’
>>>
>>> [17:18:48][Step 4/6] ../../../src/tests/values_tests.cpp:149:3:
>>> required
+1 (binding)
On Mon, Oct 5, 2015 at 11:12 PM, Niklas Nielsen <nik...@mesosphere.io>
wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.25.0.
>
>
>
> 0.
Hi all,
Please vote on releasing the following candidate as Apache Mesos 0.25.0.
0.25.0 includes the following:
* [MESOS-1474] - Experimental support for maintenance primitives.
* [MESOS-2600] - Added master
Hi everyone,
Mesos 0.25.0 rc1 should now be ready for testing! [1]
While we already know of documentation additions we want in RC2, this is
our chance to test and bake the release bits.
*Please keep us posted with any failures, crashes, flaky test, unintuitive
upgrade paths or deprecations we
And here are the release bits:
The candidate for Mesos 0.25.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.0-rc1/mesos-0.25.0.tar.gz
The tag to be voted on is 0.25.0-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.0-rc1
The MD5 checksum
at
>> > needs to get into 0.25.0!
>> >
>> > Thanks,
>> >
>> > Joris, MPark, and Niklas
>> >
>> > On Mon, Sep 14, 2015, 9:23 AM Joris Van Remoortere <jo...@mesosphere.io
>> >
>> > wrote:
>> >
>> > > Followi
to 0.25.0!
>
> Thanks,
>
> Joris, MPark, and Niklas
>
> On Mon, Sep 14, 2015, 9:23 AM Joris Van Remoortere <jo...@mesosphere.io>
> wrote:
>
> > Following in the footsteps of the dashboard for the 0.23.0 release,
> > here is the Mesos 0.25.0 Release Dashboard
&
Joris Van Remoortere <jo...@mesosphere.io>
wrote:
> Following in the footsteps of the dashboard for the 0.23.0 release,
> here is the Mesos 0.25.0 Release Dashboard
> <
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12326859
> >
>
> T
Following in the footsteps of the dashboard for the 0.23.0 release,
here is the Mesos 0.25.0 Release Dashboard
<https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12326859>
This dashboard was very successful at reducing the time required to triage
the first release candidate.
A minor nit...
Please use the "target" version for those you _would like_ to land in 0.25
(with reasonably high degree of certainty by now ;-) hopefully) and "fix
version" only when resolved.
That should make constructing release notes less painstaking.
Thanks!
—
Sent from my
Hi folks,
With 0.24.0 out the door, we need to start focus on 0.25.0.
As to planning, we will aim to release by *October 5th (just before
MesosCon EU)*. In order to test, fix and stabilize, we will try to tag a
release by *September 23th*. That leaves us with two weeks to land the
final patches
On 30 August 2015 at 16:00, Dave Lester wrote:
> Hi Niklas,
>
> Could you create a JIRA issue tracking this release? A great example
> would be what was created for the 0.22.0 release and promotes more
> transparency IMO about what is going in a release:
>
Hi Niklas,
Could you create a JIRA issue tracking this release? A great example
would be what was created for the 0.22.0 release and promotes more
transparency IMO about what is going in a release:
https://issues.apache.org/jira/browse/MESOS-2248
Additionally, can you add a link to that JIRA
Hi Nik,
I'd like to co-manage with you as I am invested in Maintenance Primitives
:-)
Joris
On Thu, Aug 27, 2015 at 9:25 PM, Michael Park mcyp...@gmail.com wrote:
Hey Niklas,
As we discussed offline, I'm happy to co-manage or shadow this release.
I would also like to add the beta
Hi folks,
While we have 0.24.0 in flight (voting and fixing is in progress), with a
release cadence of 1 month, we should consider to start thinking about
0.25.0.
I have cycles to release manage this one (and bring some of the newer
committers on for shadowing). If others want to take this on
Hey Niklas,
As we discussed offline, I'm happy to co-manage or shadow this release.
I would also like to add the beta follow-up features for persistence
primitives (dynamic reservation + persistent volume):
- Operator API
- Authorization
Thanks,
MPark.
On Thu, Aug 27, 2015 at 7:24 PM
27 matches
Mail list logo