Current Trajectory
==================
-Now that we've finished the 0.31 release, we're working on 0.32, and
+Now that we've finished the 0.33 release, we're working on 0.34, and
although we're not certain which new features will be included, we're
considering:
+ - Migrating hashsplitting to C.
+
+ - Automatically splitting trees to avoid having to save large tree
+ objects for large directories even if only a few files have
+ changed or been added (e.g. maildirs).
+
+ - Moving all of the compoents of the index to sqlite. Right now the
+ main index is an mmapped file, and the hard link and metadata
+ databases are pickled. As a result the index isn't transactional
+ and suffers from bugs caused by "skew" across the components.
+
- Better VFS performance for large repositories (i.e. fuse, ls,
web...).
More specific ways to help
==========================
-Testing -- yes please.
+Testing -- yes please.
With respect to patches, bup development is handled via the mailing
list, and all patches should be sent to the list for review (see
./pytest test/int/test_git.py
./pytest test/ext/test-ftp
+If you have the xdist module installed, then you can specify its `-n`
+option to run the tests in parallel (e.g. `./pytest -nauto ...`), or
+you can specify `-j` to make, which will be translated to xdist with
+`-j` becoming `-nauto` and `-jN` becoming `-nN`.
+
Internal tests that test bup's code directly are located in test/int,
and external tests that test bup from the outside, typically by
running the executable, are located in test/ext.
In particular, we've been paying at least some attention to the bits
regarding Acked-by:, Reported-by:, Tested-by: and Reviewed-by:.
+
+<!--
+Local Variables:
+mode: markdown
+End:
+-->