X-Git-Url: https://arthur.barton.de/gitweb/?a=blobdiff_plain;f=HACKING;h=372bc732a5188e164e0b33f2d7a8a390e7d3d6d7;hb=51e0158c85a3519be1b3bc5ac4f1349f5010923c;hp=31f48a556336b133af5cfc46fa2ed0526ec97336;hpb=0144a07edc1a00b065bda208c36986b8201fb15a;p=bup.git diff --git a/HACKING b/HACKING index 31f48a5..372bc73 100644 --- a/HACKING +++ b/HACKING @@ -19,7 +19,7 @@ via email. 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.32 release, we're working on 0.33, and although we're not certain which new features will be included, we're considering: @@ -38,6 +38,8 @@ considering: - Support for alternate remote storage APIs. + - Discontinuing Python 2 work, excepting perhaps some bugfixes. + If you have the time and inclination, please help review patches posted to the list, or post your own. (See "ways to help" below.) @@ -45,7 +47,7 @@ posted to the list, or post your own. (See "ways to help" below.) 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 @@ -69,6 +71,11 @@ For example: ./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. @@ -135,3 +142,9 @@ ideas here aren't altogether terrible: In particular, we've been paying at least some attention to the bits regarding Acked-by:, Reported-by:, Tested-by: and Reviewed-by:. + +