Re: [sage-devel] Release schedule survey

2018-07-26 Thread Erik Bray
On Thu, Jul 19, 2018 at 12:24 AM Volker Braun 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

Re: [sage-devel] Release schedule survey

2018-07-20 Thread Emmanuel Charpentier
Ahem... Le jeudi 19 juillet 2018 01:20:28 UTC+2, Volker Braun a écrit : [ Snip... ] The same people that wish for a rigid schedule now will complain later > that they missed the merge window by a day ;-) > Hmmm... Bayesian suggestion : make the schedule dates random variables and publish th

Re: [sage-devel] Release schedule survey

2018-07-19 Thread Erik Bray
On Thu, Jul 19, 2018 at 1:05 AM William Stein wrote: > > On Wed, Jul 18, 2018 at 3:24 PM, Volker Braun 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, > > l

Re: [sage-devel] Release schedule survey

2018-07-19 Thread Erik Bray
On Thu, Jul 19, 2018 at 10:09 AM Volker Braun wrote: > > On Thursday, July 19, 2018 at 8:50:12 AM UTC+2, Jeroen Demeyer wrote: >> >> C) Don't keep a strict time table, but announce at some point during the >> beta releases when you plan to cut off the merge window. > > > Thats a bit of a cop out,

Re: [sage-devel] Release schedule survey

2018-07-19 Thread Erik Bray
On Thu, Jul 19, 2018 at 8:50 AM Jeroen Demeyer wrote: > > On 2018-07-19 00:24, Volker Braun 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 peo

Re: [sage-devel] Release schedule survey

2018-07-19 Thread Volker Braun
On Thursday, July 19, 2018 at 8:50:12 AM UTC+2, Jeroen Demeyer wrote: > > C) Don't keep a strict time table, but announce at some point during the > beta releases when you plan to cut off the merge window. > Thats a bit of a cop out, what do you mean by "at some point"? This time I wrote in the

Re: [sage-devel] Release schedule survey

2018-07-19 Thread Daniel Krenn
On 2018-07-19 08:50, Jeroen Demeyer wrote: > On 2018-07-19 00:24, Volker Braun 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 havin

Re: [sage-devel] Release schedule survey

2018-07-18 Thread Jeroen Demeyer
On 2018-07-19 00:24, Volker Braun 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) Ke

Re: [sage-devel] Release schedule survey

2018-07-18 Thread Volker Braun
No, I'm fine with either way. Personally, I think more flexibility is going to be an advantage most of the time. Though I also see how strict rules appeal to mathematicians. The same people that wish for a rigid schedule now will complain later that they missed the merge window by a day ;-) Both

Re: [sage-devel] Release schedule survey

2018-07-18 Thread William Stein
On Wed, Jul 18, 2018 at 3:24 PM, Volker Braun 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

[sage-devel] Release schedule survey

2018-07-18 Thread Volker Braun
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