20
* Fix tests so that import errors caused by modules don't produce false reports
21
that the tests themselves don't exist.
23
* Fix tests so that one test failure doesn't prevent other tests from running
25
* print a message at the end of running the tests telling them that the
26
test log and output exists but can be removed
28
* tests for running the commit editor, and fix problem of not passing in
31
* Merging add of a new file clashing with an existing file doesn't
32
work; add gets an error that it's already versioned and the merge
35
* Merge should ignore the destination's working directory, otherwise
36
we get an error about the statcache when pulling from a remote
39
20
* Add of a file that was present in the base revision should put back
40
21
the previous file-id.
42
* Not sure I'm happy with needing to pass a root id to EmptyTree;
43
comparing anything against an EmptyTree with no root should have the
46
23
* Handle diff of files which do not have a trailing newline; probably
47
24
requires patching difflib to get it exactly right, or otherwise
48
25
calling out to GNU diff.
50
* Should be able to copy files between branches to preserve their
51
file-id (and perhaps eventually parentage.)
27
* Import ElementTree update patch.
29
* Plugins that provide commands. By just installing a file into some
30
directory (e.g. ``/usr/share/bzr/plugins``) it should be possible to
31
create new top-level commands (``bzr frob``). Extensions can be
32
written in either Python (in which case they use the bzrlib API) or
33
in a separate process (in sh, C, whatever). It should be possible
34
to get help for plugin commands.
36
* Smart rewrap text in help messages to fit in $COLUMNS (or equivalent
53
39
* -r option should take a revision-id as well as a revno.
41
* ``bzr info`` could show space used by working tree, versioned files,
42
unknown and ignored files.
55
44
* ``bzr info`` should count only people with distinct email addresses as
56
45
different committers. (Or perhaps only distinct userids?)
75
64
* ``bzr status DIR`` should give status on all files under that
78
* ``bzr log DIR`` should give changes to any files within DIR; at the
79
moment it only lists things which modify the specific named file
80
(and not its contents)
67
* ``bzr log DIR`` should give changes to any files within DIR.
69
* Check all commands have decent help.
82
71
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
83
72
giving options to display ids, types, etc.
74
* Split BzrError into various more specific subclasses for different
75
errors people might want to catch.
77
* If the export destination ends in '.tar', '.tar.gz', etc then create
78
a tarball instead of a directory. (Need to actually make a
79
temporary directory and then tar that up.)
81
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
85
83
* RemoteBranch could maintain a cache either in memory or on disk. We
86
84
know more than an external cache might about which files are
87
85
immutable and which can vary. On the other hand, it's much simpler
112
110
Nice for humans; less good for machine parsing.
114
112
* Patches should probably use only forward slashes, even on Windows,
115
otherwise Unix patch can't apply them. (?)
113
otherwise Unix patch can't apply them. (?)
117
115
* Branch.update_revisions() inefficiently fetches revisions from the
118
116
remote server twice; once to find out what text and inventory they
119
117
need and then again to actually get the thing. This is a bit
122
120
One complicating factor here is that we don't really want to have
123
121
revisions present in the revision-store until all their constituent
127
125
methods return object, but what we really want is the raw XML, which
128
126
can be popped into our own store. That needs to be refactored.
130
* Guard against repeatedly merging any particular patch.
132
* More options for diff:
134
- diff two revisions of the same tree
136
- diff two different branches, optionally at different revisions
138
- diff a particular file in another tree against the corresponding
139
version in this tree (which should be the default if the second
140
parameter is a tree root)
142
- diff everything under a particular directory, in any of the above
145
- diff two files inside the same tree, even if they have different
148
- and, of course, tests for all this
150
* Reproducible performance benchmark to measure whether performance is
151
getting better or worse.
153
* ``bzr log -m foo`` should perhaps error if nothing matches?
155
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
157
If diffing between two branches then we probably want two -r
158
options, since the revisions don't form a range that can be
159
evaluated on either one.
161
* bzr diff shouldn't diff binary files
163
* setup.py install when run from a bzr tree should freeze the tree
164
revision-id into the installed bzr.
166
* bzr script should trap ImportError and perhaps give a better error
169
* revert after a merge should possibly remove all the BASE/THIS/OTHER
170
files to get you back to where you were.
172
* files that are added and then deleted are still reported as added
174
* stores should raise KeyError, not IndexError
176
* merging from a remote branch seems to sometimes raise errors not
179
* should be possible to give a related branch when pulling from a
180
remote branch to make things faster
182
* sometimes gives "conflicting add" even when the contents are in fact
185
* BZRDIR should be in branch.py not __init__.py.
187
* bzrlib.delta.compare_trees() shouldn't need to sort all of the result
188
lists, since they are being added in alphabetical order. Write tests
189
to guarantee this, and remove the sort() calls.
128
* ``bzr status FOO`` where foo is ignored should say so.
130
* ``bzr mkdir A...`` should just create and add A.
194
* merge should add all revision and inventory XML to the local store.
196
* check should give a warning for revisions that are named in the
197
chain but not actually present in the store.
199
* remove anything outside of the branch implementation that directly
137
* Merge revert patch.
139
* ``bzr mv`` that does either rename or move as in Unix.
202
141
* More efficient diff of only selected files. We should be able to
203
142
just get the id for the selected files, look up their location and
204
143
diff just those files. No need to traverse the entire inventories.
145
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
146
under that directory.
206
148
* Fix up Inventory objects to represent root object as an entry.
208
150
* Don't convert entire entry from ElementTree to an object when it is
232
172
At the very least we could run diffstat over the diff, or perhaps
233
173
read the status output from patch. Just knowing which files might
234
174
be modified would be enough to guide the add and commit.
236
176
Given this we might be able to import patches at 1/second or better.
178
* Get branch over http.
180
* Pull pure updates over http.
238
182
* revfile compression.
240
* Split inventory into per-directory files?
184
* Split inventory into per-directory files.
242
186
* Fix ignore file parsing:
278
222
if the subdirectory is not already versioned. Perhaps also require
279
223
a ``--nested`` to protect against confusion.
283
227
* More test framework:
285
229
- Class that describes the state of a working tree so we can just
286
230
assert it's equal.
232
* There are too many methods on Branch() that really manipulate the
233
WorkingTree. They should be moved across.
235
Also there are some methods which are duplicated on Tree and
236
Inventory objects, and it should be made more clear which ones are
237
proxies and which ones behave differently, and how.
288
239
* Try using XSLT to add some formatting to REST-generated HTML. Or
289
240
maybe write a small Python program that specifies a header and foot
290
241
for the pages and calls into the docutils libraries.
307
258
- Hold the ElementTree in memory in the Inventory object and work
308
259
directly on that, rather than converting into Python objects every
309
time it is read in. Probably still expose it through some kind of
260
time it is read in. Probably still exposoe it through some kind of
310
261
object interface though, but perhaps that should just be a proxy
311
262
for the elements.
313
- Less special cases for the root directory.
264
- Less special cases for the root directory.
315
266
* Perhaps inventories should remember the revision in which each file
316
267
was last changed, as well as its current state? This is a bit
319
270
* stat cache should perhaps only stat files as necessary, rather than
320
271
doing them all up-front. On the other hand, that disallows the
321
optimization of stating them in inode order.
272
opimization of stating them in inode order.
323
274
* It'd be nice to pipeline multiple HTTP requests. Often we can
324
275
predict what will be wanted in future: all revisions, or all texts
325
in a particular revision, etc.
276
in a particular revision, etc.
327
278
urlgrabber's docs say they are working on batched downloads; we
328
279
could perhaps ride on that or just create a background thread (ew).
330
281
* Paranoid mode where we never trust SHA-1 matches.
283
* Don't commit if there are no changes unless forced.
332
285
* --dry-run mode for commit? (Or maybe just run with
333
286
check-command=false?)
340
293
* XML attributes might have trouble with filenames containing \n and
341
294
\r. Do we really want to support this? I think perhaps not.
296
* Remember execute bits, so that exports will work OK.
343
298
* Unify smart_add and plain Branch.add(); perhaps smart_add should
344
299
just build a list of files to add and pass that to the regular add
347
302
* Function to list a directory, saying in which revision each file was
348
last modified. Useful for web and GUI interfaces, and slow to
303
last modified. Useful for web and gui interfaces, and slow to
349
304
compute one file at a time.
351
This will be done when we track file texts by referring to the
352
version that created them.
306
* unittest is standard, but the results are kind of ugly; would be
307
nice to make it cleaner.
354
309
* Check locking is correct during merge-related operations.
356
311
* Perhaps attempts to get locks should timeout after some period of
357
312
time, or at least display a progress message.
314
* Split out upgrade functionality from check command into a separate
359
317
* Don't pass around command classes but rather pass objects. This'd
360
318
make it cleaner to construct objects wrapping external commands.
362
* Track all merged-in revisions in a versioned add-only metafile.
364
* ``uncommit`` command that removes a revision from the end of the
365
revision-history; just doing this is enough to remove the commit,
366
and a new commit will automatically be made against the
367
predecessor. This can be repeated.
369
It only makes sense to delete from the tail of history.
371
This has been implemented, but it does not remove the texts from
374
* ``bzrlib.lazy_import.lazy_import`` could check to see if a given
375
module has already been imported (look at ``sys.modules``). If it
376
has, then just import it directly, rather than creating a lazy
443
384
with removing the tags on the way back in.
450
* Write some benchmark tests
452
* we could display the ids of some tests selected by time to rune, or cputime,
455
* We could run tests multiple times and report deviation/slowest/fastest.
457
* Gather lsprofile output for each test individually - log that somewhere.
459
* Should plugins be able to offer benchmark tests ?
463
Ensure changeset command behaves properly w/revisions (e.g. 0)
464
Figure out whether testament-related bug is my problem
465
Get rid of the 'old' directory
467
What to do about ghost ancestors in remote branch that are present locally?
added
removed
TODO
