Aaron Meurer pointed out that we should move the solving main page before the next release, so the page is in its final location when it gets published to the "latest" (not dev) version of the documentation web site. Given that, I'll make a simple pull request to reorganize the solving main page from guides/solving.md to guides/solving/index.md.
I included that reorganization in my draft pull request #23638 Documentation guide: Solve an equation algebraically <https://github.com/sympy/sympy/pull/23638> but the new sub-page is still very much in development, so I'll split out the reorganization into its own pull request. Jeremy Monat P.S. Creating this release will also have the benefit of making the "latest" version of the docs use the new Sphinx theme. That will address the "bug" in the docs that was raised in this mailing list recently, about clicking a link in the left navigation bar not doing anything. On Sat, Jun 18, 2022 at 8:25 AM Oscar Gustafsson <oscar.gustafs...@gmail.com> wrote: > I've marked a few PRs as candidates to be merged, one requires resolving > merge conflicts, but as far as I can tell there are no major arguments > against merging them. Feel free to remove the milestone and point out what > still may be missing. > > BR Oscar > > Den lör 18 juni 2022 kl 13:32 skrev Oscar Benjamin < > oscar.j.benja...@gmail.com>: > >> Hi all, >> >> I'm thinking about making a release of SymPy 1.11. Until now I've been >> too busy at work to make a release but things are beginning to ease up >> at the end of the academic year. We're already at the point where >> we're getting new reports for bugs that were fixed months ago so a new >> release would be good: >> https://github.com/sympy/sympy/issues/23639 >> >> Does anyone know of anything that should be done before issuing a new >> release? Are there any significant pull requests etc that should be >> merged? Is there any work that is incomplete and should be fixed >> first? >> >> Of course we have GSOC projects underway so potentially it's good to >> wait until that's over but that would delay the next release by a long >> time (there's usually some unfinished work so it's not as simple as >> just releasing as soon as GSOC is over). >> >> Another possibility here would be to make a release branch, put out a >> beta release and let that sit for a while to collect bug fixes. >> Pre-releases don't seem to get that much downstream testing though >> (but maybe that's because they aren't used consistently by SymPy). >> >> A few minor fixes have been made for Python 3.11 so it would be good >> to get out a new release before 3.11 comes out. We're still in the >> 3.11 beta cycle though so there's the potential for more fixes to be >> needed by the time of 3.11 final. >> >> 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 sympy+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/sympy/CAHVvXxS0MvFbhc2J%2B7VcyLsft4hLZH2%2BuqgL8XEHhiEyYm3Lng%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/CAFjzj-KUbWEU2uj%3DdT4BrHbjtzvpMTub2YtMk0eWO2aZnY_EXQ%40mail.gmail.com > <https://groups.google.com/d/msgid/sympy/CAFjzj-KUbWEU2uj%3DdT4BrHbjtzvpMTub2YtMk0eWO2aZnY_EXQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAO00iLgG4JyB3YSQLhJX0SXsdJta1QqF33dbHat3gAh3GRrD0g%40mail.gmail.com.
