test-web: mark as unresolved with respect to python 3

[bup.git] / HACKING

diff --git a/HACKING b/HACKING
index 6ecab7ea3bd29c72e909effcd78e7c246f73ac0f..6dc10b19aa95319b5ef804e7757fa03b3924e19f 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -19,27 +19,26 @@ via email.
 Current Trajectory
 ==================
 
-Now that we've finished the 0.27 release, we're working on 0.28, 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 likely candidates:
 
-  - Support for rm/gc.
-
-  - 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...).
 
+  - Better VFS caching.
+
+  - Index improvements.
+
   - Incremental indexing via inotify.
 
   - Smarter (and quieter) handling of cross-filesystem metadata.
 
-  - Support for more general purpose push/pull of branches, saves, and
-    tags between repositories.  (See the bup-get patch series.)
-
 If you have the time and inclination, please help review patches
 posted to the list, or post your own.  (See "ways to help" below.)
 
@@ -59,6 +58,24 @@ 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
 ==================
 
@@ -96,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.