You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Benjamin Mahler <bm...@apache.org> on 2016/05/04 17:20:02 UTC
Re: stable remote branches
Jie I've highlighted in the doc the backports that remain from the initial
search of fix versions.
Let me know if you'd like any help!
On Mon, Apr 25, 2016 at 7:23 PM, Benjamin Mahler <bm...@apache.org> wrote:
> +user as an FYI
>
> Going forward we'll push directly to these branches as backport decisions
> are made. Since 0.28.x, 0.27.x, and 0.26.x have just been created, here is
> what was already marked for these versions, that we'll have to cherry-pick:
>
> The following need to be cherry-picked for 0.28.2:
> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> [bmahler]
> https://issues.apache.org/jira/browse/MESOS-5253 - Isolator cleanup fix
> [jie]
> https://issues.apache.org/jira/browse/MESOS-5282 - CHECK failure in test
> [jie]
> https://issues.apache.org/jira/browse/MESOS-5238 - Race in mesos
> containerizer [jie] (cause of MESOS-5282)
>
> The following need to be cherry-picked for 0.27.3:
> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> [bmahler]
> https://issues.apache.org/jira/browse/MESOS-4869 - Health checker leaks
> memory [bmahler]
> https://issues.apache.org/jira/browse/MESOS-5021 - process::Subprocess
> memory leak [bmahler] (cause of MESOS-4869)
> https://issues.apache.org/jira/browse/MESOS-4662 - PortMapping network
> isolator should not assume BIND_MOUNT_ROOT is a realpath. [jie]
> https://issues.apache.org/jira/browse/MESOS-4979 - os::rmdir does not
> handle special files [jie]
> https://issues.apache.org/jira/browse/MESOS-5018 - FrameworkInfo
> Capability enum does not support upgrades. [bmahler]
>
> The following need to be cherry-picked for 0.26.2:
> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> [bmahler]
>
> Looks like it's just on jie and I, I've put these together in a doc here
> to capture the progress:
>
> https://docs.google.com/document/d/1DKCn05oFNirXRvX3A-i_h3nLn-0oyJL3vmakjqdarNw/edit?usp=sharing
>
> As always, if you see things that you believe should be backported, let us
> know.
>
> Ben
>
> On Mon, Apr 25, 2016 at 2:47 PM, Vinod Kone <vi...@apache.org> wrote:
>
>> Hi guys,
>>
>> Per the latest guidelines on doing mesos releases and backports, we've
>> created remote branches for releases that are still supported (0.26.x,
>> 0.27.x, 0.28.x).
>>
>> Going forward, any issues that need to be backported or fixed should land
>> in these branches. For backports and *CHANGELOG* updates, make sure to
>> *land
>> them first on the master* before cherry-picking them onto the remote
>> branches.
>>
>> Please let me know if you have any questions/concerns,
>>
>> Thanks,
>> Vinod
>>
>> P.S: Sorry for the commit noise. We won't have this noise from 0.29.0
>> onward since we will push 0.29.x at the same time as 0.29.0.
>>
>
>
Re: stable remote branches
Posted by Jie Yu <yu...@gmail.com>.
Joshua,
Unified containerizer was announced *experiemental* starting from 0.28.0.
It's not stable prior to that and we made a bunch of breaking changes
between 0.27.x and 0.28.x. So I am leaning towards not backporting fixes
for unified containerizer in 0.27.x.
- Jie
On Wed, May 4, 2016 at 10:56 AM, Joshua Cohen <jc...@apache.org> wrote:
> Would you guys be willing to backport
> https://github.com/apache/mesos/commit/7de26f6a to 0.27.3? It's currently
> not possible to run Docker images with the unified containerizer w/ 0.27.2
> because the agent crashes on startup when specifying a local docker
> registry.
>
> On Wed, May 4, 2016 at 12:22 PM, Jie Yu <yu...@gmail.com> wrote:
>
> > Thanks Ben! I've done with the backport for 0.28.2.
> >
> > Will do the rest later today.
> >
> > - Jie
> >
> > On Wed, May 4, 2016 at 10:20 AM, Benjamin Mahler <bm...@apache.org>
> > wrote:
> >
> > > Jie I've highlighted in the doc the backports that remain from the
> > initial
> > > search of fix versions.
> > >
> > > Let me know if you'd like any help!
> > >
> > > On Mon, Apr 25, 2016 at 7:23 PM, Benjamin Mahler <bm...@apache.org>
> > > wrote:
> > >
> > >> +user as an FYI
> > >>
> > >> Going forward we'll push directly to these branches as backport
> > decisions
> > >> are made. Since 0.28.x, 0.27.x, and 0.26.x have just been created,
> here
> > is
> > >> what was already marked for these versions, that we'll have to
> > cherry-pick:
> > >>
> > >> The following need to be cherry-picked for 0.28.2:
> > >> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> > >> [bmahler]
> > >> https://issues.apache.org/jira/browse/MESOS-5253 - Isolator cleanup
> fix
> > >> [jie]
> > >> https://issues.apache.org/jira/browse/MESOS-5282 - CHECK failure in
> > test
> > >> [jie]
> > >> https://issues.apache.org/jira/browse/MESOS-5238 - Race in mesos
> > >> containerizer [jie] (cause of MESOS-5282)
> > >>
> > >> The following need to be cherry-picked for 0.27.3:
> > >> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> > >> [bmahler]
> > >> https://issues.apache.org/jira/browse/MESOS-4869 - Health checker
> leaks
> > >> memory [bmahler]
> > >> https://issues.apache.org/jira/browse/MESOS-5021 -
> process::Subprocess
> > >> memory leak [bmahler] (cause of MESOS-4869)
> > >> https://issues.apache.org/jira/browse/MESOS-4662 - PortMapping
> network
> > >> isolator should not assume BIND_MOUNT_ROOT is a realpath. [jie]
> > >> https://issues.apache.org/jira/browse/MESOS-4979 - os::rmdir does not
> > >> handle special files [jie]
> > >> https://issues.apache.org/jira/browse/MESOS-5018 - FrameworkInfo
> > >> Capability enum does not support upgrades. [bmahler]
> > >>
> > >> The following need to be cherry-picked for 0.26.2:
> > >> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> > >> [bmahler]
> > >>
> > >> Looks like it's just on jie and I, I've put these together in a doc
> here
> > >> to capture the progress:
> > >>
> > >>
> >
> https://docs.google.com/document/d/1DKCn05oFNirXRvX3A-i_h3nLn-0oyJL3vmakjqdarNw/edit?usp=sharing
> > >>
> > >> As always, if you see things that you believe should be backported,
> let
> > >> us know.
> > >>
> > >> Ben
> > >>
> > >> On Mon, Apr 25, 2016 at 2:47 PM, Vinod Kone <vi...@apache.org>
> > wrote:
> > >>
> > >>> Hi guys,
> > >>>
> > >>> Per the latest guidelines on doing mesos releases and backports,
> we've
> > >>> created remote branches for releases that are still supported
> (0.26.x,
> > >>> 0.27.x, 0.28.x).
> > >>>
> > >>> Going forward, any issues that need to be backported or fixed should
> > land
> > >>> in these branches. For backports and *CHANGELOG* updates, make sure
> to
> > >>> *land
> > >>> them first on the master* before cherry-picking them onto the remote
> > >>> branches.
> > >>>
> > >>> Please let me know if you have any questions/concerns,
> > >>>
> > >>> Thanks,
> > >>> Vinod
> > >>>
> > >>> P.S: Sorry for the commit noise. We won't have this noise from 0.29.0
> > >>> onward since we will push 0.29.x at the same time as 0.29.0.
> > >>>
> > >>
> > >>
> > >
> >
>
Re: stable remote branches
Posted by Joshua Cohen <jc...@apache.org>.
Would you guys be willing to backport
https://github.com/apache/mesos/commit/7de26f6a to 0.27.3? It's currently
not possible to run Docker images with the unified containerizer w/ 0.27.2
because the agent crashes on startup when specifying a local docker
registry.
On Wed, May 4, 2016 at 12:22 PM, Jie Yu <yu...@gmail.com> wrote:
> Thanks Ben! I've done with the backport for 0.28.2.
>
> Will do the rest later today.
>
> - Jie
>
> On Wed, May 4, 2016 at 10:20 AM, Benjamin Mahler <bm...@apache.org>
> wrote:
>
> > Jie I've highlighted in the doc the backports that remain from the
> initial
> > search of fix versions.
> >
> > Let me know if you'd like any help!
> >
> > On Mon, Apr 25, 2016 at 7:23 PM, Benjamin Mahler <bm...@apache.org>
> > wrote:
> >
> >> +user as an FYI
> >>
> >> Going forward we'll push directly to these branches as backport
> decisions
> >> are made. Since 0.28.x, 0.27.x, and 0.26.x have just been created, here
> is
> >> what was already marked for these versions, that we'll have to
> cherry-pick:
> >>
> >> The following need to be cherry-picked for 0.28.2:
> >> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> >> [bmahler]
> >> https://issues.apache.org/jira/browse/MESOS-5253 - Isolator cleanup fix
> >> [jie]
> >> https://issues.apache.org/jira/browse/MESOS-5282 - CHECK failure in
> test
> >> [jie]
> >> https://issues.apache.org/jira/browse/MESOS-5238 - Race in mesos
> >> containerizer [jie] (cause of MESOS-5282)
> >>
> >> The following need to be cherry-picked for 0.27.3:
> >> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> >> [bmahler]
> >> https://issues.apache.org/jira/browse/MESOS-4869 - Health checker leaks
> >> memory [bmahler]
> >> https://issues.apache.org/jira/browse/MESOS-5021 - process::Subprocess
> >> memory leak [bmahler] (cause of MESOS-4869)
> >> https://issues.apache.org/jira/browse/MESOS-4662 - PortMapping network
> >> isolator should not assume BIND_MOUNT_ROOT is a realpath. [jie]
> >> https://issues.apache.org/jira/browse/MESOS-4979 - os::rmdir does not
> >> handle special files [jie]
> >> https://issues.apache.org/jira/browse/MESOS-5018 - FrameworkInfo
> >> Capability enum does not support upgrades. [bmahler]
> >>
> >> The following need to be cherry-picked for 0.26.2:
> >> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
> >> [bmahler]
> >>
> >> Looks like it's just on jie and I, I've put these together in a doc here
> >> to capture the progress:
> >>
> >>
> https://docs.google.com/document/d/1DKCn05oFNirXRvX3A-i_h3nLn-0oyJL3vmakjqdarNw/edit?usp=sharing
> >>
> >> As always, if you see things that you believe should be backported, let
> >> us know.
> >>
> >> Ben
> >>
> >> On Mon, Apr 25, 2016 at 2:47 PM, Vinod Kone <vi...@apache.org>
> wrote:
> >>
> >>> Hi guys,
> >>>
> >>> Per the latest guidelines on doing mesos releases and backports, we've
> >>> created remote branches for releases that are still supported (0.26.x,
> >>> 0.27.x, 0.28.x).
> >>>
> >>> Going forward, any issues that need to be backported or fixed should
> land
> >>> in these branches. For backports and *CHANGELOG* updates, make sure to
> >>> *land
> >>> them first on the master* before cherry-picking them onto the remote
> >>> branches.
> >>>
> >>> Please let me know if you have any questions/concerns,
> >>>
> >>> Thanks,
> >>> Vinod
> >>>
> >>> P.S: Sorry for the commit noise. We won't have this noise from 0.29.0
> >>> onward since we will push 0.29.x at the same time as 0.29.0.
> >>>
> >>
> >>
> >
>
Re: stable remote branches
Posted by Jie Yu <yu...@gmail.com>.
Thanks Ben! I've done with the backport for 0.28.2.
Will do the rest later today.
- Jie
On Wed, May 4, 2016 at 10:20 AM, Benjamin Mahler <bm...@apache.org> wrote:
> Jie I've highlighted in the doc the backports that remain from the initial
> search of fix versions.
>
> Let me know if you'd like any help!
>
> On Mon, Apr 25, 2016 at 7:23 PM, Benjamin Mahler <bm...@apache.org>
> wrote:
>
>> +user as an FYI
>>
>> Going forward we'll push directly to these branches as backport decisions
>> are made. Since 0.28.x, 0.27.x, and 0.26.x have just been created, here is
>> what was already marked for these versions, that we'll have to cherry-pick:
>>
>> The following need to be cherry-picked for 0.28.2:
>> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
>> [bmahler]
>> https://issues.apache.org/jira/browse/MESOS-5253 - Isolator cleanup fix
>> [jie]
>> https://issues.apache.org/jira/browse/MESOS-5282 - CHECK failure in test
>> [jie]
>> https://issues.apache.org/jira/browse/MESOS-5238 - Race in mesos
>> containerizer [jie] (cause of MESOS-5282)
>>
>> The following need to be cherry-picked for 0.27.3:
>> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
>> [bmahler]
>> https://issues.apache.org/jira/browse/MESOS-4869 - Health checker leaks
>> memory [bmahler]
>> https://issues.apache.org/jira/browse/MESOS-5021 - process::Subprocess
>> memory leak [bmahler] (cause of MESOS-4869)
>> https://issues.apache.org/jira/browse/MESOS-4662 - PortMapping network
>> isolator should not assume BIND_MOUNT_ROOT is a realpath. [jie]
>> https://issues.apache.org/jira/browse/MESOS-4979 - os::rmdir does not
>> handle special files [jie]
>> https://issues.apache.org/jira/browse/MESOS-5018 - FrameworkInfo
>> Capability enum does not support upgrades. [bmahler]
>>
>> The following need to be cherry-picked for 0.26.2:
>> https://issues.apache.org/jira/browse/MESOS-4705 - Linux perf fix
>> [bmahler]
>>
>> Looks like it's just on jie and I, I've put these together in a doc here
>> to capture the progress:
>>
>> https://docs.google.com/document/d/1DKCn05oFNirXRvX3A-i_h3nLn-0oyJL3vmakjqdarNw/edit?usp=sharing
>>
>> As always, if you see things that you believe should be backported, let
>> us know.
>>
>> Ben
>>
>> On Mon, Apr 25, 2016 at 2:47 PM, Vinod Kone <vi...@apache.org> wrote:
>>
>>> Hi guys,
>>>
>>> Per the latest guidelines on doing mesos releases and backports, we've
>>> created remote branches for releases that are still supported (0.26.x,
>>> 0.27.x, 0.28.x).
>>>
>>> Going forward, any issues that need to be backported or fixed should land
>>> in these branches. For backports and *CHANGELOG* updates, make sure to
>>> *land
>>> them first on the master* before cherry-picking them onto the remote
>>> branches.
>>>
>>> Please let me know if you have any questions/concerns,
>>>
>>> Thanks,
>>> Vinod
>>>
>>> P.S: Sorry for the commit noise. We won't have this noise from 0.29.0
>>> onward since we will push 0.29.x at the same time as 0.29.0.
>>>
>>
>>
>