Hi all,
I’m proposing the release schedule for SciPy 1.17.0 below and I’m happy to hear feedback/requests for adjustments if needed.
- 2025-12-06T07:00:00Z branch
maintenance/1.17.x
- 2025-12-09T07:00:00Z release SciPy
1.17.0rc1
- 2025-12-20T07:00:00Z release SciPy
1.17.0rc2 (if needed)
- 2026-01-03T07:00:00Z final SciPy
1.17.0 release
Current tallies for 1.17.0 milestone:
If there are any major items you think should be tracked before branching, feel free to share those here as well. Otherwise, the usual milestone tagging on GitHub should suit as usual.
7 Likes
what’s the latest @tylerjereddy 
@lucascolley The current plan is to release SciPy 1.17.0 “final” on January 11/2026 (Sunday). I discussed this a bit with the NumPy team in their meeting today–it would be nice if we could avoid building our “final” wheels against NumPy 2.4.0 because of the symbol issue, but it isn’t really a blocker (obviously, using 2.4.0 at runtime when building against any other version is the issue we know about). The other reason to wait until the weekend is just to give a bit of time for feedback on the delayed RC2.
It sounds like Chuck may try to release NumPy 2.4.1 by Saturday, but it depends on how things go for them. NumPy folks seemed a bit divided on yanking the 2.4.0 release from PyPI after 2.4.1 goes up, but they may do that given that Ralf and I were mostly in favor of a yank I think. In any case, I’ll probably open a WIP backport/preparation PR “soon” and probably ping on what we want to do in the few scenarios that might happen (i.e., if NumPy doesn’t yank 2.4.0, do we want some kind of block on that version, or too ugly to have a single-version runtime block, etc.)
2 Likes