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 process documentation #215

Merged
merged 1 commit into from
May 22, 2018

Conversation

markmandel
Copy link
Member

Outlines a 6 week release process, with included templates for a release issue and github release.

The make do-release will need to be updated once this has been approved, and make gen-changelog will also need to implemented.

Closes #203

Outlines a 6 week release process, with included
templates for a release issue and github release.

The `make do-release` will need to be updated once
this has been approved, and `make gen-changelog` will
also need to implemented.

Closes googleforgames#203
@markmandel markmandel added the area/meta Organisational matters. e.g. Governance, release cycles, etc. label May 22, 2018
@markmandel markmandel added this to the 0.2 milestone May 22, 2018
@agones-bot
Copy link
Collaborator

Build Succeeded 👏

Build Id: 648c9914-d87e-42cd-a72e-c1c0271d6c97

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

@cyriltovena
Copy link
Collaborator

Should we talk about versioning ? Are those major releases ?

@markmandel
Copy link
Member Author

I figured we'd outline a process for the while we are currently in alpha. When we are ready to go 1.0, then let's worry about semver and when major versions happen, etc. Start simple 😄

@markmandel markmandel merged commit 44945e0 into googleforgames:master May 22, 2018
@markmandel markmandel deleted the docs/releases branch May 22, 2018 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/meta Organisational matters. e.g. Governance, release cycles, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants