On Friday, 24 January 2025 at 11:28:42 UTC-8 axio...@yahoo.de wrote: To do this, it is very helpful that unfinished tickets are *not* closed, because this gives me the "interesting" tickets with a single click: I hide all the closed ones. Usually only a few remain, and the older among those tell me the story I want to listen to.
One major annoyance for this scheme was that, some time in the past, tickets were automatically modified with a message similar to "As the Sage-8.8 release milestone is pending,...next release milestone (sage-8.9)." That's a relevant data point: indeed, "stale" PRs are not "closed" PRs (which would include integrated PRs and truly discarded ones). The "stale" PRs need to be differentiated from them so that they can show up in searches. So perhaps "closing" them isn't the right thing to do. However, if changing a tag on them changes a modification date and therefore changes where they show up in searches, wouldn't that give a handle to distinguish them? Just search on PRs that have a recent modification date? Then tickets would automatically become "stale" just by being not modified. So if some people are advocating a tag (because otherwise there is no way to distinguish stale tickets) and other people are advocating *not* a tag, because that would ruin a way to distinguish stale tickets, perhaps these people should compare notes and investigate convenient search criteria. -- 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 visit https://groups.google.com/d/msgid/sage-devel/c204d284-0e07-4d69-8247-501e02fd5d16n%40googlegroups.com.
