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; at the
83
moment it only lists things which modify the specific named file
84
(and not its contents)
86
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
87
giving options to display ids, types, etc.
89
* Split BzrError into various more specific subclasses for different
90
errors people might want to catch.
92
* If the export destination ends in '.tar', '.tar.gz', etc then create
93
a tarball instead of a directory. (Need to actually make a
94
temporary directory and then tar that up.)
96
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
98
* RemoteBranch could maintain a cache either in memory or on disk. We
99
know more than an external cache might about which files are
100
immutable and which can vary. On the other hand, it's much simpler
101
to just use an external proxy cache.
103
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
104
~/.arch-cache, containing revision information encoded almost as a
105
bunch of archives. Perhaps we could simply store full paths.
107
* Maybe also store directories in the statcache so that we can quickly
108
identify that they still exist.
110
* Diff should show timestamps; for files from the working directory we
111
can use the file itself; for files from a revision we should use the
112
commit time of the revision.
114
* Perhaps split command infrastructure from the actual command
117
* Cleaner support for negative boolean options like --no-recurse.
119
* Statcache should possibly map all file paths to / separators
121
* quotefn doubles all backslashes on Windows; this is probably not the
122
best thing to do. What would be a better way to safely represent
123
filenames? Perhaps we could doublequote things containing spaces,
124
on the principle that filenames containing quotes are unlikely?
125
Nice for humans; less good for machine parsing.
127
* Patches should probably use only forward slashes, even on Windows,
128
otherwise Unix patch can't apply them. (?)
130
* Branch.update_revisions() inefficiently fetches revisions from the
131
remote server twice; once to find out what text and inventory they
132
need and then again to actually get the thing. This is a bit
135
One complicating factor here is that we don't really want to have
136
revisions present in the revision-store until all their constituent
137
parts are also stored.
139
The basic problem is that RemoteBranch.get_revision() and similar
140
methods return object, but what we really want is the raw XML, which
141
can be popped into our own store. That needs to be refactored.
143
* ``bzr status FOO`` where foo is ignored should say so.
145
* ``bzr mkdir A...`` should just create and add A.
147
* Guard against repeatedly merging any particular patch.
149
* More options for diff:
151
- diff two revisions of the same tree
153
- diff two different branches, optionally at different revisions
155
- diff a particular file in another tree against the corresponding
156
version in this tree (which should be the default if the second
157
parameter is a tree root)
159
- diff everything under a particular directory, in any of the above
162
- diff two files inside the same tree, even if they have different
165
- and, of course, tests for all this
167
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
169
* Reproducible performance benchmark to measure whether performance is
170
getting better or worse.
172
* ``bzr log -m foo`` should perhaps error if nothing matches?
178
* Merge revert patch.
180
* ``bzr mv`` that does either rename or move as in Unix.
182
* More efficient diff of only selected files. We should be able to
183
just get the id for the selected files, look up their location and
184
diff just those files. No need to traverse the entire inventories.
186
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
187
under that directory.
189
* Fix up Inventory objects to represent root object as an entry.
191
* Don't convert entire entry from ElementTree to an object when it is
192
read in, but rather wait until the program actually wants to know
195
* Extract changes from one revision to the next to a text form
196
suitable for transmission over email.
200
- Selected-file commit
202
- Impossible selected-file commit: adding things in non-versioned
203
directories, crossing renames, etc.
205
* Write a reproducible benchmark, perhaps importing various kernel versions.
207
* Directly import diffs! It seems a bit redundant to need to rescan
208
the directory to work out what files diff added/deleted/changed when
209
all the information is there in the diff in the first place.
210
Getting the exact behaviour for added/deleted subdirectories etc
213
At the very least we could run diffstat over the diff, or perhaps
214
read the status output from patch. Just knowing which files might
215
be modified would be enough to guide the add and commit.
217
Given this we might be able to import patches at 1/second or better.
219
* Get branch over http.
221
* Pull pure updates over http.
223
* revfile compression.
225
* Split inventory into per-directory files.
227
* Fix ignore file parsing:
229
- fnmatch is not the same as unix patterns
231
- perhaps add extended globs from rsh/rsync
233
- perhaps a pattern that matches only directories or non-directories
235
* Consider using Python logging library as well as/instead of
238
* Commands should give some progress indication by default.
240
- But quieten this with ``--silent``.
242
* Change to using gettext message localization.
244
* Make a clearer separation between internal and external bzrlib
245
interfaces. Make internal interfaces use protected names. Write at
246
least some documentation for those APIs, probably as docstrings.
248
Consider using ZopeInterface definitions for the external interface;
249
I think these are already used in PyBaz. They allow automatic
250
checking of the interface but may be unfamiliar to general Python
251
developers, so I'm not really keen.
253
* Commands to dump out all command help into a manpage or HTML file or
256
* Handle symlinks in the working directory; at the very least it
257
should be possible for them to be present and ignored/unknown
258
without causing assertion failures.
260
Eventually symlinks should be versioned.
262
* Allow init in a subdirectory to create a nested repository, but only
263
if the subdirectory is not already versioned. Perhaps also require
264
a ``--nested`` to protect against confusion.
268
* More test framework:
270
- Class that describes the state of a working tree so we can just
273
* There are too many methods on Branch() that really manipulate the
274
WorkingTree. They should be moved across.
276
Also there are some methods which are duplicated on Tree and
277
Inventory objects, and it should be made more clear which ones are
278
proxies and which ones behave differently, and how.
280
* Try using XSLT to add some formatting to REST-generated HTML. Or
281
maybe write a small Python program that specifies a header and foot
282
for the pages and calls into the docutils libraries.
284
* --format=xml for log, status and other commands.
286
* Attempting to explicitly add a file that's already added should give
287
a warning; however there should be no warning for directories (since
288
we scan for new children) or files encountered in a directory that's
291
* Better handling of possible collisions on case-losing filesystems;
292
make sure a single file does not get added twice under different
295
* Clean up XML inventory:
297
- Use nesting rather than parent_id pointers.
299
- Hold the ElementTree in memory in the Inventory object and work
300
directly on that, rather than converting into Python objects every
301
time it is read in. Probably still exposoe it through some kind of
302
object interface though, but perhaps that should just be a proxy
305
- Less special cases for the root directory.
307
* Perhaps inventories should remember the revision in which each file
308
was last changed, as well as its current state? This is a bit
309
redundant but might often be interested to know.
311
* stat cache should perhaps only stat files as necessary, rather than
312
doing them all up-front. On the other hand, that disallows the
313
opimization of stating them in inode order.
315
* It'd be nice to pipeline multiple HTTP requests. Often we can
316
predict what will be wanted in future: all revisions, or all texts
317
in a particular revision, etc.
319
urlgrabber's docs say they are working on batched downloads; we
320
could perhaps ride on that or just create a background thread (ew).
322
* Paranoid mode where we never trust SHA-1 matches.
324
* Don't commit if there are no changes unless forced.
326
* --dry-run mode for commit? (Or maybe just run with
327
check-command=false?)
329
* Generally, be a bit more verbose unless --silent is specified.
331
* Function that finds all changes to files under a given directory;
332
perhaps log should use this if a directory is given.
334
* XML attributes might have trouble with filenames containing \n and
335
\r. Do we really want to support this? I think perhaps not.
337
* Remember execute bits, so that exports will work OK.
339
* Unify smart_add and plain Branch.add(); perhaps smart_add should
340
just build a list of files to add and pass that to the regular add
343
* Function to list a directory, saying in which revision each file was
344
last modified. Useful for web and gui interfaces, and slow to
345
compute one file at a time.
347
* unittest is standard, but the results are kind of ugly; would be
348
nice to make it cleaner.
350
* Check locking is correct during merge-related operations.
352
* Perhaps attempts to get locks should timeout after some period of
353
time, or at least display a progress message.
355
* Split out upgrade functionality from check command into a separate
358
* Don't pass around command classes but rather pass objects. This'd
359
make it cleaner to construct objects wrapping external commands.
361
* Track all merged-in revisions in a versioned add-only metafile.
363
* ``pull --clobber`` should discard any local changes not present
364
remotely. Not generally what you want, but possibly useful when
365
you're just mirroring another branch and want to keep tracking it
366
even when they e.g. uncommit or make similar non-forward movements.
367
Also for push I suppose. Clobber may not be the best name, maybe
370
* ``uncommit`` command that removes a revision from the end of the
371
revision-history; just doing this is enough to remove the commit,
372
and a new commit will automatically be made against the
373
predecessor. This can be repeated.
375
It only makes sense to delete from the tail of history, not from the
378
The revision, its inventory and texts remain floating in the store.
379
We should perhaps add the revision to a list of removed-commits, so
380
that it can be restored or at least accounted for when checking
381
consistency. This file would not be versioned, and probably should
382
not propagate when branched.
384
If we track merged revisions then we need to update this list too.
385
If the list is stored in a weave it's easy (implicit): the version
386
of the list can remain but it won't be referenced anymore. It's
387
probably best to just store this list in a weave in the first place
394
* Generate annotations from current file relative to previous
397
- Is it necessary to store any kind of annotation where data was
400
* Update revfile_ format and make it active:
402
- Texts should be identified by something keyed on the revision, not
403
an individual text-id. This is much more useful for annotate I
404
think; we want to map back to the revision that last changed it.
406
- Access revfile revisions through the Tree/Store classes.
408
- Check them from check commands.
412
.. _revfile: revfile.html
414
* Hooks for pre-commit, post-commit, etc.
416
Consider the security implications; probably should not enable hooks
417
for remotely-fetched branches by default.
419
* Pre-commit check. If this hook is defined, it needs to be handled
420
specially: create a temporary directory containing the tree as it
421
will be after the commit. This means excluding any ignored/unknown
422
files, and respecting selective commits. Run the pre-commit check
423
(e.g. compile and run test suite) in there.
425
Possibly this should be done by splitting the commit function into
426
several parts (under a single interface). It is already rather
427
large. Decomposition:
429
- find tree modifications and prepare in-memory inventory
431
- export that inventory to a temporary directory
433
- run the test in that temporary directory
435
- if that succeeded, continue to actually finish the commit
437
What should be done with the text of modified files while this is
438
underway? I don't think we want to count on holding them in memory
439
and we can't trust the working files to stay in one place so I
440
suppose we need to move them into the text store, or otherwise into
441
a temporary directory.
443
If the commit does not actually complete, we would rather the
444
content was not left behind in the stores.
448
* GUI (maybe in Python GTK+?)
450
* C library interface
452
* Expansion of $Id$ keywords within working files. Perhaps do this in
453
exports first as a simpler case because then we don't need to deal
454
with removing the tags on the way back in.
1
For things to do in Bazaar development, see
3
https://bugs.launchpad.net/bzr/
4
https://blueprints.launchpad.net/bzr/
added
removed
TODO
