Current Trajectory
==================
-Now that we've finished the 0.25 release, we're working on 0.26, and
-although we're not certain which new features will eventually be
-included, here are some possible candidates:
+Now that we've finished the 0.30 release, we're working on 0.31, and
+although we're not certain which new features will be included, here
+are likely candidates:
+
+ - Accommodation for the upcoming demise of Python 2, most likely via
+ support for Python 3.
+
+and these are also under consideration:
+
+ - Better VFS performance for large repositories (i.e. fuse, ls,
+ web...).
+
+ - Better VFS caching.
+
+ - Index improvements.
+
+ - Incremental indexing via inotify.
- - Support for rm/gc.
- - Support for remote (push and/or pull) restore.
- - Support for some kind of push/pull.
- Smarter (and quieter) handling of cross-filesystem metadata.
If you have the time and inclination, please help review patches
We also love a good "Tested-by:" -- the more the merrier.
+Testing
+=======
+
+You can run the test suite much more quickly via "make -j test" (as
+compared to "make test"), at the expense of slightly more confusing
+output (interleaved parallel test output), and inaccurate intermediate
+success/failure counts, but the final counts displayed should be
+correct.
+
+Individual non-Python tests can be run via "./wvtest run t/TEST" and
+if you'd like to see all of the test output, you can omit the wvtest
+run wrapper: "t/TEST"
+
+Individual Python tests can be run via "./wvtest run ./wvtest.py
+lib/bup/t/TEST", and as above, you can see all the output by omitting
+the wvtest run wrapper like this: "./wvtest.py lib/bup/t/TEST"
+
+
Submitting patches
==================
As mentioned, all patches should be posted to the mailing list for
review, and must be "signed off" by the author before official
inclusion (see ./SIGNED-OFF-BY). You can create a "signed off" set of
-patches in ./pending, ready for submission to the list, like this:
+patches in ./patches, ready for submission to the list, like this:
git format-patch -s -o patches origin/master
locally, you may need to configure git to be able to send mail. See
git-send-email(1) for further details.
-Oh, and we do have a ./CODING-STYLE, hobgoblins and all, though don't
+Oh, and we do have a ./CODINGSTYLE, hobgoblins and all, though don't
let that scare you off. We're not all that fierce.