You will notice a lot of noise as I update the fix versions in JIRA. In the past we've sometimes had JIRA automatically move everything unresolved to the next version when we do the release. However, this leads to inaccurate fix versions so I'm opting to unset fix versions rather than default to 0.20.0 arbitrarily.
Please let me know if there are any issues with this. On Fri, May 16, 2014 at 1:03 PM, Benjamin Mahler <[email protected]>wrote: > Update: Aiming to cut for next Friday or so. > > Will start wrangling 0.19.0 JIRA tickets as appropriate. > > > On Tue, May 6, 2014 at 12:27 PM, Benjamin Mahler < > [email protected]> wrote: > >> On second thought, keeping an accurate 'Fix Version' for 0.19.0 would be >> the better approach than linking things. >> >> I will start to update things that haven't made it in 0.19.0 over the >> coming weeks. >> >> >> On Tue, May 6, 2014 at 12:22 PM, Benjamin Mahler < >> [email protected]> wrote: >> >>> Hi all, >>> >>> In the coming weeks, we would like to cut 0.19.0 on the master branch. I >>> would like to volunteer to be the release manager. >>> >>> I've added a ticket here to help track any dependencies: >>> >>> https://issues.apache.org/jira/browse/MESOS-1311 >>> >>> Namely, there are two major features going out: >>> >>> 1. Adding state to the Master (MESOS-764). The plan is to release this >>> in a non-strict mode, using the replicated log. 0.20.0 will transition to >>> strict operation by default. This allows seamless upgrading (0.18.0 -> >>> 0.19.0 bootstraps the replicated state on a running cluster, 0.19.0 -> >>> 0.20.0 transitions to strict operation). >>> >>> 2. The external containerizer. Is this stable, are there any blocking >>> tickets that should be linked into MESOS-1311? >>> >>> Please comment on that ticket or link in any relevant issues! >>> >>> Ben >>> >> >> >
