/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to NEWS

  • Committer: Robert Collins
  • Date: 2010-05-06 07:48:22 UTC
  • mto: This revision was merged to the branch mainline in revision 5223.
  • Revision ID: robertc@robertcollins.net-20100506074822-0bsgf2j4h8jx0xkk
Added ``bzrlib.tests.matchers`` as a place to put matchers, along with
our first in-tree matcher. See the module docstring for details.
(Robert Collins)

Show diffs side-by-side

added added

removed removed

Lines of Context:
NEWS
13
13
Compatibility Breaks
14
14
********************
15
15
 
16
 
* An API break has been made to the lock_write method of ``Branch`` and
17
 
  ``Repository`` objects; they now return ``branch.BranchWriteLockResult``
18
 
  and ``repository.RepositoryWriteLockResult`` objects. This makes
19
 
  changing the API in future easier and permits some cleaner calling code.
20
 
  (Robert Collins)
21
 
 
22
16
New Features
23
17
************
24
18
 
102
96
  implementations.
103
97
  (Martin Pool)
104
98
 
105
 
* Lock methods on ``Tree``, ``Branch`` and ``Repository`` are now
106
 
  expected to return an object which can be used to unlock them. This reduces
107
 
  duplicate code when using cleanups. The previous 'tokens's returned by
108
 
  ``Branch.lock_write`` and ``Repository.lock_write`` are now attributes
109
 
  on the result of the lock_write. ``repository.RepositoryWriteLockResult``
110
 
  and ``branch.BranchWriteLockResult`` document this. (Robert Collins)
111
 
 
112
99
Internals
113
100
*********
114
101
 
115
 
* ``log._get_info_for_log_files`` now takes an add_cleanup callable.
116
 
  (Robert Collins)
117
 
 
118
102
* ``_remember_remote_is_before`` no longer raises AssertionError when
119
103
  suboptimal network behaviour is noticed; instead it just mutters to the
120
104
  log file (and warns the user if they have set the ``hpss`` debug flag).