Hi all, We're now at 5 months after the 0.19.0 release, and well behind our planned 1.0 release date [1]. So it's high time for a more concrete plan - here it is: Sep 16: Branch 1.0.x Sep 17: beta1 Sep 27: rc1 Oct 7: rc2 Oct 17: final release This gives us one month to finish and merge everything that we really would like to see in 1.0 - should be enough time for things that are already in progress. The list of things now marked for 1.0 [2] is not too long, and not all of it is critical. It would be useful if everyone could add PRs/issues that they think are critical to the 1.0 milestone. Adding yourself as an "assignee" on PRs/issues you plan to tackle would also be helpful. Besides some really nice new features, we made major strides in infrastructure (CI, testing) and project organisation for this release. Fom my perspective there are three critical things left: 1. Windows wheels. Looks like we're pretty much there, but we need to ensure that 1.0 is the first release that has Windows wheels available. 2. Adding a code of conduct. This is the last thing we imho need from an "open source project maturity" perspective (an FSA would be nice, but can wait). 3. Merging a lot of PRs. There's ~150 PRs open now, I hope in the next month we can focus on reducing that number and getting some nice improvements in that have been waiting for quite some time. Finally, we've discussed before writing a paper about SciPy to coincide with this release. I'll follow up on that separately. Thoughts? Cheers, Ralf [1] https://mail.python.org/pipermail/scipy-dev/2016-September/021485.html [2] https://github.com/scipy/scipy/milestones/1.0
su, 2017-08-20 kello 18:23 +1200, Ralf Gommers kirjoitti:
Sep 16: Branch 1.0.x Sep 17: beta1 Sep 27: rc1 Oct 7: rc2 Oct 17: final release
Release schedule looks fine to me. [clip]
3. Merging a lot of PRs. There's ~150 PRs open now, I hope in the next month we can focus on reducing that number and getting some nice improvements in that have been waiting for quite some time.
I think the actionable number of PRs is about half of those. [1] The rest are stalled waiting action from the submitter side, which in some cases is probably not going to happen unless someone else picks up the ball. Pauli [1] https://pav.iki.fi/scipy-needs-work/
Hi all, If possible, I would like to see PR7629 ( https://github.com/scipy/scipy/pull/7629) in 1.0 Alessandro 2017-08-20 8:23 GMT+02:00 Ralf Gommers <ralf.gommers@gmail.com>:
Hi all,
We're now at 5 months after the 0.19.0 release, and well behind our planned 1.0 release date [1]. So it's high time for a more concrete plan - here it is:
Sep 16: Branch 1.0.x Sep 17: beta1 Sep 27: rc1 Oct 7: rc2 Oct 17: final release
This gives us one month to finish and merge everything that we really would like to see in 1.0 - should be enough time for things that are already in progress. The list of things now marked for 1.0 [2] is not too long, and not all of it is critical. It would be useful if everyone could add PRs/issues that they think are critical to the 1.0 milestone. Adding yourself as an "assignee" on PRs/issues you plan to tackle would also be helpful.
Besides some really nice new features, we made major strides in infrastructure (CI, testing) and project organisation for this release. Fom my perspective there are three critical things left:
1. Windows wheels. Looks like we're pretty much there, but we need to ensure that 1.0 is the first release that has Windows wheels available. 2. Adding a code of conduct. This is the last thing we imho need from an "open source project maturity" perspective (an FSA would be nice, but can wait). 3. Merging a lot of PRs. There's ~150 PRs open now, I hope in the next month we can focus on reducing that number and getting some nice improvements in that have been waiting for quite some time.
Finally, we've discussed before writing a paper about SciPy to coincide with this release. I'll follow up on that separately.
Thoughts?
Cheers, Ralf
[1] https://mail.python.org/pipermail/scipy-dev/2016-September/021485.html [2] https://github.com/scipy/scipy/milestones/1.0
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
-- -------------------------------------------------------------------------- NOTICE: Dlgs 196/2003 this e-mail and any attachments thereto may contain confidential information and are intended for the sole use of the recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any dissemination or copying of this message is strictly prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you. --------------------------------------------------------------------------
On Mon, Aug 21, 2017 at 9:57 PM, alebarde@gmail.com <alebarde@gmail.com> wrote:
Hi all, If possible, I would like to see PR7629 (https://github.com/scipy/ scipy/pull/7629) in 1.0
Yes, that PR, gh-7630 and gh-7637 (all about pdist/cdist) have been hovering close to the top of my review list for a while. I've added all of them to the 1.0 milestone. Cheers, Ralf
On Sun, Aug 20, 2017 at 6:23 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
Hi all,
We're now at 5 months after the 0.19.0 release, and well behind our planned 1.0 release date [1]. So it's high time for a more concrete plan - here it is:
Sep 16: Branch 1.0.x Sep 17: beta1 Sep 27: rc1 Oct 7: rc2 Oct 17: final release
Hi all, here's a friendly reminder that we're branching 1.0.x in 2 days from now. There aren't any serious blockers in the issues marked for 1.0.0, so let's try to get as much merged as possible, and we'll bump the rest. My plan is to work as far as possible through https://github.com/scipy/scipy/milestone/32 for everything except the scipy.signal and scipy.sparse issues/PRs. For signal I'm hoping that Warren and Eric L. together can merge most open PRs. For sparse the linalg issues can be fixed later and backported, and the sparse matrix ones it looks like we won't get to (unless CJ you have fixes up your sleeve?). Ralf
This gives us one month to finish and merge everything that we really would like to see in 1.0 - should be enough time for things that are already in progress. The list of things now marked for 1.0 [2] is not too long, and not all of it is critical. It would be useful if everyone could add PRs/issues that they think are critical to the 1.0 milestone. Adding yourself as an "assignee" on PRs/issues you plan to tackle would also be helpful.
Besides some really nice new features, we made major strides in infrastructure (CI, testing) and project organisation for this release. Fom my perspective there are three critical things left:
1. Windows wheels. Looks like we're pretty much there, but we need to ensure that 1.0 is the first release that has Windows wheels available. 2. Adding a code of conduct. This is the last thing we imho need from an "open source project maturity" perspective (an FSA would be nice, but can wait). 3. Merging a lot of PRs. There's ~150 PRs open now, I hope in the next month we can focus on reducing that number and getting some nice improvements in that have been waiting for quite some time.
Finally, we've discussed before writing a paper about SciPy to coincide with this release. I'll follow up on that separately.
Thoughts?
Cheers, Ralf
[1] https://mail.python.org/pipermail/scipy-dev/2016-September/021485.html [2] https://github.com/scipy/scipy/milestones/1.0
My plan is to work as far as possible through https://github.com/scipy/scipy/milestone/32 for everything except the scipy.signal and scipy.sparse issues/PRs. For signal I'm hoping that Warren and Eric L. together can merge most open PRs.
One PR is Warren's, which I'll merge tomorrow. The other three open PRs are mine. One of these depends on an open linalg PR <https://github.com/scipy/scipy/pull/7810>, so it has two levels to get through. I'm happy to iterate quickly on them as necessary, but I'm not sure if it will be possible to get them in by tomorrow. Would it be okay to backport them, too? Eric
I've cleaned up / pushed back the remaining scipy.sparse items for the 1.0 milestone. There's one scipy.sparse.linalg issue open (gh-7600) but it's outside the scope of what I'm familiar with. On Thu, Sep 14, 2017 at 9:39 AM, Eric Larson <larson.eric.d@gmail.com> wrote:
My plan is to work as far as possible through
https://github.com/scipy/scipy/milestone/32 for everything except the scipy.signal and scipy.sparse issues/PRs. For signal I'm hoping that Warren and Eric L. together can merge most open PRs.
One PR is Warren's, which I'll merge tomorrow.
The other three open PRs are mine. One of these depends on an open linalg PR <https://github.com/scipy/scipy/pull/7810>, so it has two levels to get through. I'm happy to iterate quickly on them as necessary, but I'm not sure if it will be possible to get them in by tomorrow. Would it be okay to backport them, too?
Eric
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
On Fri, Sep 15, 2017 at 2:47 AM, CJ Carey <perimosocordiae@gmail.com> wrote:
I've cleaned up / pushed back the remaining scipy.sparse items for the 1.0 milestone.
There's one scipy.sparse.linalg issue open (gh-7600) but it's outside the scope of what I'm familiar with.
Thanks CJ! Ralf
On Thu, Sep 14, 2017 at 9:39 AM, Eric Larson <larson.eric.d@gmail.com> wrote:
My plan is to work as far as possible through
https://github.com/scipy/scipy/milestone/32 for everything except the scipy.signal and scipy.sparse issues/PRs. For signal I'm hoping that Warren and Eric L. together can merge most open PRs.
One PR is Warren's, which I'll merge tomorrow.
The other three open PRs are mine. One of these depends on an open linalg PR <https://github.com/scipy/scipy/pull/7810>, so it has two levels to get through. I'm happy to iterate quickly on them as necessary, but I'm not sure if it will be possible to get them in by tomorrow. Would it be okay to backport them, too?
Eric
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
On Fri, Sep 15, 2017 at 1:39 AM, Eric Larson <larson.eric.d@gmail.com> wrote:
My plan is to work as far as possible through
https://github.com/scipy/scipy/milestone/32 for everything except the scipy.signal and scipy.sparse issues/PRs. For signal I'm hoping that Warren and Eric L. together can merge most open PRs.
One PR is Warren's, which I'll merge tomorrow.
The other three open PRs are mine. One of these depends on an open linalg PR <https://github.com/scipy/scipy/pull/7810>, so it has two levels to get through. I'm happy to iterate quickly on them as necessary, but I'm not sure if it will be possible to get them in by tomorrow. Would it be okay to backport them, too?
I think all those PRs except possibly the dpss one will make it in. I'll work on the beta release before branching, so can postpone that another half day (till Sunday afternoon my time, which is Sat evening US time). We never backport enhancements after branching though, and I wouldn't like to start now. So if people want that dpss window function in 1.0.0, it'll require rapid review and iteration. Ralf
On Fri, Sep 15, 2017 at 9:42 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Fri, Sep 15, 2017 at 1:39 AM, Eric Larson <larson.eric.d@gmail.com> wrote:
My plan is to work as far as possible through
https://github.com/scipy/scipy/milestone/32 for everything except the scipy.signal and scipy.sparse issues/PRs. For signal I'm hoping that Warren and Eric L. together can merge most open PRs.
One PR is Warren's, which I'll merge tomorrow.
The other three open PRs are mine. One of these depends on an open linalg PR <https://github.com/scipy/scipy/pull/7810>, so it has two levels to get through. I'm happy to iterate quickly on them as necessary, but I'm not sure if it will be possible to get them in by tomorrow. Would it be okay to backport them, too?
I think all those PRs except possibly the dpss one will make it in. I'll work on the beta release before branching, so can postpone that another half day (till Sunday afternoon my time, which is Sat evening US time).
We never backport enhancements after branching though, and I wouldn't like to start now. So if people want that dpss window function in 1.0.0, it'll require rapid review and iteration.
Almost therre! I sent two deprecation related PRs yesterday that need to go in. They're already reviewed (thanks Eric, Stefan) but will at least give those 24 hrs after submission so everyone has a chance to have a quick look at them. Here's a list of PRs that I plan on merging within about 10 hours from now unless there are new comments/objections: - Wrappers for some LAPACK functions (by Ilhan) https://github.com/scipy/scipy/pull/7851 - Automatic FIR order for decimate (by Eric L) https://github.com/scipy/scipy/pull/7835 - Add eigvals_tridiagonal (by Eric L) https://github.com/scipy/scipy/pull/7810 - Speed up freqz computation (by Eric L) https://github.com/scipy/scipy/pull/7738 - Removing deprecated function (by me) https://github.com/scipy/scipy/pull/7870 - Deprecate misc.pilutil functions (by me) https://github.com/scipy/scipy/pull/7869 - Update 1.0 release notes (by me) https://github.com/scipy/scipy/pull/7868 Anything else is a bonus. I've also started adding PRs for new features that are ready but haven't gotten the reviewer attention they deserve to the 1.1.0 milestone ( https://github.com/scipy/scipy/milestone/34). Cheers, Ralf
Sounds good to me. Thanks for taking the reins on this. Eric On Sat, Sep 16, 2017 at 5:34 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Fri, Sep 15, 2017 at 9:42 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Fri, Sep 15, 2017 at 1:39 AM, Eric Larson <larson.eric.d@gmail.com> wrote:
My plan is to work as far as possible through
https://github.com/scipy/scipy/milestone/32 for everything except the scipy.signal and scipy.sparse issues/PRs. For signal I'm hoping that Warren and Eric L. together can merge most open PRs.
One PR is Warren's, which I'll merge tomorrow.
The other three open PRs are mine. One of these depends on an open linalg PR <https://github.com/scipy/scipy/pull/7810>, so it has two levels to get through. I'm happy to iterate quickly on them as necessary, but I'm not sure if it will be possible to get them in by tomorrow. Would it be okay to backport them, too?
I think all those PRs except possibly the dpss one will make it in. I'll work on the beta release before branching, so can postpone that another half day (till Sunday afternoon my time, which is Sat evening US time).
We never backport enhancements after branching though, and I wouldn't like to start now. So if people want that dpss window function in 1.0.0, it'll require rapid review and iteration.
Almost therre!
I sent two deprecation related PRs yesterday that need to go in. They're already reviewed (thanks Eric, Stefan) but will at least give those 24 hrs after submission so everyone has a chance to have a quick look at them.
Here's a list of PRs that I plan on merging within about 10 hours from now unless there are new comments/objections:
- Wrappers for some LAPACK functions (by Ilhan) https://github.com/scipy/ scipy/pull/7851 - Automatic FIR order for decimate (by Eric L) https://github.com/scipy/ scipy/pull/7835 - Add eigvals_tridiagonal (by Eric L) https://github.com/scipy/ scipy/pull/7810 - Speed up freqz computation (by Eric L) https://github.com/scipy/ scipy/pull/7738 - Removing deprecated function (by me) https://github.com/scipy/ scipy/pull/7870 - Deprecate misc.pilutil functions (by me) https://github.com/scipy/ scipy/pull/7869 - Update 1.0 release notes (by me) https://github.com/scipy/ scipy/pull/7868
Anything else is a bonus.
I've also started adding PRs for new features that are ready but haven't gotten the reviewer attention they deserve to the 1.1.0 milestone ( https://github.com/scipy/scipy/milestone/34).
Cheers, Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev
participants (5)
-
alebarde＠gmail.com -
CJ Carey -
Eric Larson -
Pauli Virtanen -
Ralf Gommers