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
DOC: SciPy 1.11.0 release notes #18563
Conversation
* add draft author list, and fix broken `.mailmap` file (Zoufiné Lauer-Bare had an invalid entry) * add draft issue/PR lists * transcribe/reformat wiki release notes to the rst format * manually scan the 118 merged `enhancement` PRs, and update any missing entries in the release notes * fixes from checking doc build locally: `python dev.py doc html -j 12` [skip actions] [skip cirrus]
@perimosocordiae said he'd try to help me document the recent |
|
||
|
||
|
||
******* | ||
Authors | ||
******* | ||
|
||
* h-vetinari (69) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other single-name users seem to be sorted alphabetically, not sure what's going on there; I'm also really surprised by my supposed commit count, it should be around half that:
git shortlog -sn --no-merges tags/v1.10.0..6d9754182e5f65540957ade962cd3689eacd3599 | grep -i "vetinari"
34 @h-vetinari
(with merges it's 36)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe that's something you can discuss with @tupui re: the machinery that calculates this in tools/authors.py
. I'm not sure the commit counts are that useful anyway, but I probably won't have the bandwidth to debug at this time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's also looking at the message to find if the name is thanked or in co-authored. So the number here should be greater or equal than the actual numbers of commit you got yourself in the history.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deprecated features | ||
******************* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stefanv could you suggest an entry for your recent sparse deprecation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! It's holiday in the US Monday, so if this can happen on Tuesday that'd be great.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CJ drafted some deprecations in, and I added a few more locally based on the sprint notes/PRs, that I'll push shortly. I'll welcome refinements even after I branch, so a PR can be opened later.
I still plan to branch on May 29th at some reasonable hour of US Mountain Time. I'll try to make a few more rounds of improvements here, check the |
DOC: stats: improve 1.11.0 stats release notes
I merged Matt's PR to my branch in. Feel free to ping me directly if you make such a PR so I see it right away on my phone tomorrow. |
For reference, here are the final notes on scipy.sparse changes from the Summit last week: https://hackmd.io/@y1KjxOX0RyaAGSI6B4cY0g/B1Y47nAHh |
* apply reviewer suggestions in cases where it was possible to do directly via the GH interface [skip actions] [skip cirrus] Co-authored-by: Ilhan Polat <ilhanpolat@gmail.com> Co-authored-by: CJ Carey <perimosocordiae@gmail.com> Co-authored-by: Matt Haberland <mhaberla@calpoly.edu>
* address suggestions from code review [skip actions] [skip cirrus]
* formatting cleanup for `sparse` section, and move deprecation information to the appropriate section + expand it * draft the release highlights * some line length cleanups and removal of empty sections * re-run author and issue/PR list scripts [skip actions] [skip cirrus]
I wrote a first draft of the release highlights and made a bunch of other cleanups to the release notes. The rendered version of the notes looks nice locally. Of course, there is always room for improvement, but if the CI passes here I'm likely to merge and move forward with the branching timeline, with release notes refinements accepted before RC1 on Wednesday and where needed during the RC phase. |
Presumably there will be a PR for updates at some point, into which we can merge https://github.com/mdhaber/scipy/tree/gh18563. |
.mailmap
file (Zoufiné Lauer-Bare had an invalid entry)enhancement
PRs, and update any missing entries in the release notespython dev.py doc html -j 12
TODO:
sparse
arrays, and something for the enormous volume ofstats
work done.mailmap
updates