Sage 9.8.rc1 released

103 views
Skip to first unread message

Volker Braun

unread,
Feb 5, 2023, 9:14:57 AM2/5/23
to sage-release
Note: the old trac git server is already disabled and the new https://github.com/sagemath/sage is still locked for migration, so you will only be able to get the branch from there starting tomorrow (Monday). If you are dying to see the new version you can temporarily get it from my own fork at github.com:vbraun/sage, but I'd recommend waiting until tomorrow.

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html


200557e00c3 (origin/develop, tag: 9.8.rc1) Updated SageMath version to 9.8.rc1
2d3c71b03b2 Trac #34942: GH Actions: Remove pull_request triggers for portability workflows
1df8f128303 Trac #34935: Followup to #34547: fix emacs sage-shell-mode
77173ef550c Trac #34873: Deprecate sage.homology.graded_resolution.GradedFreeResolution
9116c5584f9 (tag: 9.8.rc0, trac/develop) Updated SageMath version to 9.8.rc0

Matthias Köppe

unread,
Feb 5, 2023, 11:58:59 AM2/5/23
to sage-release
Thanks for the new rc. It's currently not tagged on vbraun/sage though; could you push the tag please?

Volker Braun

unread,
Feb 5, 2023, 12:21:45 PM2/5/23
to sage-release
tag is pushed!

Thierry Dumont

unread,
Feb 6, 2023, 2:37:15 AM2/6/23
to sage-r...@googlegroups.com
On Debian testing (debian 12), migration from rcà to rc1 without any
problem.
> --
> You received this message because you are subscribed to the Google
> Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-release...@googlegroups.com
> <mailto:sage-release...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/98556973-2a19-4fe2-8bbe-6e6804612671n%40googlegroups.com <https://groups.google.com/d/msgid/sage-release/98556973-2a19-4fe2-8bbe-6e6804612671n%40googlegroups.com?utm_medium=email&utm_source=footer>.

Matthias Köppe

unread,
Feb 6, 2023, 2:42:53 AM2/6/23
to sage-release
I've fast-forwarded develop to 9.8.rc1 on https://github.com/sagemath/sage

Yannick Delbecque

unread,
Feb 6, 2023, 8:58:02 AM2/6/23
to Matthias Köppe, sage-release

fchap...@gmail.com

unread,
Feb 6, 2023, 10:10:34 AM2/6/23
to sage-release
why is the "develop" branch now two commits after the 9.8.rc1 release?

Frédéric

John Cremona

unread,
Feb 6, 2023, 10:19:55 AM2/6/23
to sage-r...@googlegroups.com
On Mon, 6 Feb 2023 at 15:10, fchap...@gmail.com <fchap...@gmail.com> wrote:
why is the "develop" branch now two commits after the 9.8.rc1 release?

Surely this is bound to happen.  Every time a PR is merged, the develop branch's head advances, but there will  not be a release (or candidate) every time).

I assume this sort of thing will be covered in the talk 1 hour +10 minutes from now.
 
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/40db8677-ab03-432e-bdd2-8ccb689e419bn%40googlegroups.com.

Dima Pasechnik

unread,
Feb 6, 2023, 1:52:55 PM2/6/23
to sage-release


On Mon, 6 Feb 2023, 15:10 fchap...@gmail.com, <fchap...@gmail.com> wrote:
why is the "develop" branch now two commits after the 9.8.rc1 release?

because they rectify misleading templates for PRs and issues, as you can see.

--
Message has been deleted

Emmanuel Charpentier

unread,
Feb 6, 2023, 4:08:18 PM2/6/23
to sage-release
On Debian testing running on core i7 + 16 GB RAM, rebuilding `9.8.rc1' in a fresh tree and running `ptestlong' results in four permanent failures :

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 Doctest                                                Result            
──────────────────────────────────────────────────────────────────────────
 src/sage/schemes/elliptic_curves/ell_curve_isogeny.py  2 doctests failed
 src/sage/interfaces/fricas.py                          3 doctests failed
 src/sage/graphs/generators/families.py                 2 doctests failed
 src/sage/graphs/graph_generators.py                    1 doctest failed  
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

All these failures were already reported for previous betas.

HTH,

Le dimanche 5 février 2023 à 15:14:57 UTC+1, Volker Braun a écrit :

Kenji Iohara

unread,
Feb 6, 2023, 7:24:08 PM2/6/23
to sage-r...@googlegroups.com
On MacBook Pro with Intel Core i5, homebrew updated etc., it compiles from the first built and all tests passed ! 
Kenji

05/02/2023 18:21、Volker Braun <vbrau...@gmail.com>のメール:

-- 
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.

Yannick Delbecque

unread,
Feb 11, 2023, 11:18:09 AM2/11/23
to sage-r...@googlegroups.com, Adèle Clapperton-Richard, Abonnements revue À bâbord!
Le 6 février 2023 02 h 42 min 52 s HNE, "Matthias Köppe" <matthia...@gmail.com> a écrit :
Reply all
Reply to author
Forward
0 new messages