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

0.8.0 Release #1160

Closed
grondo opened this issue Aug 22, 2017 · 10 comments
Closed

0.8.0 Release #1160

grondo opened this issue Aug 22, 2017 · 10 comments

Comments

@grondo
Copy link
Contributor

grondo commented Aug 22, 2017

We have a new toss release coming up, so we should probably tag 0.8.0 soon (this week?). I'll take a stab at the release notes and paste it here.

I think there is a bunch of issues tied to the 0.8.0 milestone. We should promote most of those to 0.9.0, and also decide if we want the pending KVS work to land in 0.8.0 or 0.9.0.

flux-core version 0.8.0 (2017-08-xx)

Fixes

New Features

Cleanup

Testing

Documentation

@garlick
Copy link
Member

garlick commented Aug 22, 2017

I would say it might be a bit bold to drop those KVS changes in right before a release tag.

We should definitely try to get sched tagged and pushed out in that TOSS release though.

Can #925 (ppc64le buildfarm issue) wait until I'm back next week? I'm not sure I can get much done on that one remotely.

@garlick
Copy link
Member

garlick commented Aug 22, 2017

Er #918 might be the one? #925 is closed.

@garlick
Copy link
Member

garlick commented Aug 22, 2017

I would say it might be a bit bold to drop those KVS changes in right before a release tag.

Oh then again, it's not like we're in production with flux. Maybe moving forward is the right thing. If we can get #1154 merged early in the week we'll have a few days to discover any fallout.

(Sorry for my chatty comments, spamming everybody)

@grondo
Copy link
Contributor Author

grondo commented Aug 22, 2017

Oh then again, it's not like we're in production with flux.

Yes, though I think we'll definitely want something stable to make it into that release. If we have a set of KVS changes (including the utility changes) we could assign those to 0.9.0 which could be tagged in a week or a month.

I'm fine with including kvs updates though, just wanted to argue the other side.

I could investigate #918 while you're out if that's helpful. Seems like a straightforward buildfarm problem.

@chu11
Copy link
Member

chu11 commented Aug 22, 2017

I would lean towards #1154 being in 0.9.0 as well. While PRs like #1158 and #1159 aren't a necessity or requirement, they do feel somewhat important to be in the release as well.

@garlick
Copy link
Member

garlick commented Aug 22, 2017

OK, works for me, and I certainly don't mind "sharing" #918 - just didn't want to dump it on anybody since I had volunteered.

@grondo
Copy link
Contributor Author

grondo commented Aug 22, 2017

@chu11, just to clarify, you are proposing we tag 0.8.0 without #1154, and assign that PR and #1158 and #1159 to 0.9.0, right?

@chu11
Copy link
Member

chu11 commented Aug 22, 2017

@grondo yes, correct

@grondo
Copy link
Contributor Author

grondo commented Aug 23, 2017

I added a first cut of the NEWS.md additions to the first comment above.

@garlick
Copy link
Member

garlick commented Aug 23, 2017

Thanks for putting together the notes @grondo!

@grondo grondo closed this as completed Aug 24, 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

No branches or pull requests

3 participants