[ANNOUNCE] bzr 1.13 released

[Ben Finney]

Congratulations on the release!

Some meta comments:

Bob Tanner <tanner at real-time.com> writes:

> This release includes bug fixes and a few performance and feature
> improvements.
> GNU Changelog output can now be produced by ``bzr log --format gnu- 
> changelog``.
> Debug flags can now be set in ``~/.bazaar/bazaar.conf``. Lightweight
> Checkouts
> and Stacked Branches should both be much faster over remote connections.

Please send these messages using a MUA that doesn't apply
double-wrapping to lines. If that means not using GMail, then that's
what it means.

> The Bazaar team is happy to announce availability of a new
> release of the bzr adaptive version control system.

I like this “announce” and “available” terminology. Could this be
used for non-release milestones, such as betas and release candidates?

“RELEASED: Something that has a name indicating it's not actually a
release” is brain-pain. If instead it were “ANNOUNCE: Something not
yet a release is now available” parses fine.

I don't know if there's some procedure document that would need
updating for this to make the terminology sensible.

> Thanks to everyone who contributed patches, suggestions, and
> feedback.

Thank you for your first successful Bazaar release!

-- 
 \         “A politician is an animal which can sit on a fence and yet |
  `\                  keep both ears to the ground.” —Henry L. Mencken |
_o__)                                                                  |
Ben Finney