Re: [sage-release] Sage 10.0 released

[Matthias Köppe]

 

Now available:

- https://pypi.org/project/sagemath-tdlib/10.0/

- https://pypi.org/project/sagemath-meataxe/10.0/

- https://pypi.org/project/sagemath-coxeter3/10.0/

- https://pypi.org/project/sagemath-bliss/10.0/

- https://pypi.org/project/sagemath-mcqd/10.0/

- https://pypi.org/project/sagemath-sirocco/10.0/
Built using https://github.com/sagemath/sage/pull/35661, which needs review


On Sunday, May 21, 2023 at 3:48:34 PM UTC-7 François Bissey wrote:

> sage-on-gentoo 10.0 is out sans bliss and meataxe options for now.
>
> On Monday, May 22, 2023 at 8:47:33 AM UTC+12 François Bissey wrote:
>
>>
>>
>> On 22/05/23 06:14, Matthias Köppe wrote: 
>> > On Sunday, May 21, 2023 at 3:55:18 AM UTC-7 François Bissey wrote: 
>> > 
>> > I am preparing the sage-on-gentoo release. I just noticed the file 
>> > sage/graphs/bliss.pyx 
>> > is missing from the pypi tarball of sagemath-standard. 
>> > 
>> > 
>> > I have a feeling I will find it in the sage-bliss package. However I 
>> > did 
>> > not notice that the splitting of sage-bliss was live in the 10.0rc*. Is 
>> > this a mistake? 
>> > 
>> > 
>> > Sorry about this. Two possible courses of action: 
>> > 1) Prepare a sagemath-standard-10.0.post1 distribution that ships 
>> > bliss.pyx (other probably missing files such as mcqd.pyx) 
>> > 2) Prepare the sagemath-bliss-10.0 etc. packages 
>> > (https://github.com/sagemath/sage/issues/34346) 
>> > 
>> > I will work on 2) unless there are good reasons for 1) 
>> > 
>>
>> Ok on work on (2), it is just annoying for it to happen post release 
>> rather being able to prepare for it prior to it. And you are right it 
>> probably affects all the optional stuff, bliss is the one I caught 
>> because I include patch for the newer bliss. And patch complained that 
>> the file to patch doesn't exist. 
>>
>> François 
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/20f91b69-d745-4ed7-8330-790865523bdan%40googlegroups.com.

Re: [sage-release] Sage 10.0 released

[François Bissey]

sage-on-gentoo 10.0 is out sans bliss and meataxe options for now.

On Monday, May 22, 2023 at 8:47:33 AM UTC+12 François Bissey wrote:

>
>
> On 22/05/23 06:14, Matthias Köppe wrote:
> > On Sunday, May 21, 2023 at 3:55:18 AM UTC-7 François Bissey wrote:
> > 
> > I am preparing the sage-on-gentoo release. I just noticed the file
> > sage/graphs/bliss.pyx
> > is missing from the pypi tarball of sagemath-standard.
> > 
> > 
> > I have a feeling I will find it in the sage-bliss package. However I
> > did
> > not notice that the splitting of sage-bliss was live in the 10.0rc*. Is
> > this a mistake?
> > 
> > 
> > Sorry about this. Two possible courses of action:
> > 1) Prepare a sagemath-standard-10.0.post1 distribution that ships 
> > bliss.pyx (other probably missing files such as mcqd.pyx)
> > 2) Prepare the sagemath-bliss-10.0 etc. packages 
> > (https://github.com/sagemath/sage/issues/34346)
> > 
> > I will work on 2) unless there are good reasons for 1)
> > 
>
> Ok on work on (2), it is just annoying for it to happen post release 
> rather being able to prepare for it prior to it. And you are right it 
> probably affects all the optional stuff, bliss is the one I caught 
> because I include patch for the newer bliss. And patch complained that 
> the file to patch doesn't exist.
>
> François
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/23fcb70f-a4f9-4301-ad8f-0e37249b3300n%40googlegroups.com.

Re: [sage-release] Sage 10.0 released

[François Bissey]

On 22/05/23 06:14, Matthias Köppe wrote:

On Sunday, May 21, 2023 at 3:55:18 AM UTC-7 François Bissey wrote:

I am preparing the sage-on-gentoo release. I just noticed the file
sage/graphs/bliss.pyx
is missing from the pypi tarball of sagemath-standard.


I have a feeling I will find it in the sage-bliss package. However I
did
not notice that the splitting of sage-bliss was live in the 10.0rc*. Is
this a mistake?


Sorry about this. Two possible courses of action:
1) Prepare a sagemath-standard-10.0.post1 distribution that ships 
bliss.pyx (other probably missing files such as mcqd.pyx)
2) Prepare the sagemath-bliss-10.0 etc. packages 
(https://github.com/sagemath/sage/issues/34346)


I will work on 2) unless there are good reasons for 1)



Ok on work on (2), it is just annoying for it to happen post release 
rather being able to prepare for it prior to it. And you are right it 
probably affects all the optional stuff, bliss is the one I caught 
because I include patch for the newer bliss. And patch complained that 
the file to patch doesn't exist.


François

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/b5e2d8c4-c6e9-89de-71cc-cc92dd984abe%40gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Matthias Köppe]

On Sunday, May 21, 2023 at 1:18:09 PM UTC-7 Dima Pasechnik wrote:


On Sun, 21 May 2023, 19:37 Matthias Köppe,  wrote:

On Sunday, May 21, 2023 at 5:44:35 AM UTC-7 Samuel Lelievre wrote:

> - I will no longer create a text version 
> of the changelog in the traditional format (e.g. 
> https://www.sagemath.org/changelogs/sage-9.8.txt), 
> as it provides no added value. 

I strongly disagree with "as it provides no added value".


"git log" does a good job of searching the history.
I think each ticket/PR can be found there.


In particular, "git log --first-parent upstream/develop" shows just the 
merge commits for each PR / ticket. This includes all PR / ticket 
descriptions in full.


 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/c6c3cf8c-4569-430e-ac9f-964560187329n%40googlegroups.com.

Re: [sage-release] Re: Sage 10.0 released

[Dima Pasechnik]

On Sun, 21 May 2023, 19:37 Matthias Köppe,  wrote:

> On Sunday, May 21, 2023 at 5:44:35 AM UTC-7 Samuel Lelievre wrote:
>
> > - I will no longer create a text version
> > of the changelog in the traditional format (e.g.
> > https://www.sagemath.org/changelogs/sage-9.8.txt),
> > as it provides no added value.
>
> I strongly disagree with "as it provides no added value".
>
>
"git log" does a good job of searching the history.
I think each ticket/PR can be found there.



>
> The traditional changelogs do provide added value:
>
> - the changelogs, as text files, are very searchable
> (see above for detecting previous contributions!)
> - they give a nice overview of what went into
> each development release and final release
> - they name authors and reviewers for each ticket
>
> Many other free software projects maintain changelogs
> as text files (which might point to their added value too).
>
>
> I'm not opposed to creating such changelogs. I'm just announcing that I
> will not be working on it.
>
> In fact, https://github.com/sagemath/sage/issues/31533 proposes to "Migrate
> old Sage release tours and changelogs from Sage website and wiki to Sage
> documentation".
>
> That may be something that people who perceive an added value in text
> changelogs may be movtivated to work on.
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/e629d2ca-a338-4108-812c-168786e2089en%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAAWYfq3BWraq2_qoU8HdQYzNhNrNUu7XX8mPc2_vDfvfh6bCMw%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Matthias Köppe]

On Sunday, May 21, 2023 at 5:44:35 AM UTC-7 Samuel Lelievre wrote:

> - I will no longer create a text version 
> of the changelog in the traditional format (e.g. 
> https://www.sagemath.org/changelogs/sage-9.8.txt), 
> as it provides no added value. 

I strongly disagree with "as it provides no added value". 

The traditional changelogs do provide added value: 

- the changelogs, as text files, are very searchable 
(see above for detecting previous contributions!) 
- they give a nice overview of what went into 
each development release and final release 
- they name authors and reviewers for each ticket 

Many other free software projects maintain changelogs 
as text files (which might point to their added value too).


I'm not opposed to creating such changelogs. I'm just announcing that I 
will not be working on it.

In fact, https://github.com/sagemath/sage/issues/31533 proposes to "Migrate 
old Sage release tours and changelogs from Sage website and wiki to Sage 
documentation".

That may be something that people who perceive an added value in text 
changelogs may be movtivated to work on.


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/e629d2ca-a338-4108-812c-168786e2089en%40googlegroups.com.

Re: [sage-release] Re: Sage 10.0 released

[Matthias Köppe]

On Sunday, May 21, 2023 at 5:44:35 AM UTC-7 Samuel Lelievre wrote:

2023-05-21 01:00 UTC, Matthias Köppe: 
> 
> I have created a changelog at 
> https://github.com/sagemath/sage/releases/tag/10.0 
> (automatically generated from the merged PRs by GitHub; 
> then lightly edited). 

Thanks. 

> Some notes: 
> 
> - The list of "New Contributors" was also automatically generated 
> by GitHub. It did not know the contributors of previous versions. 
> I've manually removed many of these lines when I recognized 
> the username. There may be others that should be removed 
> from this list; let me know. 

Here is one way to detect a few. By hovering over 
the github handles in the "new contributors" list at 

- https://github.com/sagemath/sage/releases/tag/10.0 

one can get (or guess) some names: 

- @Sandstorm831: Rohan Garg 
- @MatteoCati: Matteo Cati 
- @zovelsanj: Sanjay Rijal 
- @kryzar: Antoine Leudière 
- @minaminao: minaminao 
- @jnash10: Agamdeep Singh 
- @thecaligarmo: Aram Dermenjian 
- @wermos: Tirthamkar Mazumder 
- @prirai: Priyanshu Kumar Rai 
- @mathcals: Sander 
- @remyoudompheng: Rémy Oudompheng 
- @Eloitor: Eloi Torrents 
- @MatanZ: Matan Ziv-Av 
- @karan0handa: Karan Handa 
- @yukibl: Yuki 
- @alexhutman: Alex Hutman 
- @aadya940: Aadya Chinubhai 
- @fingolfin: Max Horn 
- @marizee: Marie Bonboire 

Then, grepping the past changelogs reveals 
a few previous contributions: 

```shell 
$ git clone https://github.com/sagemath/website.git sagemath-website 

$ cd sagemath-website/src/changelogs 

$ grep -i "Matteo Cati" *.txt 
sage-9.8.txt: - Matteo Cati [first contribution] 

$ grep -i "Antoine Leudière" *.txt 
sage-9.7.txt: - Antoine Leudière [first contribution] 

$ grep -i "Aram Dermenjian" *.txt 
sage-6.9.txt: - Aram Dermenjian [first contribution] 

$ grep -i "Rémy Oudompheng" *.txt 
sage-9.7.txt: - Rémy Oudompheng [first contribution] 

$ grep -i "Max Horn" *.txt 
sage-9.4.txt: - Max Horn [first contribution] 


Thanks for working on this. I've removed these 5 from the "New 
contributors" list.
 

Besides, some users might have had a Sage Trac username 
similar to their github handle, or have used github authentication 
to contribute to Sage Trac, so it would be nice to be able 
to search Trac, if it was restored (even readonly).


We have been very careful about preserving ALL information from Trac.
A lot of thought and hard work has gone into this.

Specifically, all username mappings were migrated 
to https://www.sagemath.org/development-map.html

> - We do not have clean Author/Reviewer information 
> on all of our PRs. The changelog only shows 
> the GitHub handle of the user who created the PR. 

This is a sad loss of the new system.


Also on Trac the Author/Reviewer information was not automagically created.
The authors and reviewers had to manually put their names in the 
corresponding fields.

We just need to build this into our new workflow. 

For example, in the PR template we could include something like

"Authors (if not the same as the PR author): ..."

For instance, 
#35571 is authored by Thierry Monteil, and reviewed 
by Matthias Köppe, even though the PR was created 
by Dima Pasechnik.


Thanks, I've updated the release notes accordingly.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/772997d4-1934-4405-bb1d-ef2a88f83b46n%40googlegroups.com.

Re: [sage-release] Sage 10.0 released

[Matthias Köppe]

On Sunday, May 21, 2023 at 3:55:18 AM UTC-7 François Bissey wrote:

I am preparing the sage-on-gentoo release. I just noticed the file 
sage/graphs/bliss.pyx 
is missing from the pypi tarball of sagemath-standard.


I have a feeling I will find it in the sage-bliss package. However I did 
not notice that the splitting of sage-bliss was live in the 10.0rc*. Is 
this a mistake?


Sorry about this. Two possible courses of action:
1) Prepare a sagemath-standard-10.0.post1 distribution that ships bliss.pyx 
(other probably missing files such as mcqd.pyx)
2) Prepare the sagemath-bliss-10.0 etc. packages 
(https://github.com/sagemath/sage/issues/34346)

I will work on 2) unless there are good reasons for 1)

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/928e0566-335f-4416-89f0-8314559cdfb8n%40googlegroups.com.

Re: [sage-release] Re: Sage 10.0 released

[Dima Pasechnik]

This is now https://github.com/sagemath/sage/issues/35659

On Sun, May 21, 2023 at 2:33 PM Dima Pasechnik  wrote:
>
> probably, related to
> https://github.com/citation-file-format/citation-file-format/issues/374
>
> On Sun, May 21, 2023 at 1:58 PM Dima Pasechnik  wrote:
> >
> > something is again off with the DOI records for Sagemath, the latest
> > is still shown as 9.7.
> > Also, https://github.com/sagemath/sage/blob/develop/CITATION.cff
> > is off, and still refers to 9.5.
> >
> > (sorry, I didn't check this for 9.8)
> >
> > Dima

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAAWYfq3uF8r73zCua6yzY-uoBqv5hKbTvigWCbWayVWA%2BNzPnQ%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Dima Pasechnik]

probably, related to
https://github.com/citation-file-format/citation-file-format/issues/374

On Sun, May 21, 2023 at 1:58 PM Dima Pasechnik  wrote:
>
> something is again off with the DOI records for Sagemath, the latest
> is still shown as 9.7.
> Also, https://github.com/sagemath/sage/blob/develop/CITATION.cff
> is off, and still refers to 9.5.
>
> (sorry, I didn't check this for 9.8)
>
> Dima

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAAWYfq3CWJyOV8OiXFvLpsDMm1F4CJUN%2BDY59PRA5fLRE2w7dA%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Dima Pasechnik]

something is again off with the DOI records for Sagemath, the latest
is still shown as 9.7.
Also, https://github.com/sagemath/sage/blob/develop/CITATION.cff
is off, and still refers to 9.5.

(sorry, I didn't check this for 9.8)

Dima

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAAWYfq3kFPOOh8-dSMpyk_44RN6M4xST9FvpdGBM5YAYOu47%3DA%40mail.gmail.com.

Re: [sage-release] Re: Sage 10.0 released

[Samuel Lelièvre]

Congratulations to Volker and to all Sage contributors
on the new release.

2023-05-21 01:00 UTC, Matthias Köppe:
>
> I have created a changelog at
> https://github.com/sagemath/sage/releases/tag/10.0
> (automatically generated from the merged PRs by GitHub;
> then lightly edited).

Thanks.

> Some notes:
>
> - The list of "New Contributors" was also automatically generated
>   by GitHub. It did not know the contributors of previous versions.
>   I've manually removed many of these lines when I recognized
>   the username. There may be others that should be removed
>   from this list; let me know.

Here is one way to detect a few. By hovering over
the github handles in the "new contributors" list at

- https://github.com/sagemath/sage/releases/tag/10.0

one can get (or guess) some names:

- @Sandstorm831: Rohan Garg
- @MatteoCati: Matteo Cati
- @zovelsanj: Sanjay Rijal
- @kryzar: Antoine Leudière
- @minaminao: minaminao
- @jnash10: Agamdeep Singh
- @thecaligarmo: Aram Dermenjian
- @wermos: Tirthamkar Mazumder
- @prirai: Priyanshu Kumar Rai
- @mathcals: Sander
- @remyoudompheng: Rémy Oudompheng
- @Eloitor: Eloi Torrents
- @MatanZ: Matan Ziv-Av
- @karan0handa: Karan Handa
- @yukibl: Yuki
- @alexhutman: Alex Hutman
- @aadya940: Aadya Chinubhai
- @fingolfin: Max Horn
- @marizee: Marie Bonboire

Then, grepping the past changelogs reveals
a few previous contributions:

```shell
$ git clone https://github.com/sagemath/website.git sagemath-website

$ cd sagemath-website/src/changelogs

$ grep -i "Matteo Cati" *.txt
sage-9.8.txt:  - Matteo Cati [first contribution]

$ grep -i "Antoine Leudière" *.txt
sage-9.7.txt:  - Antoine Leudière [first contribution]

$ grep -i "Aram Dermenjian" *.txt
sage-6.9.txt:  - Aram Dermenjian [first contribution]

$ grep -i "Rémy Oudompheng" *.txt
sage-9.7.txt:  - Rémy Oudompheng [first contribution]

$ grep -i "Max Horn" *.txt
sage-9.4.txt:  - Max Horn [first contribution]
```

Besides, some users might have had a Sage Trac username
similar to their github handle, or have used github authentication
to contribute to Sage Trac, so it would be nice to be able
to search Trac, if it was restored (even readonly).

> - We do not have clean Author/Reviewer information
>   on all of our PRs. The changelog only shows
>   the GitHub handle of the user who created the PR.

This is a sad loss of the new system. For instance,
#35571 is authored by Thierry Monteil, and reviewed
by Matthias Köppe, even though the PR was created
by Dima Pasechnik.

> - I will no longer create a text version
>   of the changelog in the traditional format (e.g.
>   https://www.sagemath.org/changelogs/sage-9.8.txt),
>   as it provides no added value.

I strongly disagree with "as it provides no added value".

The traditional changelogs do provide added value:

- the changelogs, as text files, are very searchable
  (see above for detecting previous contributions!)
- they give a nice overview of what went into
  each development release and final release
- they name authors and reviewers for each ticket

Many other free software projects maintain changelogs
as text files (which might point to their added value too).

>   The script to generate the changelog
>   (https://github.com/sagemath/sage-changelogs;
>   now archived) no longer works, as it was using
>   the Trac server.

This is a sad loss.

I found Trac's searchability vastly superior to GitHub's,
despite some claims to the contrary in the "campaign"
to ditch Trac and move to GitHub a while ago.

I am still bitter about how that campaign went,
and about the result, but hey that happened.

Happy Sage development to all anyway.   --Samuel

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAEcArF3jUc%3DYR9NhHheirbDbKONytG7yfxuUY6_%2B0Kmqf-igLA%40mail.gmail.com.

Re: [sage-release] Sage 10.0 released

[François Bissey]

I am preparing the sage-on-gentoo release. I just noticed the file
sage/graphs/bliss.pyx
is missing from the pypi tarball of sagemath-standard.
I have a feeling I will find it in the sage-bliss package. However I did 
not notice that the splitting of sage-bliss was live in the 10.0rc*. Is 
this a mistake?


Cheers,
François

On 21/05/23 11:10, Volker Braun wrote:
The "master" git branch has been updated to Sage-10.0. 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


As you are undoubtedly aware, this version is the first since the 
migration of the development process to github. A big thanks to everyone 
who was involved, we couldn't have done it without you 


6ba0eafc2ca (tag: 10.0, github/develop) Updated SageMath version to 10.0
8476c469588 gh-35460: Update developer guide for workflows on github
4ed2157cd2a gh-35638: build/pkgs/python3/spkg-configure.m4: Add depcheck 
for zlib

9de8c5b1b6c gh-35637: remark that WSL needs a lot of RAM
f2f5863c08a (tag: 10.0.rc3) Updated SageMath version to 10.0.rc3

--
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+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/48dea2b5-d56c-4191-b1e8-518b03f6aac2n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/25a10aa1-4ab5-8a18-8007-a72e402d941a%40gmail.com.