Mesos 1.2.0 status update: - We have 12 blockers <https://issues.apache.org/jira/issues/?jql=filter%20%3D%20%22Mesos%201.2%22%20AND%20status%20!%3D%20Resolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20status%20ASC%2C%20assignee%20DESC> left, 7 of which are not yet "In Progress", 5 without a Shepherd, 2 Unassigned. - I don't foresee us cutting an rc1 for at least another week while we work on these remaining blockers. - There are another ~50 issues targeted for 1.2, so squeeze them in this week if you can. - Your help is appreciated a) fixing blockers, b) updating JIRAs, and c) *documenting your new features.*
Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329897 On Mon, Dec 26, 2016 at 7:04 PM, Adam Bordelon <a...@mesosphere.io> wrote: > It's about time for Mesos 1.2.0, given our two-month release cadence. I > volunteer to be release manager, and I'd like to get a new committer or two > to help out. Any volunteers? > > I expect to cut rc1 in early January, once all Blockers (and most Critical > issues) have been resolved/deferred. Here's how you can help: > - Set *Target Version = "1.2.0"* for anything that needs to go into this > release. Anything not critical can wait for Mesos 1.3. > - Upgrade release blockers to *"Blocker" priority*. Use "Critical" for > any issues that would be painful (but possible) to ship Mesos 1.2 without. > > Mesos 1.2 release dashboard: https://issues.apache.org/ > jira/secure/Dashboard.jspa?selectPageId=12329897 > > Cheers, > -Adam- >
