On Fri, Sep 26, 2025 at 1:19 AM Antonio Rojas <[email protected]> wrote: > > El viernes, 26 de septiembre de 2025 a las 1:41:56 UTC+2, [email protected] > escribió: > > Thanks. This is the kind of break that is to be expected in an alpha, but > normally something like this in a beta is a pretty big deal. It would instill > confidence if this were followed up very quickly with a release aimed > (purely) at fixing the rather bad regression. > > > Note that the word "beta" has a very unusual (and misleading) meaning in Sage > development: a beta is just a development snapshot. This is wrong IMO and > should be changed (sage is the only software project that uses "beta" in this > way, that I know of), but it's nothing new: it's been like that since I can > remember.
That's a great point. Indeed, a much more standard development cycle is where a development window is quite long, then comes a freeze (no really new code, just fixes) with betas, then come RCs, and then a release. Our "betas" are an artifact of the release process, not anything meaningful in terms of feature completeness. It's a chunk that (hopefully) builds, no more than that. > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/sage-release/1579357f-5dd7-45e9-8c87-73802840a90an%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-release/CAAWYfq3de%2BctEa5N1y7%2B8%2BJSZTSWXTZGD69Pi1ZMGe4LzfV65g%40mail.gmail.com.
