New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bumped Mesos to latest 1.2.x (f8706e5). #2104
Bumped Mesos to latest 1.2.x (f8706e5). #2104
Conversation
This repo has @mesosphere-mergebot integration. You can interact with the following commands.
|
@mesosphere-mergebot bump-ee |
Enterprise Bump PR: mesosphere/dcos-enterprise/pull/1720 |
The |
@mesosphere-mergebot label [Ready For Review] |
@vinodkone @adam-mesos: When you get a chance, can you fellas review this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This Mesos bump LGTM.
We need to have a DC/OS JIRA ticket that tracks this change, and it must be linked in this pull request. |
@jgehrcke Updated PR with https://jira.mesosphere.com/browse/DCOS_OSS-1897 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 Identical to Mesos 1.2.3-rc1 except for the CHANGELOG update. Good enough for me!
High-level description
Bumped Mesos to latest 1.2.x (f8706e5).
Corresponding DC/OS tickets (obligatory)
Related tickets (optional)
Checklist for all PRs
Tests covered by Mesos test suite.
Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath
packages
), then in addition to the above please also include:PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:
It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.