X-Git-Url: https://arthur.barton.de/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=HACKING;h=6dc10b19aa95319b5ef804e7757fa03b3924e19f;hb=9fc0171c58dd467586f70251228a39a486d35673;hp=d2edcc16ab05aa895ac14290d50db50b8356f07f;hpb=c16fd3fc28fac913bb8c42560de58bf61ed04922;p=bup.git

diff --git a/HACKING b/HACKING
index d2edcc1..6dc10b1 100644
--- a/HACKING
+++ b/HACKING
@@ -19,19 +19,23 @@ via email.
 Current Trajectory
 ==================
 
-Now that we've finished the 0.26 release, we're working on 0.27, and
+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 some possible candidates:
+are likely candidates:
 
-  - Support for transferring saves between repositories and rewriting
-    branches.
+  - 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...).
 
-  - Incremental indexing via inotify.
+  - Better VFS caching.
 
-  - Support for rm/gc.
+  - Index improvements.
+
+  - Incremental indexing via inotify.
 
   - Smarter (and quieter) handling of cross-filesystem metadata.
 
@@ -54,13 +58,31 @@ incorporating it into master, so reviews are an important way to help.
 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
 
@@ -91,7 +113,7 @@ Of course, unless your machine is set up to handle outgoing mail
 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.