On Thu, Jul 19, 2018 at 12:24 AM Volker Braun <[email protected]> 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.
So, I count 1) 1 clear vote for "A". 2) 1 clear vote for "B", but with some built-in allowance for flexibility 3) My vote is somewhere between B and C 4) +2 for C I'm not sure how much weight this survey has considering the lack of participation (it is summer after all) and that the original poll options were not really exactly what I would have put on the table in the first place. FWIW I'd be happy with having at least 2 release dates planned in advance, so that when opening tickets I can assign them to a future release that is not the "next" release, but is still a real release that I would hope to get something done by. Target release dates can be at the release manager's discretion, but should be announced somewhere and open to discussion (I imagine most of the time no one will have any immediate problem with any suggested dates, but it at least gives the opportunity to point out things like "Hey, there's a Sage days coming up ____"). -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
