In many software packages the automatic update is triggered only after
the release has been out for a day or more. This would avoid issues like
this (where the automatic update fails because a particular build is not
Annoucing the new release on the website and mailing list will attract a
broader base of early adopters that the very latest nightly builds.
Delaying the automatic update a couple days or longer (after the
announcement first goes out) also gives an opportunity for these early
adopters to discover any potential show-stopper bugs before it goes out
to the broader public.
On 4/30/2013 9:57 AM, Emil Ivov wrote:
We are currently releasing 2.2 indeed. Actually the screenshot you
pasted contains the new build (it's just not at the top) but lacks the
64 bit version.