Thanks for the fix Jie!
Tim
On Fri, Apr 24, 2015 at 2:38 PM, Jie Yu j...@twitter.com.invalid wrote:
Tim's patch cause a few compiler warnings. I committed a fix (just added to
the spreadsheet).
On Fri, Apr 24, 2015 at 2:35 PM, Jie Yu j...@twitter.com wrote:
Now that MESOS-2601 has landed,
Now that MESOS-2601 has landed, shall we include it in 0.22.1(-rc5) too?
+1
On Fri, Apr 24, 2015 at 2:34 PM, Adam Bordelon a...@mesosphere.io wrote:
Added MESOS-2643 to the cherry-pick spreadsheet
Tim's patch cause a few compiler warnings. I committed a fix (just added to
the spreadsheet).
On Fri, Apr 24, 2015 at 2:35 PM, Jie Yu j...@twitter.com wrote:
Now that MESOS-2601 has landed, shall we include it in 0.22.1(-rc5) too?
+1
On Fri, Apr 24, 2015 at 2:34 PM, Adam Bordelon
Added MESOS-2643 to the cherry-pick spreadsheet
https://docs.google.com/a/mesosphere.io/spreadsheets/d/1OzAWNjAL4zKtI-jOJqaQUcDNlnrNik2Dd7dHhwFLKcI/edit#gid=0
.
Now that MESOS-2601 has landed, shall we include it in 0.22.1(-rc5) too?
On Wed, Apr 22, 2015 at 2:58 PM, Benjamin Mahler
One regression in 0.22.x we missed:
https://issues.apache.org/jira/browse/MESOS-2643
Here, the python bindings are not backwards compatible in that they disable
implicit acknowledgements by default. The fix is trivial, and I have a
review linked below. Can we get this in 0.22.1?
Linked it with the release ticket as a blocker.
The fix is committed.
On Wed, Apr 22, 2015 at 2:53 PM, Benjamin Mahler bmah...@twitter.com
wrote:
One regression in 0.22.x we missed:
https://issues.apache.org/jira/browse/MESOS-2643
Here, the python bindings are not backwards compatible in
I also think we should push that fix for 0.23.0, it will take time to
review and merge.
Tim
On Tue, Apr 14, 2015 at 10:17 PM, Benjamin Hindman
b...@eecs.berkeley.edu wrote:
Yes, fixing it in 0.23.0 SGTM.
On Tue, Apr 14, 2015 at 10:02 PM, Jie Yu yujie@gmail.com wrote:
I am just asking if
Also, this one:
https://issues.apache.org/jira/browse/MESOS-2601
This sounds like a non trivial fix.
- Jie
On Tue, Apr 14, 2015 at 6:35 PM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
Per Nik's comment here:
Based on input from Vinod and Adam; I will reduce the scope on the point
Per Nik's comment here:
Based on input from Vinod and Adam; I will reduce the scope on the point
release to focus on MESOS-1795 and MESOS-2583.
I will move the other tickets back to 0.23.0 if you don't have any
objections - let me know if you have any tickets which were regressions in
Hey Nik, any progress on this? Is the spreadsheet up-to-date?
On Wed, Apr 8, 2015 at 1:00 AM, Adam Bordelon a...@mesosphere.io wrote:
Hi Adam,
Yes, once we have finalized the scope of the point release, Niklas will
send out an announcement of Mesos 0.22.1-rc1 (release candidate) which we
I think the plan is to cut a new RC by sometime tomorrow. The spreadsheet
is up-to-date, just need to cherry-pick and modify the change-log.
Joris
On Tue, Apr 14, 2015 at 5:37 PM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
Hey Nik, any progress on this? Is the spreadsheet up-to-date?
Yes, fixing it in 0.23.0 SGTM.
On Tue, Apr 14, 2015 at 10:02 PM, Jie Yu yujie@gmail.com wrote:
I am just asking if you guys want to fix that for 0.22.1 or not. It sounds
to me a non trivial fix. Given the bug is there for quite a while, maybe we
can fix it in 0.23.0?
- Jie
On Tue, Apr
I am just asking if you guys want to fix that for 0.22.1 or not. It sounds
to me a non trivial fix. Given the bug is there for quite a while, maybe we
can fix it in 0.23.0?
- Jie
On Tue, Apr 14, 2015 at 9:55 PM, Benjamin Hindman b...@eecs.berkeley.edu
wrote:
We are going to include MESOS-2614
We are going to include MESOS-2614 (it's a really trivial fix).
Jie, where did you get MESOS-2601 from? That's definitely not in the
spreadsheet.
On Tue, Apr 14, 2015 at 7:40 PM, Jie Yu yujie@gmail.com wrote:
Also, this one:
https://issues.apache.org/jira/browse/MESOS-2601
This sounds
Hi Adam,
Yes, once we have finalized the scope of the point release, Niklas will
send out an announcement of Mesos 0.22.1-rc1 (release candidate) which we
would love you to test any way you can. The email will contain instructions
for building the release candidate and voting in the thread. See
On Fri, Apr 3, 2015 at 3:47 PM, Niklas Nielsen nik...@mesosphere.io wrote:
Based on input from Vinod and Adam; I will reduce the scope on the point
release to focus on MESOS-1795 and MESOS-2583.
Can I help test these in any way?
--
/adam
+1
- Original Message -
From: Niklas Nielsen nik...@mesosphere.io
To: dev dev@mesos.apache.org
Sent: Friday, April 3, 2015 5:47:47 PM
Subject: Re: Suggestion: Mesos 0.22.1 point release
Based on input from Vinod and Adam; I will reduce the scope on the point
release to focus
Hi everyone,
I think we have everything for the point release now:
https://docs.google.com/a/mesosphere.io/spreadsheets/d/1OzAWNjAL4zKtI-jOJqaQUcDNlnrNik2Dd7dHhwFLKcI/edit#gid=0
We planned on making an RC today. So with that in mind, if you have any
urgent issues that needs to go into 0.22.1,
Based on input from Vinod and Adam; I will reduce the scope on the point
release to focus on MESOS-1795 and MESOS-2583.
I will move the other tickets back to 0.23.0 if you don't have any
objections - let me know if you have any tickets which were regressions in
0.22.0.
Also, this will probably
+1 to get it to our users ASAP
On 31 Mar 2015, at 03:01, Niklas Nielsen nik...@mesosphere.io wrote:
Hi all,
Joris and Ben H recently located and fixed a resident bug in the state
abstraction which caused many crashes in the JVM (mostly in conjunction
with Marathon) at scale
Inlined
On 30 March 2015 at 18:47, Dave Lester d...@davelester.org wrote:
Hi Niklas,
Assuming that you'd like to be release manager for this bugfix release,
could you create a JIRA issue to track this and add it to the release
planning wiki?
Hi all,
Joris and Ben H recently located and fixed a resident bug in the state
abstraction which caused many crashes in the JVM (mostly in conjunction
with Marathon) at scale (https://issues.apache.org/jira/browse/MESOS-1795)
We therefore wanted to suggest doing a point release with this fix
+1 for stability.
On Mar 30, 2015 6:26 PM, Benjamin Hindman b...@eecs.berkeley.edu wrote:
Obviously a +1, this is a stability fix we should get to our users as soon
as possible.
On Mon, Mar 30, 2015 at 9:01 PM, Niklas Nielsen nik...@mesosphere.io
wrote:
Hi all,
Joris and Ben H
Obviously a +1, this is a stability fix we should get to our users as soon
as possible.
On Mon, Mar 30, 2015 at 9:01 PM, Niklas Nielsen nik...@mesosphere.io
wrote:
Hi all,
Joris and Ben H recently located and fixed a resident bug in the state
abstraction which caused many crashes in the JVM
Hi Niklas,
Assuming that you'd like to be release manager for this bugfix release,
could you create a JIRA issue to track this and add it to the release
planning wiki?
https://cwiki.apache.org/confluence/display/MESOS/Mesos+Release+Planning
I've already updated the page to reflect the previous
25 matches
Mail list logo
