Uh oh!
There was an error while loading. Please reload this page.
MAINT prepare new release - #600
Conversation
janvanrijn
commented
Dec 4, 2018
Can we try to have #567 in the release as well? I can contribute the example today |
glemaitre
commented
Dec 4, 2018
What is the release schedule. I'll like to have #548 as well and I am willing to finish it up right away. |
mfeurer
commented
Dec 4, 2018
There's not really a release schedule yet and there's no hurry at all. My motivation was to get things out as it has been a while since the last release and there have been multiple new issues for problems which we have already solved in the development branch. Therefore, I'm happy to wait for both PRs to have a nice and consistent release. However, it would be great to get this done within the next few days. |
joaquinvanschoren
commented
Dec 4, 2018
Regression (#560) as well please :) |
mfeurer
commented
Dec 4, 2018
What's the current status of #560? I know that the other two are almost done, but I did not follow the regression PR. |
joaquinvanschoren
commented
Dec 4, 2018
It was done, and we did the requested change to enums. |
janvanrijn
commented
Dec 4, 2018
Cool! Let me know when #560 is ready for review and I will go through it again. |
janvanrijn
commented
Dec 4, 2018
Another pretty important issue that should definitely be solved: #569 I will create a PR tomorrow. |
mfeurer
commented
Feb 11, 2019
ping @janvanrijn |
Codecov Report
@@ Coverage Diff @@## develop #600 +/- ##
===========================================
- Coverage 89.9% 89.87% -0.04%
===========================================
Files 32 32 Lines 3031 3031 ===========================================
- Hits 2725 2724 -1 - Misses 306 307 +1
Continue to review full report at Codecov.
|
This PR prepares a new release.