-
Notifications
You must be signed in to change notification settings - Fork 40k
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 Heapster to stable version 1.0.0 #22993
Merged
Merged
+12
−12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
piosz
added
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
cherrypick-candidate
labels
Mar 15, 2016
LGTM |
mwielgus
added
the
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
label
Mar 15, 2016
k8s-github-robot
added
the
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
label
Mar 15, 2016
Labelling this PR as size/S |
GCE e2e build/test passed for commit 1f57718. |
LGTM |
bgrant0607
added
the
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
label
Mar 15, 2016
pwittrock
pushed a commit
that referenced
this pull request
Mar 15, 2016
Bumped Heapster to stable version 1.0.0
bgrant0607
removed
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
cherrypick-candidate
labels
Mar 15, 2016
eparis
added
cherrypick-candidate
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
labels
Mar 15, 2016
eparis
pushed a commit
to eparis/kubernetes
that referenced
this pull request
Mar 15, 2016
Bumped Heapster to stable version 1.0.0 (cherry picked from commit 70036b3)
Commit 8603db4 found in the "release-1.2" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this s an error find help to get your PR picked. |
piosz
added
the
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
label
Mar 16, 2016
shyamjvs
pushed a commit
to shyamjvs/kubernetes
that referenced
this pull request
Dec 1, 2016
Bumped Heapster to stable version 1.0.0 (cherry picked from commit 70036b3)
shouhong
pushed a commit
to shouhong/kubernetes
that referenced
this pull request
Feb 14, 2017
Bumped Heapster to stable version 1.0.0 (cherry picked from commit 70036b3)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #22979
This version has no changes comparing to v1.0.0-beta2 and minor ones comparing to v1.0.0-beta1.