bzr-svn (0.5.0~rc1-1) unstable; urgency=low

  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.

 -- Jelmer Vernooij <jelmer@samba.org>  Fri, 28 Nov 2008 17:07:00 +0100

bzr-svn (0.4.0-1) unstable; urgency=low

  As of this version bzr-svn creates revisions with different revision ids than 
  previous versions. In other words, existing bzr-svn branches created with 
  0.3.x can not be used directly with 0.4.0 but will have to be upgraded to 
  work with 0.4.0 using the "bzr svn-upgrade" command. The bzr-rebase package 
  has to be installed for this command to work correctly.

 -- Jelmer Vernooij <jelmer@samba.org>  Sun, 05 Aug 2007 14:14:54 +0200
