On Thu, Jul 19, 2018 at 1:05 AM William Stein <wst...@gmail.com> wrote: > > On Wed, Jul 18, 2018 at 3:24 PM, Volker Braun <vbraun.n...@gmail.com> wrote: > > Since Erik is clamoring for a more calendar-driven release schedule, here is > > a quick A/B test: > > > > A) Keep the current process of releasing approximately every 3 months, > > longer if people insist on having their own pet tickets merged at the last > > minute. > > > > B) Keep a strict time table: Merge window is open for 2 months, after that > > only fixes for new regressions, release on 1/1, 3/1, 6/1, and 9/1. > > Does our vote/answer have any impact on whether or not you continue to > be release manager? (Your incredible work on this difficult and time > consuming role for the Sage software is very greatly appreciated. > Perhaps only those who have been release manager for Sage know how > difficult it is...)
Perhaps I'm misreading, but your last comment seems to be suggesting that requesting planning and communication is somehow a denial of the difficulty of the task. I'm asking for those things because it would make the task easier, both for the release manager, and for everyone else who does hard (or even a small amount of work) on Sage. It's not an extra burden solely for the release manager to carry either; the question of when to make a release is something that's subject to, and often even requires solicitation of community feedback. None of us can be oracles. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
