bugfix release 0.5.1 #1079

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

Projects

None yet

2 participants

@josef-pkt
Member

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

@josef-pkt
Member

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
Member

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
Member

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
Member

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