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.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
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?
On Sunday, November 15, 2020 at 2:42:30 AM UTC-8 Volker Braun wrote:
> I think there are
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 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
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:
> - macOS 11 Big Sur
> - critical fixes that were not merged in 9.2
> - package upgrades that did not
