-
Notifications
You must be signed in to change notification settings - Fork 14
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
Comments
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. |
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. |
Sounds good. I will get that LU decomp thinger going... also, I found my GPG keys. Yay. |
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. |
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. |
The release is out. Now let's concentrate on polishing up the code base for the first milestone release. |
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.
The text was updated successfully, but these errors were encountered: