1
.. -*- mode: indented-text; compile-command: "make -C doc" -*-
9
See also various low-level TODOs in the source code. Try looking in
10
the list archive or on gmane.org for previous discussion of these
13
These are classified by approximate size: an hour or less, a day or
14
less, and several days or more.
20
* ``bzr status`` should show some description of patches that are merged but
21
not yet committed. Preferably in a very compact format so that they
22
just fit on a single line; this could also be used for say ``log
25
2005-11-05 mbp Flowers for stephane
27
* print a message at the end of running the tests telling them tht the
28
test log and output exists but can be removed
30
* tests for running the commit editor, and fix problem of not passing in
33
* Merging add of a new file clashing with an existing file doesn't
34
work; add gets an error that it's already versioned and the merge
37
* Merge should ignore the destination's working directory, otherwise
38
we get an error about the statcache when pulling from a remote
41
* Add of a file that was present in the base revision should put back
44
* Not sure I'm happy with needing to pass a root id to EmptyTree;
45
comparing anything against an EmptyTree with no root should have the
48
* Handle diff of files which do not have a trailing newline; probably
49
requires patching difflib to get it exactly right, or otherwise
50
calling out to GNU diff.
52
* Should be able to copy files between branches to preserve their
53
file-id (and perhaps eventually parentage.)
55
* -r option should take a revision-id as well as a revno.
57
* allow ``bzr st -r 300`` to show a summary of changes since then.
59
* ``bzr info`` should count only people with distinct email addresses as
60
different committers. (Or perhaps only distinct userids?)
62
* On Windows, command-line arguments should be `glob-expanded`__,
63
because the shell doesn't do this. However, there are probably some
64
commands where this shouldn't be done, such as 'bzr ignore', because
65
we want to accept globs.
67
* ``bzr ignore`` command that just adds a line to the ``.bzrignore`` file
68
and makes it versioned. Fix this to break symlinks.
70
* Any useful sanity checks in 'bzr ignore'? Perhaps give a warning if
71
they try to add a single file which is already versioned, or if they
72
add a pattern which already exists, or if it looks like they gave an
75
__ http://mail.python.org/pipermail/python-list/2001-April/037847.html
77
* Separate read and write version checks?
79
* ``bzr status DIR`` should give status on all files under that
82
* ``bzr log DIR`` should give changes to any files within DIR.
84
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
85
giving options to display ids, types, etc.
87
* Split BzrError into various more specific subclasses for different
88
errors people might want to catch.
90
* If the export destination ends in '.tar', '.tar.gz', etc then create
91
a tarball instead of a directory. (Need to actually make a
92
temporary directory and then tar that up.)
94
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
96
* RemoteBranch could maintain a cache either in memory or on disk. We
97
know more than an external cache might about which files are
98
immutable and which can vary. On the other hand, it's much simpler
99
to just use an external proxy cache.
101
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
102
~/.arch-cache, containing revision information encoded almost as a
103
bunch of archives. Perhaps we could simply store full paths.
105
* Maybe also store directories in the statcache so that we can quickly
106
identify that they still exist.
108
* Diff should show timestamps; for files from the working directory we
109
can use the file itself; for files from a revision we should use the
110
commit time of the revision.
112
* Perhaps split command infrastructure from the actual command
115
* Cleaner support for negative boolean options like --no-recurse.
117
* Statcache should possibly map all file paths to / separators
119
* quotefn doubles all backslashes on Windows; this is probably not the
120
best thing to do. What would be a better way to safely represent
121
filenames? Perhaps we could doublequote things containing spaces,
122
on the principle that filenames containing quotes are unlikely?
123
Nice for humans; less good for machine parsing.
125
* Patches should probably use only forward slashes, even on Windows,
126
otherwise Unix patch can't apply them. (?)
128
* Branch.update_revisions() inefficiently fetches revisions from the
129
remote server twice; once to find out what text and inventory they
130
need and then again to actually get the thing. This is a bit
133
One complicating factor here is that we don't really want to have
134
revisions present in the revision-store until all their constituent
135
parts are also stored.
137
The basic problem is that RemoteBranch.get_revision() and similar
138
methods return object, but what we really want is the raw XML, which
139
can be popped into our own store. That needs to be refactored.
141
* ``bzr status FOO`` where foo is ignored should say so.
143
* ``bzr mkdir A...`` should just create and add A.
145
* Guard against repeatedly merging any particular patch.
147
* More options for diff:
149
- diff two revisions of the same tree
151
- diff two different branches, optionally at different revisions
153
- diff a particular file in another tree against the corresponding
154
version in this tree (which should be the default if the second
155
parameter is a tree root)
157
- diff everything under a particular directory, in any of the above
160
- diff two files inside the same tree, even if they have different
163
- and, of course, tests for all this
165
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
167
* Reproducible performance benchmark to measure whether performance is
168
getting better or worse.
174
* Merge revert patch.
176
* ``bzr mv`` that does either rename or move as in Unix.
178
* More efficient diff of only selected files. We should be able to
179
just get the id for the selected files, look up their location and
180
diff just those files. No need to traverse the entire inventories.
182
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
183
under that directory.
185
* Fix up Inventory objects to represent root object as an entry.
187
* Don't convert entire entry from ElementTree to an object when it is
188
read in, but rather wait until the program actually wants to know
191
* Extract changes from one revision to the next to a text form
192
suitable for transmission over email.
196
- Selected-file commit
198
- Impossible selected-file commit: adding things in non-versioned
199
directories, crossing renames, etc.
201
* Write a reproducible benchmark, perhaps importing various kernel versions.
203
* Directly import diffs! It seems a bit redundant to need to rescan
204
the directory to work out what files diff added/deleted/changed when
205
all the information is there in the diff in the first place.
206
Getting the exact behaviour for added/deleted subdirectories etc
209
At the very least we could run diffstat over the diff, or perhaps
210
read the status output from patch. Just knowing which files might
211
be modified would be enough to guide the add and commit.
213
Given this we might be able to import patches at 1/second or better.
215
* Get branch over http.
217
* Pull pure updates over http.
219
* revfile compression.
221
* Split inventory into per-directory files.
223
* Fix ignore file parsing:
225
- fnmatch is not the same as unix patterns
227
- perhaps add extended globs from rsh/rsync
229
- perhaps a pattern that matches only directories or non-directories
231
* Consider using Python logging library as well as/instead of
234
* Commands should give some progress indication by default.
236
- But quieten this with ``--silent``.
238
* Change to using gettext message localization.
240
* Make a clearer separation between internal and external bzrlib
241
interfaces. Make internal interfaces use protected names. Write at
242
least some documentation for those APIs, probably as docstrings.
244
Consider using ZopeInterface definitions for the external interface;
245
I think these are already used in PyBaz. They allow automatic
246
checking of the interface but may be unfamiliar to general Python
247
developers, so I'm not really keen.
249
* Commands to dump out all command help into a manpage or HTML file or
252
* Handle symlinks in the working directory; at the very least it
253
should be possible for them to be present and ignored/unknown
254
without causing assertion failures.
256
Eventually symlinks should be versioned.
258
* Allow init in a subdirectory to create a nested repository, but only
259
if the subdirectory is not already versioned. Perhaps also require
260
a ``--nested`` to protect against confusion.
264
* More test framework:
266
- Class that describes the state of a working tree so we can just
269
* There are too many methods on Branch() that really manipulate the
270
WorkingTree. They should be moved across.
272
Also there are some methods which are duplicated on Tree and
273
Inventory objects, and it should be made more clear which ones are
274
proxies and which ones behave differently, and how.
276
* Try using XSLT to add some formatting to REST-generated HTML. Or
277
maybe write a small Python program that specifies a header and foot
278
for the pages and calls into the docutils libraries.
280
* --format=xml for log, status and other commands.
282
* Attempting to explicitly add a file that's already added should give
283
a warning; however there should be no warning for directories (since
284
we scan for new children) or files encountered in a directory that's
287
* Better handling of possible collisions on case-losing filesystems;
288
make sure a single file does not get added twice under different
291
* Clean up XML inventory:
293
- Use nesting rather than parent_id pointers.
295
- Hold the ElementTree in memory in the Inventory object and work
296
directly on that, rather than converting into Python objects every
297
time it is read in. Probably still exposoe it through some kind of
298
object interface though, but perhaps that should just be a proxy
301
- Less special cases for the root directory.
303
* Perhaps inventories should remember the revision in which each file
304
was last changed, as well as its current state? This is a bit
305
redundant but might often be interested to know.
307
* stat cache should perhaps only stat files as necessary, rather than
308
doing them all up-front. On the other hand, that disallows the
309
opimization of stating them in inode order.
311
* It'd be nice to pipeline multiple HTTP requests. Often we can
312
predict what will be wanted in future: all revisions, or all texts
313
in a particular revision, etc.
315
urlgrabber's docs say they are working on batched downloads; we
316
could perhaps ride on that or just create a background thread (ew).
318
* Paranoid mode where we never trust SHA-1 matches.
320
* Don't commit if there are no changes unless forced.
322
* --dry-run mode for commit? (Or maybe just run with
323
check-command=false?)
325
* Generally, be a bit more verbose unless --silent is specified.
327
* Function that finds all changes to files under a given directory;
328
perhaps log should use this if a directory is given.
330
* XML attributes might have trouble with filenames containing \n and
331
\r. Do we really want to support this? I think perhaps not.
333
* Remember execute bits, so that exports will work OK.
335
* Unify smart_add and plain Branch.add(); perhaps smart_add should
336
just build a list of files to add and pass that to the regular add
339
* Function to list a directory, saying in which revision each file was
340
last modified. Useful for web and gui interfaces, and slow to
341
compute one file at a time.
343
* unittest is standard, but the results are kind of ugly; would be
344
nice to make it cleaner.
346
* Check locking is correct during merge-related operations.
348
* Perhaps attempts to get locks should timeout after some period of
349
time, or at least display a progress message.
351
* Split out upgrade functionality from check command into a separate
354
* Don't pass around command classes but rather pass objects. This'd
355
make it cleaner to construct objects wrapping external commands.
357
* Track all merged-in revisions in a versioned add-only metafile.
363
* Generate annotations from current file relative to previous
366
- Is it necessary to store any kind of annotation where data was
369
* Update revfile_ format and make it active:
371
- Texts should be identified by something keyed on the revision, not
372
an individual text-id. This is much more useful for annotate I
373
think; we want to map back to the revision that last changed it.
375
- Access revfile revisions through the Tree/Store classes.
377
- Check them from check commands.
381
.. _revfile: revfile.html
383
* Hooks for pre-commit, post-commit, etc.
385
Consider the security implications; probably should not enable hooks
386
for remotely-fetched branches by default.
388
* Pre-commit check. If this hook is defined, it needs to be handled
389
specially: create a temporary directory containing the tree as it
390
will be after the commit. This means excluding any ignored/unknown
391
files, and respecting selective commits. Run the pre-commit check
392
(e.g. compile and run test suite) in there.
394
Possibly this should be done by splitting the commit function into
395
several parts (under a single interface). It is already rather
396
large. Decomposition:
398
- find tree modifications and prepare in-memory inventory
400
- export that inventory to a temporary directory
402
- run the test in that temporary directory
404
- if that succeeded, continue to actually finish the commit
406
What should be done with the text of modified files while this is
407
underway? I don't think we want to count on holding them in memory
408
and we can't trust the working files to stay in one place so I
409
suppose we need to move them into the text store, or otherwise into
410
a temporary directory.
412
If the commit does not actually complete, we would rather the
413
content was not left behind in the stores.
417
* GUI (maybe in Python GTK+?)
419
* C library interface
421
* Expansion of $Id$ keywords within working files. Perhaps do this in
422
exports first as a simpler case because then we don't need to deal
423
with removing the tags on the way back in.
added
removed
TODO
