[arkitaip]

The great thing about this is that it makes shipping less dramatical. If your code misses this month's release, just wait another 30 days. Also, when you're doing these incremental releases, you don't risk shipping major releases that might be buggy or not appeal your customers.

[tonfa]

For most code (at least the interesting one), it's not 30 days, but 4 months. The monthly release is only for the stable branch.

See http://mercurial.selenic.com/wiki/TimeBasedReleasePlan

Personally i find it great (and we try to do the coding sprint one/two months before the next release, so the big features have some time to be stabilized).

[Silhouette]

In case any Mercurial people are reading this: It might be helpful to advertise that release schedule information more prominently on the home and/or download pages of your site.

I've been using Hg for a while on various machines, but I hadn't noticed anything so regular. I just set up a whole load of machines for some colleagues yesterday with the then-latest version, wondering why downloading the installers seemed so slow. I assume with hindsight that I missed the update by a few hours at most, and maybe the connection was weighed down with release-related tasks.

(Oh, and thanks to the dev team for the hard work, BTW!)

[tonfa]

Hi, I'm a Hg dev. I'll talk to the people doing the website see what they think about that.