On Thursday, July 6, 2023 at 4:51:57 PM UTC-7 Nils Bruin wrote: On Thursday, 6 July 2023 at 14:55:35 UTC-7 Matthias Koeppe wrote:
I don't think so; I think there is an effective difference of about 6–9 months. Just O(1), of course, but so are the release cadences of OS distributions and major packages. In NEP 29 I see a 42 month window; in Proposal 2 I also see a 42 month window. Where does the 6-9 month difference come from? [...] It's just the difference between the point in time when NEP 29 *allows* us to to drop a version and the point in time when we would *drop* the version following our current practice. (See https://github.com/sagemath/sage/wiki/NEP-29:-Python-version-strategy#schedule-with-comparison-to-nep-29). The main difference between the wordings of the two proposals seems to be: "the SageMath project clarifies that it is invalid for a developer to demand that we drop support immediately at the stated time". So I think that means Proposal 2 explicitly advocates for discussion of each PR that drops support, Proposal 2 simply describes the current practice. PR author proposes and builds the case for the change, and a normal discussion take place on the PR. Proposal 1 includes a reversal of burden of proof. Right when NEP 29 allows us to drop a version, someone can (and will) prepare the (trivial) PR and demand that it be merged immediately. The wording of proposal 1 reserves deviating from this to "exceptional cases". Can you elaborate on the advantages of [Proposal 2] Sure, I've planned to be adding this to the wiki page in my next writing session, before the start of the coming week. Matthias -- 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/6d840646-c384-441d-a2c2-17f458066c70n%40googlegroups.com.
