Bazaar 1.6.1rc1

This release fixes a few regressions found in the 1.6 client. Fetching
changes was using an O(N^2) buffering algorithm, so for large projects it
would cause memory thrashing. There is also a specific problem with the
``--1.6-rich-root`` format, which prevented stacking on top of
``--rich-root-pack`` repositories, and could allow users to accidentally
fetch experimental data (``-subtree``) without representing it properly.
The ``--1.6-rich-root`` format has been deprecated and users are
recommended to upgrade to ``--1.6.1-rich-root`` immediately. Also we
re-introduced a workaround for users who have repositories with incorrect
nodes (not possible if you only used official releases).
I should also clarify that none of this is data loss level issues, but
still sufficient enough to warrant an updated release.

Milestone information

Project:
Bazaar
Series:
1.6
Version:
1.6.1rc1
Released:
2008-08-29  
Registrant:
John A Meinel
Release registered:
2008-08-29
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon Bazaar-1.6.1rc1-OSX10.4-universal.dmg (md5, sig) Mac OS X 10.4 (universal) installer (for Python 2.5) 107
last downloaded 13 weeks ago
download icon bzr-setup-1.6.1rc1.exe (md5, sig) Windows standalone installer 55
last downloaded 13 weeks ago
download icon bzr-1.6.1rc1.tar.gz (md5, sig) bzr 1.6.1rc1 source 32
last downloaded 56 weeks ago
Total downloads: 194

Release notes 

bzr 1.6.1rc1 2008-08-29
-----------------------

This release fixes a few regressions found in the 1.6 client. Fetching
changes was using an O(N^2) buffering algorithm, so for large projects it
would cause memory thrashing. There is also a specific problem with the
``--1.6-rich-root`` format, which prevented stacking on top of
``--rich-root-pack`` repositories, and could allow users to accidentally
fetch experimental data (``-subtree``) without representing it properly.
The ``--1.6-rich-root`` format has been deprecated and users are
recommended to upgrade to ``--1.6.1-rich-root`` immediately. Also we
re-introduced a workaround for users who have repositories with incorrect
nodes (not possible if you only used official releases).
I should also clarify that none of this is data loss level issues, but
still sufficient enough to warrant an updated release.

  BUG FIXES:

    * ``RemoteTransport.readv()`` was being inefficient about how it
      buffered the readv data and processed it. It would keep appending to
      the same string (causing many copies) and then pop bytes out of the
      start of the string (causing more copies).
      With this patch "bzr+ssh://local" can improve dramatically,
      especially for projects with large files.
      (John Arbash Meinel)

    * Revision texts were always meant to be stored as fulltexts. There
      was a bug in a bzr.dev version that would accidentally create deltas
      when copying from a Pack repo to a Knit repo. This has been fixed,
      but to support those repositories, we know always request full texts
      for Revision texts. (John Arbash Meinel, #261339)

    * The previous ``--1.6-rich-root`` format used an incorrect xml
      serializer, which would accidentally support fetching from a
      repository that supported subtrees, even though the local one would
      not. We deprecated that format, and introduced a new one that uses
      the correct serializer ``--1.6.1-rich-root``.
      (John Arbash Meinel, #262333)

Changelog 

This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.