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... On Wednesday, November 11, 2020 at 12:14:45 AM UTC+1 Matthias Koeppe wrote: > 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 make it into 9.2 >> - fixing broken optional packages >> >> Perhaps a release date at the end of the month would be possible. >> > > 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. > > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/bc968f1c-515d-4767-b756-a090abe20bc5n%40googlegroups.com.
