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 On Mon, 27 Apr 2020 at 19:55, Oscar Benjamin <oscar.j.benja...@gmail.com> wrote: > > Yes, I'm aiming to release as soon as possible. There aren't many > release blockers and some are already getting fixed. > > On Mon, 27 Apr 2020 at 19:52, Aaron Meurer <asmeu...@gmail.com> wrote: > > > > I think we should try to release before GSoC starts. Otherwise we will > > have to wait until the fall to do the release. > > > > Aaron Meurer > > > > On Mon, Apr 27, 2020 at 12:30 PM Nikhil Maan <nikhilmaa...@gmail.com> wrote: > > > > > > Hi Oscar, > > > > > > Do you plan to release 1.6 before the GSoC coding period ends? > > > Or will the GSoC 2020 projects also be included in this release? > > > > > > Regards, > > > Nikhil Maan > > > > > > On Sunday, April 26, 2020 at 7:30:34 PM UTC+5:30, Oscar wrote: > > >> > > >> Hi Aaron, > > >> > > >> I've done some basic benchmarking and opened an issue to track > > >> performance changes since 1.4/1.5.1: > > >> https://github.com/sympy/sympy/issues/19199 > > >> > > >> When releasing 1.5 Jason did not manage to find time to run the full > > >> benchmark suite so I compared 1.4 as well. Hopefully we can also run > > >> the full suite (not sure I can do that myself). > > >> > > >> Oscar > > >> > > >> On Sun, 26 Apr 2020 at 09:18, Aaron Meurer <asme...@gmail.com> wrote: > > >> > > > >> > Thanks for doing this! > > >> > > > >> > It might be worth running the benchmarks to see if there any > > >> > regressions we should be aware of. I saw at least one issue in the > > >> > milestone is performance related. > > >> > > > >> > Aaron Meurer > > >> > > > >> > On Sat, Apr 25, 2020 at 2:07 PM Oscar Benjamin > > >> > <oscar.j...@gmail.com> wrote: > > >> > > > > >> > > Hi all, > > >> > > > > >> > > I think it's time to start thinking about the sympy 1.6 release. At > > >> > > this stage all that needs doing is flagging issues or pull requests > > >> > > that are potential release blockers. > > >> > > > > >> > > I've opened an issue to keep track of the release itself here: > > >> > > https://github.com/sympy/sympy/issues/19193 > > >> > > > > >> > > If you know of any issues, bugs, pull requests that should be > > >> > > resolved > > >> > > for the next release then please add the 1.6 milestone on github. > > >> > > Currently there are only a handful of issues with the milestone: > > >> > > https://github.com/sympy/sympy/milestone/53 > > >> > > > > >> > > Oscar > > >> > > > > >> > > -- > > >> > > You received this message because you are subscribed to the Google > > >> > > Groups "sympy" group. > > >> > > To unsubscribe from this group and stop receiving emails from it, > > >> > > send an email to sy...@googlegroups.com. > > >> > > To view this discussion on the web visit > > >> > > https://groups.google.com/d/msgid/sympy/CAHVvXxS8eZQx99GtoY_5RrBe%3DwGrX-_UNgtzfyKm7o6Dsrx1_Q%40mail.gmail.com. > > >> > > > >> > -- > > >> > You received this message because you are subscribed to the Google > > >> > Groups "sympy" group. > > >> > To unsubscribe from this group and stop receiving emails from it, send > > >> > an email to sy...@googlegroups.com. > > >> > To view this discussion on the web visit > > >> > https://groups.google.com/d/msgid/sympy/CAKgW%3D6KGdtc087D7wJEyUTu%3DUJNYaUHQOu%3DhA7fz3scDcQSqiA%40mail.gmail.com. > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "sympy" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to sympy+unsubscr...@googlegroups.com. > > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/sympy/43f05f45-fae9-49e4-af7e-59e0d54486f2%40googlegroups.com. > > > > -- > > You received this message because you are subscribed to the Google Groups > > "sympy" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to sympy+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/sympy/CAKgW%3D6LdcPYRToEMmvX8bQF_yKisktn-swKeSHRCWsG_0XLCaQ%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAHVvXxQwvgPtWL%2BzA%2BhwE76q8EyBokHbGRSZJXyN_wm78%2BZrxw%40mail.gmail.com.
