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

bugfix release 0.5.1 #1079

Closed
josef-pkt opened this issue Sep 12, 2013 · 4 comments

Comments

Projects
None yet
2 participants
@josef-pkt
Copy link
Member

commented Sep 12, 2013

last issue for 0.5.1
(to keep milestone open in case it's empty of other issues)

@josef-pkt

This comment has been minimized.

Copy link
Member Author

commented Nov 21, 2013

that's what I get currently with backport_pr.py

Marked PR closed without merge: 1058
The following PRs should be backported:
#1089
#1124
#1125
#1057
#1117
#1071
#1075
#1077
#1149
#1118
#1157

there are still some open issues in the milestone 0.5.1

@jseabold

This comment has been minimized.

Copy link
Member

commented Nov 23, 2013

These are all merged. Provided everything looks good, we need to merge #1142, but not before we're sure that nothing else needs to go into 0.5.1. Backport that, then tag and release. I'll look into getting the SDK setup on windows 8, but from what I've read this might not be so easy.

@josef-pkt

This comment has been minimized.

Copy link
Member Author

commented Nov 23, 2013

Thanks for doing the "git work". I'm glad that we can merge again into master without worrying about how it affects 0.5.x.

I will start testing most likely tomorrow and check if we missed something. (today it's still cluster robust and family)

@jseabold

This comment has been minimized.

Copy link
Member

commented Sep 20, 2014

Closing this. We should just release 0.6 at this point.

@jseabold jseabold closed this Sep 20, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.