SciPy 1.1.0 release schedule
Hi all, It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://github.com/scipy/scipy/milestone/34), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule: April 11: branch 1.0.x April 13: rc1 April 27: rc2 (if needed) May 4: final release It would be useful if everyone could add PRs/issues that they think are critical to the 1.1 milestone. Adding yourself as an "assignee" on PRs/issues you plan to tackle would also be helpful. Thoughts? Cheers, Ralf
There are several PRs that I started reviewing, but just don't have time at the moment to finish the process. Such as the simulated dual annealing, ratio of uniforms...
On Sun, Mar 25, 2018 at 5:49 PM, Andrew Nelson <andyfaff@gmail.com> wrote:
There are several PRs that I started reviewing, but just don't have time at the moment to finish the process. Such as the simulated dual annealing
https://github.com/scipy/scipy/pull/8203 is close to ready I'd say, Antonio already finished reviewing and Jacob did a quick review as well. Would be good to get that PR in. Maybe submit any comments you already had?
, ratio of uniforms...
https://github.com/scipy/scipy/pull/8293 seems to have a bit more review work left, but code looks close to finished. Would be nice to get it in, but less critical I'd say - let's just see how far we get on that one. Ralf
Hi, su, 2018-03-25 kello 17:45 -0700, Ralf Gommers kirjoitti:
It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://github.com/scipy/scipy/milestone/34), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule:
April 11: branch 1.1.x April 13: rc1 April 27: rc2 (if needed) May 4: final release
Just a friendly heads up/reminder: staying roughly with the schedule proposed earlier, I'll branch 1.1.x on this Thursday, and work towards getting 1.1.0rc1 out during the weekend. If there are features almost ready to be merged, there's a few days before the branch point. After that, it's mainly bugfixes that'll get to 1.1.0. There are several feature PRs marked in the milestone and elsewhere that in principle might use help with reviewing/status triaging --- I've been working toward getting low-hanging ones in, but there are several which I'm not sure about. Nothing seems blocking, though. If there are blocking problems that need to be addressed currently in master before 1.1.0, please remind about them (I'm not aware of such issues though). Best, Pauli
Hi, su, 2018-03-25 kello 17:45 -0700, Ralf Gommers kirjoitti:
It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://github.com/scipy/scipy/milestone/34), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule:
April 11: branch 1.1.x April 13: rc1 April 27: rc2 (if needed) May 4: final release
Just a friendly heads up/reminder: staying roughly with the schedule proposed earlier, I'll branch 1.1.x on this Thursday, and work towards getting 1.1.0rc1 out during the weekend. If there are features almost ready to be merged, there's a few days before the branch point. After that, it's mainly bugfixes that'll get to 1.1.0. There are several feature PRs marked in the milestone and elsewhere that in principle might use help with reviewing/status triaging --- I've been working toward getting low-hanging ones in, but there are several which I'm not sure about. Nothing seems blocking, though. If there are blocking problems that need to be addressed currently in master before 1.1.0, please remind about them (I'm not aware of such issues though). Best, Pauli
On 10 April 2018 at 20:04, Pauli Virtanen <pav@iki.fi> wrote:
Hi,
su, 2018-03-25 kello 17:45 -0700, Ralf Gommers kirjoitti:
It's 5 months after the 1.0 release, so it's time to start planning for 1.1. There's still quite a few open issues and PRs marked for 1.1.0 (see https://github.com/scipy/scipy/milestone/34), but not many that seem blocking or really difficult to resolve. So I'd like to propose the following schedule:
April 11: branch 1.1.x April 13: rc1 April 27: rc2 (if needed) May 4: final release
Just a friendly heads up/reminder: staying roughly with the schedule proposed earlier, I'll branch 1.1.x on this Thursday, and work towards getting 1.1.0rc1 out during the weekend.
If there are features almost ready to be merged, there's a few days before the branch point. After that, it's mainly bugfixes that'll get to 1.1.0.
There are several feature PRs marked in the milestone and elsewhere that in principle might use help with reviewing/status triaging --- I've been working toward getting low-hanging ones in, but there are several which I'm not sure about. Nothing seems blocking, though.
If there are blocking problems that need to be addressed currently in master before 1.1.0, please remind about them (I'm not aware of such issues though).
Best, Pauli
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
Please can you consider merging PR #7374. It's already in the 1.1 milestone and I'd say it's pretty mature. The code offers 3 different ways of calculating stable pdf/cdfs all of which match samples provided by Nolan's public domain executable. It also offers parameter estimation using quantiles. Any further optimisations can be added in a later release.
participants (4)
-
Andrew Nelson
-
Blair Azzopardi
-
Pauli Virtanen
-
Ralf Gommers