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

Prepare for v0.12.0 release #81

Merged
merged 1 commit into from
Feb 3, 2017
Merged

Conversation

Xymph
Copy link
Collaborator

@Xymph Xymph commented Feb 3, 2017

I've programmed against and used the current codebase for quite a while, encountered no problems, and thought of no further changes to make. So I figure it's time to wrap it up as a new stable release. Agreed, @waldyrious ?

@waldyrious
Copy link
Collaborator

Certainly. Any potential issues can be addressed as bugfix/patch releases in any case :) Do you need help with anything for this? I will at least make sure to document the release process.

@Xymph
Copy link
Collaborator Author

Xymph commented Feb 3, 2017

Do you need help with anything for this?

I've done the 0.11 release already.

I will at least make sure to document the release process.

Ok, do you need this PR to stay open for that?

@waldyrious
Copy link
Collaborator

Ok, do you need this PR to stay open for that?

No, there's no reason for it to block the release. I was just mentioning that (and publicly committing to do so) :P

@Xymph Xymph merged commit 52ba7e8 into hamstar:master Feb 3, 2017
@Xymph Xymph deleted the 81-prepare-release branch February 3, 2017 20:16
waldyrious added a commit that referenced this pull request Mar 11, 2017
see #81 for context
@waldyrious waldyrious mentioned this pull request Mar 11, 2017
waldyrious added a commit that referenced this pull request Mar 13, 2017
see #81 for context
waldyrious added a commit that referenced this pull request Mar 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants