[ANN] bzr 2.4.0 has gone gold

[vila]

>>>>> Gordon Tyler <gordon at doxxx.net> writes:

<snip/>

    > I see no point in releasing an installer if I know that a
    > particular plugin requires some work to be compatible with the new
    > version of bzr.  That's on-par with Oracle's JDK7 release. :P

If you *know* the plugin is not compatible, yes of course.

Any name you want to share with us ? :)

    > I also don't want to release an "official" installer which bundles
    > some arbitrarily selected revision of a major plugin and have the
    > plugin author mad at me because I couldn't wait.

Then just take the same revision that was used for 2.4b5, what's the
issue ?

<snip/>

    > Whether they have a dedicated branch or not doesn't really matter
    > much to me, so long as there is either a relatively recent tarball
    > release or some indication that a particular revision should be
    > used. Otherwise I have to assume that the tip of trunk is
    > "stable". So far that hasn't been a problem (that I know of), but
    > I fear it will come back to bite me in the ass one day.

We did freeze the API after 2.4b5 specifically so that plugin authors
*may* create dedicated releases, if they didn't, they won't be in a
position to do anything with your ass :-p

We do time-based releases so that we don't get blocked by last-minute
landed features and because we consider there is more value in having
our software in the hands of our users early.

Keep in mind that 2.4.1 will be frozen on 2011-09-01 so there is no
point in delaying 2.4.0.

         Vincent