+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 <[email protected]> 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. >
