On Friday, September 26, 2025 at 7:47:25 AM UTC+9 John H Palmieri wrote:

Here are some recent occurrences in Sage development:

1. The documentation is not built by default.


Previously "make" built doc. Now it doesn't. This change affects all 
developers using sage-the-distro. 
As such, It should have been announced in sage-devel. I don't know if it 
was. 

2. There has been the assertion that Conda is the recommended approach for 
compiling from source.


This is a major change. This should be approved in sage-devel before it is 
officially adopted (appear in docs).
 

3. Kwankyu has brought up some issues about github release creation.


We are keeping changelogs 
here: https://www.sagemath.org/changelogs/index.html. They are 
automatically generated by a few github workflows.

To keep the format (contributions divided by releases) of the changelogs, I 
made the PR https://github.com/sagemath/sage/pull/39194.

Recently https://github.com/sagemath/sage/pull/40709 removed the code from 
#39194 without any discussion.

The author and the reviewer of #40709 made no efforts to fix the 
regression, as seen in https://github.com/sagemath/sage/pull/40840 
and https://github.com/sagemath/sage/pull/40843. 
 

4. Historically (at least in my experience) Sage developers were careful to 
maintain backwards compatibility, whereas there are at least some now who 
are willing to break things and then maybe fix them later. Item 3 arose, 
and some other issues arose, because code was removed without carefully 
thinking about the consequences.


I agree. Item 3 is one but trivial example. There could be other 
non-trivial items related with the work of conda/meson-based sage. 

The sage community did not approve transition from the 
sage-the-distro-based sage to conda/meson-based sage, as we did for python3 
transition and github migration.
Hence conda/meson-based sage should be developed while not breaking 
sage-the-distro-based sage. 

However, the main developer of conda/meson-based sage proposes PRs without 
testing with sage-the-distro-based sage. An example: 
https://github.com/sagemath/sage/pull/40841. 

Even though he is not "willing to break things and then maybe fix them 
later", such a PR, if merged without a careful review, is likely to break 
sage-the-distro-based sage.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/sage-devel/55ec5a3f-9f53-4716-bdc7-fcc83819611bn%40googlegroups.com.

Reply via email to