Le mercredi 28 février 2024 à 17:39:25 UTC+1, Eric Gourgoulhon a écrit :
-1 from my side, for I think an issue can be a blocker. For instance: https://github.com/sagemath/sage/issues/36914 This issue, which regards the use of the notebook, could not have been detected by the CI framework. It is a serious regression and definitely a blocker IMHO: are we willing to release a version of SageMath that cannot be used without an internet connection? Seconded. -1 from me. A PR fixing a blocker issue sould be an "unblocker". (Some low minds may think of this as what Molière would have calld "un clystère"...). OK, I'll show myself out. Sorry... Eric. Le mercredi 28 février 2024 à 07:45:03 UTC+1, Kwankyu Lee a écrit : Hi, Here I withdraw the early premature "giving up" on my recent proposal, since afterwards there were some positive comments. Hence I open a voting for Proposal: 1. Do not use "blocker" label for Issues, as "blocker" means to delay the release. 2. Instead use "critical" label for a very serious and urgent Issue. 3. A PR fixing the "critical" Issue will likely get the "blocker" label. 4. Old Issues converted from trac with "critical" label will get the "major" label instead. Voting will end when there is no new vote for a week. This is a simple majority voting (following the standard on sage-devel proposal)! A positive vote is for all parts of the Proposal. So if you do not like any of (1) -- (4), cast a negative vote (-1). Happy voting! -- 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/868f9264-0d8f-4666-9786-6a535a040bffn%40googlegroups.com.
