/brz/remove-bazaar

IN DEVELOPMENT

  NOTES WHEN UPGRADING:

    * Release 0.15rc2 of bzr changes the ``bzr init-repo`` command to

      default to ``--trees`` instead of ``--no-trees``.

      Existing shared repositories are not affected.

  IMPROVEMENTS:

    * New ``merge-directive`` command to generate machine- and human-readable

      merge requests.  (Aaron Bentley)

    * New ``submit:`` revision specifier makes it easy to diff against the

      common ancestor with the submit location (Aaron Bentley)

    * Added support for Putty's SSH implementation. (Dmitry Vasiliev)

    * Added ``bzr status --versioned`` to report only versioned files, 

      not unknowns. (Kent Gibson)

    * Merge now autodetects the correct line-ending style for its conflict

      markers.  (Aaron Bentley)

  INTERNALS:

    * Refactored SSH vendor registration into SSHVendorManager class.

      (Dmitry Vasiliev)

  BUGFIXES:

    * New ``--numbered-dirs`` option to ``bzr selftest`` to use

      numbered dirs for TestCaseInTempDir. This is default behavior

      on Windows. Anyone can force named dirs on Windows

      with ``--no-numbered-dirs``. (Alexander Belchenko)

    * Fix ``RevisionSpec_revid`` to handle the Unicode strings passed in

      from the command line. (Marien Zwart, #90501)

    * Fix ``TreeTransform._iter_changes`` when both the source and

      destination are missing. (Aaron Bentley, #88842)

    * Fix commit of merges with symlinks in dirstate trees.

      (Marien Zwart)

    * Switch the ``bzr init-repo`` default from --no-trees to --trees. 

      (Wouter van Heyst, #53483)

bzr 0.15rc1  2007-03-07

  SURPRISES:

    * The default disk format has changed. Please run 'bzr upgrade' in your

      working trees to upgrade. This new default is compatible for network

      operations, but not for local operations. That is, if you have two

      versions of bzr installed locally, after upgrading you can only use the

      bzr 0.15 version. This new default does not enable tags or nested-trees

      as they are incompatible with bzr versions before 0.15 over the network.

    * For users of bzrlib: Two major changes have been made to the working tree

      api in bzrlib. The first is that many methods and attributes, including

      the inventory attribute, are no longer valid for use until one of

      lock_read/lock_write/lock_tree_write has been called, and become invalid

      again after unlock is called. This has been done to improve performance

      and correctness as part of the dirstate development. (Robert Collins,

      John A Meinel, Martin Pool, and others).

    * For users of bzrlib: The attribute 'tree.inventory' should be considered

      readonly. Previously it was possible to directly alter this attribute, or

      its contents, and have the tree notice this. This has been made

      unsupported - it may work in some tree formats, but in the newer dirstate

      format such actions will have no effect and will be ignored, or even

      cause assertions. All operations possible can still be carried out by a

      combination of the tree API, and the bzrlib.transform API. (Robert

      Collins, John A Meinel, Martin Pool, and others).

  IMPROVEMENTS:

    * Support for OS Windows 98. Also .bzr.log on any windows system

      saved in My Documents folder. (Alexander Belchenko)

    * ``bzr mv`` enhanced to support already moved files.

      In the past the mv command would have failed if the source file doesn't

      exist. In this situation ``bzr mv`` would now detect that the file has

      already moved and update the repository accordingly, if the target file

      does exist.

      A new option ``--after`` has been added so that if two files already

      exist, you could notify Bazaar that you have moved a (versioned) file

      and replaced it with another. Thus in this case ``bzr move --after``

      will only update the Bazaar identifier.

      (Steffen Eichenberg, Marius Kruger)

    * ``ls`` now works on treeless branches and remote branches.

      (Aaron Bentley)

    * ``bzr help global-options`` describes the global options.

      (Aaron Bentley)

    * ``bzr pull --overwrite`` will now correctly overwrite checkouts.

      (Robert Collins)

    * Files are now allowed to change kind (e.g. from file to symlink).

      Supported by ``commit``, ``revert`` and ``status``

      (Aaron Bentley)

    * ``inventory`` and ``unknowns`` hidden in favour of ``ls``

      (Aaron Bentley)

    * ``bzr help checkouts`` descibes what checkouts are and some possible

      uses of them. (James Westby, Aaron Bentley)

    * A new ``-d`` option to push, pull and merge overrides the default 

      directory.  (Martin Pool)

    * Branch format 6: smaller, and potentially faster than format 5.  Supports

      "append_history_only" mode, where the log view and revnos do not change,

      except by being added to.  Stores policy settings in

      ".bzr/branch/branch.conf".

    * append_only branches:  Format 6 branches may be configured so that log

      view and revnos are always consistent.  Either create the branch using

      "bzr init --append-revisions-only" or edit the config file as descriped

      in docs/configuration.txt.

    * rebind: Format 6 branches retain the last-used bind location, so if you

      "bzr unbind", you can "bzr bind" to bind to the previously-selected

      bind location.

    * Builtin tags support, created and deleted by the ``tag`` command and

      stored in the branch.  Tags can be accessed with the revisionspec

      ``-rtag:``, and listed with ``bzr tags``.  Tags are not versioned 

      at present. Tags require a network incompatible upgrade. To perform this

      upgrade, run ``bzr upgrade --dirstate-with-subtree`` in your branch and

      repositories. (Martin Pool)

    * The bzr:// transport now has a well-known port number, 4155, which it will

      use by default.  (Andrew Bennetts, Martin Pool)

    * Bazaar now looks for user-installed plugins before looking for site-wide

      plugins. (Jonathan Lange)

    * ``bzr resolve`` now detects and marks resolved text conflicts.

      (Aaron Bentley)

  INTERNALS:

    * Internally revision ids and file ids are now passed around as utf-8

      bytestrings, rather than treating them as Unicode strings. This has

      performance benefits for Knits, since we no longer need to decode the

      revision id for each line of content, nor for each entry in the index.

      This will also help with the future dirstate format.

      (John Arbash Meinel)

    * Reserved ids (any revision-id ending in a colon) are rejected by

      versionedfiles, repositories, branches, and working trees

      (Aaron Bentley)

    * Minor performance improvement by not creating a ProgressBar for

      every KnitIndex we create. (about 90ms for a bzr.dev tree)

      (John Arbash Meinel)

    * New easier to use Branch hooks facility. There are five initial hooks,

      all documented in bzrlib.branch.BranchHooks.__init__ - 'set_rh',

      'post_push', 'post_pull', 'post_commit', 'post_uncommit'. These hooks

      fire after the matching operation on a branch has taken place, and were

      originally added for the branchrss plugin. (Robert Collins)

    * New method ``Branch.push()`` which should be used when pushing from a

      branch as it makes performance and policy decisions to match the UI

      level command ``push``. (Robert Collins).

    * Add a new method ``Tree.revision_tree`` which allows access to cached

      trees for arbitrary revisions. This allows the in development dirstate

      tree format to provide access to the callers to cached copies of 

      inventory data which are cheaper to access than inventories from the

      repository.

      (Robert Collins, Martin Pool)

    * New Branch.last_revision_info method, this is being done to allow

      optimization of requests for both the number of revisions and the last

      revision of a branch with smartservers and potentially future branch

      formats. (Wouter van Heyst, Robert Collins)

    * Allow 'import bzrlib.plugins.NAME' to work when the plugin NAME has not

      yet been loaded by load_plugins(). This allows plugins to depend on each

      other for code reuse without requiring users to perform file-renaming

      gymnastics. (Robert Collins)

    * New Repository method 'gather_stats' for statistic data collection.

      This is expected to grow to cover a number of related uses mainly

      related to bzr info. (Robert Collins)

    * Log formatters are now managed with a registry.

      ``log.register_formatter`` continues to work, but callers accessing

      the FORMATTERS dictionary directly will not.

    * Allow a start message to be passed to the ``edit_commit_message``

      function.  This will be placed in the message offered to the user

      for editing above the separator. It allows a template commit message

      to be used more easily. (James Westby)

    * ``GPGStrategy.sign()`` will now raise ``BzrBadParameterUnicode`` if

      you pass a Unicode string rather than an 8-bit string. Callers need

      to be updated to encode first. (John Arbash Meinel)

    * Branch.push, pull, merge now return Result objects with information

      about what happened, rather than a scattering of various methods.  These

      are also passed to the post hooks.  (Martin Pool)

    * File formats and architecture is in place for managing a forest of trees

      in bzr, and splitting up existing trees into smaller subtrees, and

      finally joining trees to make a larger tree. This is the first iteration

      of this support, and the user-facing aspects still require substantial

      work.  If you wish to experiment with it, use ``bzr upgrade

      --dirstate-with-subtree`` in your working trees and repositories.

      You can use the hidden commands ``split`` and ``join`` and to create

      and manipulate nested trees, but please consider using the nested-trees

      branch, which contains substantial UI improvements, instead.

      http://code.aaronbentley.com/bzr/bzrrepo/nested-trees/

      (Aaron Bentley, Martin Pool, Robert Collins).

  BUGFIXES:

    * ``bzr annotate`` now uses dotted revnos from the viewpoint of the

      branch, rather than the last changed revision of the file.

      (John Arbash Meinel, #82158)

    * Lock operations no longer hang if they encounter a permission problem.

      (Aaron Bentley)

    * ``bzr push`` can resume a push that was canceled before it finished.

      Also, it can push even if the target directory exists if you supply

      the ``--use-existing-dir`` flag.

      (John Arbash Meinel, #30576, #45504)

    * Fix http proxy authentication when user and an optional

      password appears in the ``*_proxy`` vars. (Vincent Ladeuil,

      #83954).

    * ``bzr log branch/file`` works for local treeless branches

      (Aaron Bentley, #84247)

    * Fix problem with UNC paths on Windows 98. (Alexander Belchenko, #84728)

    * Searching location of CA bundle for PyCurl in env variable (CURL_CA_BUNDLE),

      and on win32 along the PATH. (Alexander Belchenko, #82086)

    * ``bzr init`` works with unicode argument LOCATION.

      (Alexander Belchenko, #85599)

    * Raise DependencyNotPresent if pycurl do not support https. (Vincent

      Ladeuil, #85305)

    * Invalid proxy env variables should not cause a traceback.

      (Vincent Ladeuil, #87765)

    * Ignore patterns normalised to use '/' path separator.

      (Kent Gibson, #86451)

    * bzr rocks. It sure does! Fix case. (Vincent Ladeuil, #78026)

    * Fix bzrtools shelve command for removed lines beginning with "--"

      (Johan Dahlberg, #75577)

  TESTING:

    * New ``--first`` option to ``bzr selftest`` to run specified tests

      before the rest of the suite.  (Martin Pool)

bzr 0.14  2007-01-23

  IMPROVEMENTS:

    * ``bzr help global-options`` describes the global options. (Aaron Bentley)

  BUG FIXES:

    * Skip documentation generation tests if the tools to do so are not

      available. Fixes running selftest for installled copies of bzr. 

      (John Arbash Meinel, #80330)

    * Fix the code that discovers whether bzr is being run from it's

      working tree to handle the case when it isn't but the directory

      it is in is below a repository. (James Westby, #77306)

bzr 0.14rc1  2007-01-16

  IMPROVEMENTS:

    * New connection: ``bzr+http://`` which supports tunnelling the smart

      protocol over an HTTP connection. If writing is enabled on the bzr

      server, then you can write over the http connection.

      (Andrew Bennetts, John Arbash Meinel)

    * Aliases now support quotation marks, so they can contain whitespace

      (Marius Kruger)

    * PyCurlTransport now use a single curl object. By specifying explicitly

      the 'Range' header, we avoid the need to use two different curl objects

      (and two connections to the same server). (Vincent Ladeuil)

    * ``bzr commit`` does not prompt for a message until it is very likely to

      succeed.  (Aaron Bentley)

    * ``bzr conflicts`` now takes --text to list pathnames of text conflicts

      (Aaron Bentley)

    * Fix ``iter_lines_added_or_present_in_versions`` to use a set instead

      of a list while checking if a revision id was requested. Takes 10s

      off of the ``fileids_affected_by_revision_ids`` time, which is 10s

      of the ``bzr branch`` time. Also improve ``fileids_...`` time by

      filtering lines with a regex rather than multiple ``str.find()``

      calls. (saves another 300ms) (John Arbash Meinel)

    * Policy can be set for each configuration key. This allows keys to be

      inherited properly across configuration entries. For example, this

      should enable you to do::

        [/home/user/project]

        push_location = sftp://host/srv/project/

        push_location:policy = appendpath

      And then a branch like ``/home/user/project/mybranch`` should get an

      automatic push location of ``sftp://host/srv/project/mybranch``.

      (James Henstridge)

    * Added ``bzr status --short`` to make status report svn style flags

      for each file.  For example::

        $ bzr status --short

        A  foo

        A  bar

        D  baz

        ?  wooley

    * 'bzr selftest --clean-output' allows easily clean temporary tests 

      directories without running tests. (Alexander Belchenko)

    * ``bzr help hidden-commands`` lists all hidden commands. (Aaron Bentley)

    * ``bzr merge`` now has an option ``--pull`` to fall back to pull if

      local is fully merged into remote. (Jan Hudec)

    * ``bzr help formats`` describes available directory formats. (Aaron Bentley)

  INTERNALS:

    * A few tweaks directly to ``fileids_affected_by_revision_ids`` to

      help speed up processing, as well allowing to extract unannotated

      lines. Between the two ``fileids_affected_by_revision_ids`` is

      improved by approx 10%. (John Arbash Meinel)

    * Change Revision serialization to only write out millisecond

      resolution. Rather than expecting floating point serialization to

      preserve more resolution than we need. (Henri Weichers, Martin Pool)

    * Test suite ends cleanly on Windows.  (Vincent Ladeuil)

    * When 'encoding_type' attribute of class Command is equal to 'exact', 

      force sys.stdout to be a binary stream on Windows, and therefore

      keep exact line-endings (without LF -> CRLF conversion).

      (Alexander Belchenko)

    * Single-letter short options are no longer globally declared.  (Martin

      Pool)

    * Before using detected user/terminal encoding bzr should check

      that Python has corresponding codec. (Alexander Belchenko)

    * Formats for end-user selection are provided via a FormatRegistry (Aaron Bentley)

  BUG FIXES:

    * ``bzr missing --verbose`` was showing adds/removals in the wrong

      direction. (John Arbash Meinel)

    * ``bzr annotate`` now defaults to showing dotted revnos for merged