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

Roadmap: Release 0.4.0 #151

Closed
11 tasks done
memmett opened this issue Feb 4, 2015 · 7 comments
Closed
11 tasks done

Roadmap: Release 0.4.0 #151

memmett opened this issue Feb 4, 2015 · 7 comments

Comments

@memmett
Copy link
Member

memmett commented Feb 4, 2015

I think we're getting close to being able to release 0.4.0.

Blockers

Punters

Thoughts? Please move things around if you'd like!

After 0.4.0 I think we should consider a 1.0.0 release.

@torbjoernk
Copy link
Contributor

Thanks for bringing this up, @memmett.

I'll try to tackle #127 and #84 this week.

#19 can be closed and forgotten about for now I think.

I'd like to add another point, which I hope to also tackle this week: Testing PFASST++ on our "little toy machines" JUQUEEN and JUDGE. I'd love to have it up and running for v0.4.0.

Updating above list.

@torbjoernk
Copy link
Contributor

I guess, it's time for wrapping up. Once I've tested the Boris-PFASST stuff more thoroughly (it works! 🎆) I'll create the release branch by end of the week. So we can get the v0.4.0 release out by end of the month without a big hazel.

@memmett
Copy link
Member Author

memmett commented Apr 13, 2015

Sounds good. I will get that LU decomp thinger going... also, I found my GPG keys. Yay.

@memmett
Copy link
Member Author

memmett commented Apr 13, 2015

LU decomp seems to be working. Will wait until Jenkins is happy before checking that one off. Going to push all the 'punters' off to 1.0.

@torbjoernk
Copy link
Contributor

I've just created the release branch. Going to tweak Jenkins a bit to hopefully behave a little better. 😑

Now it's time for a few documentation and cleanup PRs 😃

Plus the Boris-PFASST. Or should we postpone this to v1.0.0? Although 1.0.0 was not intended for new features.

@torbjoernk
Copy link
Contributor

I'm going to tag the first release candidate once #184 and #185 are merged. While doing that I'll prepare the changelog.

Any further points you guys want to see in v0.4.0? I think I'll do the release next week.

@torbjoernk
Copy link
Contributor

The release is out. Now let's concentrate on polishing up the code base for the first milestone release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants