Two major releases per year instead of three

[Adrian Buehlmann]

On 2011-07-27 14:34, Antoine Pitrou wrote:
> Adrian Buehlmann <adrian <at> cadifra.com> writes:
>>
>> The Python project is much bigger than Mercurial (more users and
>> developers) and I'd bet it has a lot more financial support.
>>
>> IMHO, a famous mature programming language and runtime environment is a
>> bit different than a SCM.
> 
> My point was that other projects do make releases in summer. Not that Mercurial
> should align its development cycle on Python or Linux!

Which I didn't say either :-)

We're not really making progress here.

>> As such I'd
>> consider you perfectly well capable of running every single revision of
>> the mercurial default branch in your personal use. Of course probably
>> not on the server side, but on the client side for sure.
> 
> Sure, but does that mean I want to? I certainly prefer to run stable versions,
> since Mercurial is a tool for me, not something I want to spend too much time
> debugging and testing.
> 
>> As you can see there was a significant drop in August 2009 and July 2010.
> 
> I'm not disputing that some people leave on holiday for some time (typically 2
> weeks); just saying that it doesn't seem to justify avoiding releases in that
> timeframe.

So if we would switch to two major releases per year (instead of three),
what would be your preferred release dates?

Currently, we have March 1st, July 1st and Nov 1st.

I proposed two releases per year. When should they be?