/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 11:08:10 UTC
  • mto: This revision was merged to the branch mainline in revision 5223.
  • Revision ID: robertc@robertcollins.net-20100506110810-h3j07fh5gmw54s25
Cleaner matcher matching revised unlocking protocol.

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
 
  The lock_read method has also changed from having no defined return
21
 
  value to returning ``LogicalLockResult`` objects.
22
 
  (Robert Collins)
23
 
 
24
16
New Features
25
17
************
26
18
 
104
96
  implementations.
105
97
  (Martin Pool)
106
98
 
107
 
* Lock methods on ``Tree``, ``Branch`` and ``Repository`` are now
108
 
  expected to return an object which can be used to unlock them. This reduces
109
 
  duplicate code when using cleanups. The previous 'tokens's returned by
110
 
  ``Branch.lock_write`` and ``Repository.lock_write`` are now attributes
111
 
  on the result of the lock_write. ``repository.RepositoryWriteLockResult``
112
 
  and ``branch.BranchWriteLockResult`` document this. (Robert Collins)
113
 
 
114
99
Internals
115
100
*********
116
101
 
117
 
* ``log._get_info_for_log_files`` now takes an add_cleanup callable.
118
 
  (Robert Collins)
119
 
 
120
102
* ``_remember_remote_is_before`` no longer raises AssertionError when
121
103
  suboptimal network behaviour is noticed; instead it just mutters to the
122
104
  log file (and warns the user if they have set the ``hpss`` debug flag).