Hi all,
I've create the sympy 1.6 release branch and opened PRs to update
versions in both the 1.6 and master branches. For 1.5 we had a beta
release but I think there was precisely zero feedback from it so I'm
skipping that this time and going straight to release candidate
1.6rc1. I will make the release candidate available on PyPI so it can
be installed by pip.
Can I ask all contributors not to merge any PRs right now until the
version is updated on the master branch.
The release notes for 1.6 are here:
https://github.com/sympy/sympy/wiki/Release-Notes-for-1.6
Can anyone who authored/merged any work between 1.5 and 1.6 take a
look through those release notes and update/improve them if necessary?
I think anyone with push access can edit directly. If you are unable
to edit the release notes let me know and I can do it for you.
In particular:
1. Please consider whether the release note itself makes sense to end
users. Will they be able to read that and understand what is fixed or
how to find out about using a new feature?
2. Some changes e.g. refactoring work are not normally given a release
note for each PR but I still think it makes sense to give a release
note at the end that explains if a significant rearrangement of the
code has taken place. Maybe some release notes should be added
manually if you know of a lot of refactoring that has taken place.
Please let me know e.g. by replying here if that's the case (don't
assume that I will remember even if I was involved in merging...)
3. We need to manually fill in the "Backwards compatibility and
deprecations" section. If your work involved any non-backwards
compatible changes or deprecated anything can you make sure it is
listed in that section in a way that should make sense to end users.
--
Oscar