1
For things to do in Bazaar development, see
3
https://bugs.launchpad.net/bzr/
4
https://blueprints.launchpad.net/bzr/
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
* Merging add of a new file clashing with an existing file doesn't
21
work; add gets an error that it's already versioned and the merge
24
* Merge should ignore the destination's working directory, otherwise
25
we get an error about the statcache when pulling from a remote
28
* Add of a file that was present in the base revision should put back
31
* Handle diff of files which do not have a trailing newline; probably
32
requires patching difflib to get it exactly right, or otherwise
33
calling out to GNU diff.
35
* -r option should take a revision-id as well as a revno.
37
* ``bzr info`` should count only people with distinct email addresses as
38
different committers. (Or perhaps only distinct userids?)
40
* On Windows, command-line arguments should be `glob-expanded`__,
41
because the shell doesn't do this. However, there are probably some
42
commands where this shouldn't be done, such as 'bzr ignore', because
43
we want to accept globs.
45
* ``bzr ignore`` command that just adds a line to the ``.bzrignore`` file
46
and makes it versioned. Fix this to break symlinks.
48
* Any useful sanity checks in 'bzr ignore'? Perhaps give a warning if
49
they try to add a single file which is already versioned, or if they
50
add a pattern which already exists, or if it looks like they gave an
53
__ http://mail.python.org/pipermail/python-list/2001-April/037847.html
55
* Separate read and write version checks?
57
* ``bzr status DIR`` should give status on all files under that
60
* ``bzr log DIR`` should give changes to any files within DIR.
62
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
63
giving options to display ids, types, etc.
65
* Split BzrError into various more specific subclasses for different
66
errors people might want to catch.
68
* If the export destination ends in '.tar', '.tar.gz', etc then create
69
a tarball instead of a directory. (Need to actually make a
70
temporary directory and then tar that up.)
72
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
74
* RemoteBranch could maintain a cache either in memory or on disk. We
75
know more than an external cache might about which files are
76
immutable and which can vary. On the other hand, it's much simpler
77
to just use an external proxy cache.
79
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
80
~/.arch-cache, containing revision information encoded almost as a
81
bunch of archives. Perhaps we could simply store full paths.
83
* Maybe also store directories in the statcache so that we can quickly
84
identify that they still exist.
86
* Diff should show timestamps; for files from the working directory we
87
can use the file itself; for files from a revision we should use the
88
commit time of the revision.
90
* Perhaps split command infrastructure from the actual command
93
* Cleaner support for negative boolean options like --no-recurse.
95
* Statcache should possibly map all file paths to / separators
97
* quotefn doubles all backslashes on Windows; this is probably not the
98
best thing to do. What would be a better way to safely represent
99
filenames? Perhaps we could doublequote things containing spaces,
100
on the principle that filenames containing quotes are unlikely?
101
Nice for humans; less good for machine parsing.
103
* Patches should probably use only forward slashes, even on Windows,
104
otherwise Unix patch can't apply them. (?)
106
* Branch.update_revisions() inefficiently fetches revisions from the
107
remote server twice; once to find out what text and inventory they
108
need and then again to actually get the thing. This is a bit
111
One complicating factor here is that we don't really want to have
112
revisions present in the revision-store until all their constituent
113
parts are also stored.
115
The basic problem is that RemoteBranch.get_revision() and similar
116
methods return object, but what we really want is the raw XML, which
117
can be popped into our own store. That needs to be refactored.
119
* ``bzr status FOO`` where foo is ignored should say so.
121
* ``bzr mkdir A...`` should just create and add A.
123
* Guard against repeatedly merging any particular patch.
130
* Merge revert patch.
132
* ``bzr mv`` that does either rename or move as in Unix.
134
* More efficient diff of only selected files. We should be able to
135
just get the id for the selected files, look up their location and
136
diff just those files. No need to traverse the entire inventories.
138
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
139
under that directory.
141
* Fix up Inventory objects to represent root object as an entry.
143
* Don't convert entire entry from ElementTree to an object when it is
144
read in, but rather wait until the program actually wants to know
147
* Extract changes from one revision to the next to a text form
148
suitable for transmission over email.
152
- Selected-file commit
154
- Impossible selected-file commit: adding things in non-versioned
155
directories, crossing renames, etc.
157
* Write a reproducible benchmark, perhaps importing various kernel versions.
159
* Directly import diffs! It seems a bit redundant to need to rescan
160
the directory to work out what files diff added/deleted/changed when
161
all the information is there in the diff in the first place.
162
Getting the exact behaviour for added/deleted subdirectories etc
165
At the very least we could run diffstat over the diff, or perhaps
166
read the status output from patch. Just knowing which files might
167
be modified would be enough to guide the add and commit.
169
Given this we might be able to import patches at 1/second or better.
171
* Get branch over http.
173
* Pull pure updates over http.
175
* revfile compression.
177
* Split inventory into per-directory files.
179
* Fix ignore file parsing:
181
- fnmatch is not the same as unix patterns
183
- perhaps add extended globs from rsh/rsync
185
- perhaps a pattern that matches only directories or non-directories
187
* Consider using Python logging library as well as/instead of
190
* Commands should give some progress indication by default.
192
- But quieten this with ``--silent``.
194
* Change to using gettext message localization.
196
* Make a clearer separation between internal and external bzrlib
197
interfaces. Make internal interfaces use protected names. Write at
198
least some documentation for those APIs, probably as docstrings.
200
Consider using ZopeInterface definitions for the external interface;
201
I think these are already used in PyBaz. They allow automatic
202
checking of the interface but may be unfamiliar to general Python
203
developers, so I'm not really keen.
205
* Commands to dump out all command help into a manpage or HTML file or
208
* Handle symlinks in the working directory; at the very least it
209
should be possible for them to be present and ignored/unknown
210
without causing assertion failures.
212
Eventually symlinks should be versioned.
214
* Allow init in a subdirectory to create a nested repository, but only
215
if the subdirectory is not already versioned. Perhaps also require
216
a ``--nested`` to protect against confusion.
220
* More test framework:
222
- Class that describes the state of a working tree so we can just
225
* There are too many methods on Branch() that really manipulate the
226
WorkingTree. They should be moved across.
228
Also there are some methods which are duplicated on Tree and
229
Inventory objects, and it should be made more clear which ones are
230
proxies and which ones behave differently, and how.
232
* Try using XSLT to add some formatting to REST-generated HTML. Or
233
maybe write a small Python program that specifies a header and foot
234
for the pages and calls into the docutils libraries.
236
* --format=xml for log, status and other commands.
238
* Attempting to explicitly add a file that's already added should give
239
a warning; however there should be no warning for directories (since
240
we scan for new children) or files encountered in a directory that's
243
* Better handling of possible collisions on case-losing filesystems;
244
make sure a single file does not get added twice under different
247
* Clean up XML inventory:
249
- Use nesting rather than parent_id pointers.
251
- Hold the ElementTree in memory in the Inventory object and work
252
directly on that, rather than converting into Python objects every
253
time it is read in. Probably still exposoe it through some kind of
254
object interface though, but perhaps that should just be a proxy
257
- Less special cases for the root directory.
259
* Perhaps inventories should remember the revision in which each file
260
was last changed, as well as its current state? This is a bit
261
redundant but might often be interested to know.
263
* stat cache should perhaps only stat files as necessary, rather than
264
doing them all up-front. On the other hand, that disallows the
265
opimization of stating them in inode order.
267
* It'd be nice to pipeline multiple HTTP requests. Often we can
268
predict what will be wanted in future: all revisions, or all texts
269
in a particular revision, etc.
271
urlgrabber's docs say they are working on batched downloads; we
272
could perhaps ride on that or just create a background thread (ew).
274
* Paranoid mode where we never trust SHA-1 matches.
276
* Don't commit if there are no changes unless forced.
278
* --dry-run mode for commit? (Or maybe just run with
279
check-command=false?)
281
* Generally, be a bit more verbose unless --silent is specified.
283
* Function that finds all changes to files under a given directory;
284
perhaps log should use this if a directory is given.
286
* XML attributes might have trouble with filenames containing \n and
287
\r. Do we really want to support this? I think perhaps not.
289
* Remember execute bits, so that exports will work OK.
291
* Unify smart_add and plain Branch.add(); perhaps smart_add should
292
just build a list of files to add and pass that to the regular add
295
* Function to list a directory, saying in which revision each file was
296
last modified. Useful for web and gui interfaces, and slow to
297
compute one file at a time.
299
* unittest is standard, but the results are kind of ugly; would be
300
nice to make it cleaner.
302
* Check locking is correct during merge-related operations.
304
* Perhaps attempts to get locks should timeout after some period of
305
time, or at least display a progress message.
307
* Split out upgrade functionality from check command into a separate
310
* Don't pass around command classes but rather pass objects. This'd
311
make it cleaner to construct objects wrapping external commands.
313
* Track all merged-in revisions in a versioned add-only metafile.
319
* Generate annotations from current file relative to previous
322
- Is it necessary to store any kind of annotation where data was
325
* Update revfile_ format and make it active:
327
- Texts should be identified by something keyed on the revision, not
328
an individual text-id. This is much more useful for annotate I
329
think; we want to map back to the revision that last changed it.
331
- Access revfile revisions through the Tree/Store classes.
333
- Check them from check commands.
337
.. _revfile: revfile.html
339
* Hooks for pre-commit, post-commit, etc.
341
Consider the security implications; probably should not enable hooks
342
for remotely-fetched branches by default.
344
* Pre-commit check. If this hook is defined, it needs to be handled
345
specially: create a temporary directory containing the tree as it
346
will be after the commit. This means excluding any ignored/unknown
347
files, and respecting selective commits. Run the pre-commit check
348
(e.g. compile and run test suite) in there.
350
Possibly this should be done by splitting the commit function into
351
several parts (under a single interface). It is already rather
352
large. Decomposition:
354
- find tree modifications and prepare in-memory inventory
356
- export that inventory to a temporary directory
358
- run the test in that temporary directory
360
- if that succeeded, continue to actually finish the commit
362
What should be done with the text of modified files while this is
363
underway? I don't think we want to count on holding them in memory
364
and we can't trust the working files to stay in one place so I
365
suppose we need to move them into the text store, or otherwise into
366
a temporary directory.
368
If the commit does not actually complete, we would rather the
369
content was not left behind in the stores.
373
* GUI (maybe in Python GTK+?)
375
* C library interface
377
* Expansion of $Id$ keywords within working files. Perhaps do this in
378
exports first as a simpler case because then we don't need to deal
379
with removing the tags on the way back in.
added
removed
TODO
