bzr 1.12rc1 released

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> On behalf of the Bazaar team I'm happy to announce availability of the
> first release candidate for bzr 1.12.
> 
> This release of Bazaar contains many improvements to the speed and
> functionality of ``bzr log`` and the display of logged revisions by ``bzr
> status``.  bzr now also gives a better indication of progress, both in the
> way operations are drawn onto a text terminal, and by showing the rate of
> network IO.
> 
> Thanks to everyone who contributed patches, suggestions, and
> feedback.
> 
> bzr 1.12rc1 is available now as a source tarball from
> <http://bazaar-vcs.org/Download>.  Packages
> for various systems will be available soon.
> 

Win32 installers containing bzr 1.12rc1, bzrtools 1.12.0, qbzr 0.9.7,
and bzr-svn 0.5.0 have been uploaded.

I would appreciate people installing it and giving feedback before the
final release next week.

Also, I would like to point out that this is a large change for bzr-svn
that includes a format bump. I'm including the UPGRADING note here:

Upgrading from bzr-svn 0.4.x to 0.5.x
=====================================

bzr-svn 0.5 introduces a new version of the mapping used by bzr-svn.
This has several advantages, such as making bzr-svn more flexible in
what paths are considered branches and being able to work without
bzr-specific file properties in a Subversion >= 1.5 repository when
pushing/committing to that repository from bzr.

Disadvantage of this new mapping format is that older bzr-svn clients
won't be able to recognize any bzr metadata on new revisions pushed
using bzr-svn 0.5.

It is possible to make bzr-svn use the old-style mappings when pushing
revisions by setting "default-mapping = v3" in ~/.bazaar/bazaar.conf or
~/.bazaar/subversion.conf, for example if you still use older versions
of bzr-svn that you can't upgrade.


I'll also note that without setting "default-mapping = v3" your existing
bzr branches will appear diverged from the svn branches, and the svn
branches will be converted "from scratch" (as I understand it).

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmR400ACgkQJdeBCYSNAANVpQCcCs96vHd2hQV5riObYKMV5hES
T4QAnRmd71BSDnQWwoK9n/GKFaEN0yG4
=J7o6
-----END PGP SIGNATURE-----