Current Trajectory
==================
-Now that we've finished the 0.29.2 release, we're working on 0.30, and
+Now that we've finished the 0.29.3 release, we're working on 0.30, and
although we're not certain which new features will be included, here
are likely candidates:
Notable changes introduced by a release
=======================================
+ - <a href="note/0.29.3-from-0.29.2.md">Changes in 0.29.3 as compared to 0.29.2</a>
- <a href="note/0.29.2-from-0.29.1.md">Changes in 0.29.2 as compared to 0.29.1</a>
- <a href="note/0.29.1-from-0.29.md">Changes in 0.29.1 as compared to 0.29</a>
- <a href="note/0.29-from-0.28.1.md">Changes in 0.29 as compared to 0.28.1</a>
--- /dev/null
+
+Notable changes in 0.29.3 as compared to 0.29.2
+===============================================
+
+General
+-------
+
+* Newer versions of par2 can process in parallel using multiple
+ threads/cores, and they do so automatically. This ends up competing
+ with `bup fsck`s own parallelism, enabled by `-j`, in such a way
+ that the command can actually run much *slower* (and be much more
+ expensive) than it would have been with no parallelism at all.
+
+ When appropriate `bup fsck` now disables par2's competing
+ parallelism (via its `-t1` option) to avoid the contention.
+
+Build system
+------------
+
+* test-prune-older should no longer be disturbed by git's automatic
+ background gc.
+
+Thanks to (at least)
+====================
+
+Rob Browning and Robert Edmonds