Hi, The tracking ticket for the 0.24.0 release is https://issues.apache.org/jira/browse/MESOS-2562
The main feature of this release is going to be v1 (beta) release of the HTTP scheduler API. Hoping to cut an RC early next week, so if there's anything you absolutely need to be in 0.24.0 please land them by EOW. Thanks, On Tue, Jul 21, 2015 at 4:10 PM, Adam Bordelon <a...@mesosphere.io> wrote: > Thanks, Vinod. > > I've got a handful of JIRAs I'd really like to see land in 0.24.0. > https://issues.apache.org/jira/browse/MESOS-2559 Do not use > RunTaskMessage.framework_id. > https://issues.apache.org/jira/browse/MESOS-2600 Add /reserve and > /unreserve endpoints on the master for dynamic reservation > https://issues.apache.org/jira/browse/MESOS-2998 Disable Persistent > Volumes, Dynamic Reservations via master flags > https://issues.apache.org/jira/browse/MESOS-3050 Failing ROOT_ tests in > 0.23.0-rc3 on CentOS 7.1 > https://issues.apache.org/jira/browse/MESOS-3079 `sudo make distcheck` > fails on Ubuntu 14.04 (and possibly other OSes too) > > I understand your desire to untarget the majority of the tickets, since > it's a time-based release, but we might want to keep some of these targeted > so we can track the priority issues. When the actual rc1 cut date > approaches, it's pretty easy to aggressively push things out of the release > that haven't made it. Let me know what you think. > > Cheers, > -A- > > > On Tue, Jul 21, 2015 at 11:02 AM, Vinod Kone <vinodk...@gmail.com> wrote: > > > Hi folks, > > > > I will be the release manager for the upcoming release (ETA early > August). > > > > To prep for the release (and make my life easy) I'm planning to remove > the > > target versions for all *unresolved* tickets that have a target version > > 0.24.0. > > > > I would like folks to explicitly set the target version to 0.24.0* for > > tickets they want to absolutely land in the next release (keeping in mind > > the time frame). If you are unsure, please reach out to me or reply to > this > > thread. > > > > The main blocking feature for this release is going to the new HTTP API. > > > > Thanks, > > Vinod > > > > P.S. If things go according to plan we might make this 1.0 release! > > >
