Skip to content
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

Set Dashboard UI version to v1.1.0 #27869

Merged
merged 1 commit into from
Jun 22, 2016

Conversation

bryk
Copy link
Contributor

@bryk bryk commented Jun 22, 2016

Analytics

This is our final release for this quarter.

Release info and changelog will go there:
https://github.com/kubernetes/dashboard/releases/tag/v1.1.0

This is our final release for this quarter.

Release info, changelog will go there:
https://github.com/kubernetes/dashboard/releases/tag/v1.1.0
@bryk bryk added the release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. label Jun 22, 2016
@bryk bryk added this to the v1.3 milestone Jun 22, 2016
@bryk
Copy link
Contributor Author

bryk commented Jun 22, 2016

@pwittrock Can you take care of this?

@k8s-github-robot k8s-github-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 22, 2016
@k8s-bot
Copy link

k8s-bot commented Jun 22, 2016

GCE e2e build/test passed for commit aba3349.

@roberthbailey roberthbailey added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 22, 2016
@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Jun 22, 2016

GCE e2e build/test passed for commit aba3349.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 73b0b31 into kubernetes:master Jun 22, 2016
@bryk bryk deleted the dashboard-v1.1.0 branch June 23, 2016 05:53
@erictune
Copy link
Member

erictune commented Jul 2, 2016

@bryk Does this PR require action by the user when upgrading from 1.2.x to 1.3.0? (Think about non-developer users.) If so, please edit your first comment to have a release-note block, like in #28132. If it is just an optional feature, please change the label to just release-note. If it is not a complete feature by itself, then apply "release-note-none" label instead.

@bryk bryk added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. labels Jul 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants