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

Release 0.12.0 #983

Merged
merged 1 commit into from
Aug 7, 2019
Merged

Conversation

markmandel
Copy link
Member

No description provided.

@markmandel markmandel added the kind/release Checklist for a release label Aug 6, 2019
@markmandel markmandel added this to the 0.12.0 milestone Aug 6, 2019
@agones-bot
Copy link
Collaborator

Build Succeeded 👏

Build Id: cf73eac5-2ab4-4d20-ad9f-61474af99de0

The following development artifacts have been built, and will exist for the next 30 days:

A preview of the website (the last 30 builds are retained):

To install this version:

  • git fetch https://github.com/GoogleCloudPlatform/agones.git pull/983/head:pr_983 && git checkout pr_983
  • helm install install/helm/agones --namespace agones-system --name agones --set agones.image.tag=0.12.0-c08b457

Check the <a href="https://github.com/googleforgames/agones/tree/release-0.12.0-rc" data-proofer-ignore>README</a> for details on features, installation and usage.

**Implemented enhancements:**
Check the <a href="https://github.com/googleforgames/agones/tree/release-0.12.0-rc" >README</a> for details on features, installation and usage.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like this shouldn't have the rc extension in it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the release candidate post - so, yes it should? (the change here is removing the data-proofer-ignore tag from the link)

@@ -1,5 +1,19 @@
# Changelog

## [v0.12.0](https://github.com/googleforgames/agones/tree/v0.12.0) (2019-08-06)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On the blog page it lists all of the RC changes but here it look like the release doesn't have much different (because they are all captured in the release candidate). Is that how it's been done in the past?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I tend to copy new features, etc through from RC->Stable for release notes, I figured users will be looking at either and/or stable to see what the new features where.

The changelog is auto generated, and its all in one list, so I figured it was easy to peruse down, so its left as is.

Happy to take other suggestions on how to do this though.

@markmandel markmandel merged commit fbc2f2f into googleforgames:master Aug 7, 2019
@markmandel markmandel deleted the release/0.12.0 branch August 7, 2019 00:33
Namespace: default
Labels: <none>
Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"stable.agones.dev/v1alpha1","kind":"Fleet","metadata":{"annotations":{},"name":"simple-udp","namespace":"default"},"spec":{"replicas":2,...
API Version: stable.agones.dev/v1alpha1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why removing the examples? Shouldn't them be replaced with v1 version of the same example?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep - that's the next line down after this. This is removing and cleaning up the pre-v1 example

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/release Checklist for a release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants