Sage 9.3 release cycle

[Matthias Koeppe]

I would suggest that we aim for a much shorter release cycle for Sage 9.3 with a focus on the following issues:

- macOS 11 Big Sur

- critical fixes that were not merged in 9.2

- package upgrades that did not make it into 9.2

- fixing broken optional packages

Perhaps a release date at the end of the month would be possible.

[Matthias Koeppe]

Volker, I am not sure if you are aware of this, but your ticket merging scripts seem to ignore the Milestone set in the trac tickets. I would suggest that this be changed. 

The current process seems to have an abrupt transition from "merging anything that's positively reviewed" to "only merging blocker tickets". Allowing developers to defer a ticket to the next release cycle by setting the Milestone would in my opinion improve release quality.

[Vincent Delecroix]

Dear all,

Among the "package upgrades", I want to emphasize the one
to pari 2.13 (see https://trac.sagemath.org/ticket/30801).
The debian freeze is happening soon and the pari ticket
is somehow blocking the SageMath update. Would make sense
to have Sage 9.3 released by then.

[Dima Pasechnik]

On Wed, 11 Nov 2020, 07:38 Vincent Delecroix, <20100.d...@gmail.com> wrote:

Dear all,

Among the "package upgrades", I want to emphasize the one
to pari 2.13 (see https://trac.sagemath.org/ticket/30801).

is anyone working to fix the remaining issues there?

The debian freeze is happening soon and the pari ticket
is somehow blocking the SageMath update. Would make sense
to have Sage 9.3 released by then.

Le 10/11/2020 à 23:14, Matthias Koeppe a écrit :
> I would suggest that we aim for a much shorter release cycle for Sage 9.3
> with a focus on the following issues:
> - macOS 11 Big Sur
> - critical fixes that were not merged in 9.2
> - package upgrades that did not make it into 9.2
> - fixing broken optional packages
>
> Perhaps a release date at the end of the month would be possible.
>

--
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 sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/1d19b4b0-3be5-6b9c-2847-526be70d0048%40gmail.com.

[Vincent Delecroix]

Le 11/11/2020 à 08:41, Dima Pasechnik a écrit :
> On Wed, 11 Nov 2020, 07:38 Vincent Delecroix, <20100.d...@gmail.com>
> wrote:
>
>> Dear all,
>>
>> Among the "package upgrades", I want to emphasize the one
>> to pari 2.13 (see https://trac.sagemath.org/ticket/30801).
>>
>
> is anyone working to fix the remaining issues there?

I am alone with Antonio on that ticket and won't have time
before at least a week. The main points on todo list are

1) There was a change about Hermite forms in PARI which
modifies the behavior of a lot of things in SageMath quadratic
form code.

2) Some long time doctests (libs/pari/tests.py) hang

Vincent

[Matthias Koeppe]

On Tuesday, November 10, 2020 at 2:14:29 PM UTC-8, Matthias Koeppe wrote:

I would suggest that we aim for a much shorter release cycle for Sage 9.3 with a focus on the following issues: [...]

- package upgrades [...]

https://trac.sagemath.org/ticket/30611 upgrades various Python packages. Needs testing/review. 

Help is needed with opening separate upgrade tickets for the following:

- sphinx and friends

- IPython/Jupyter

[Volker Braun]

I think there are pros and cons to looking at the Milestone field; In particular, if scripts evaluate it then it must always be set correctly or else your ticket is silently ignored forever.  There is certainly a use case for deferring tickets, but you can do that already manually by depending on another ticket. Plus thats more flexible in that its not tied to the release version. 

Is it possible to get the current milestone from the trac xmlrpc api? If not then the scripts can't...

[Matthias Koeppe]

It does not look like https://trac.sagemath.org/rpc#rpc.ticket.milestone reveals this information.

But surely your scripts must have a notion of the current release series for calling sage-update-version?

[Samuel Lelievre]

This suggests we might create a ticket for each release.

For any ticket that should only be merged after that release,

make the release ticket a dependency.