This week goes mostly to Red Hat --- I need to get a GDB release together for a customer.
However, I think I've figured out how to present a pretty nice interface in the Subversion filesystem library for building transactions. A transaction will behave just like a revision: it's a directory tree, which you can browse using the normal filesystem API. However, unlike a revision's tree, which is permanent and unchanging, a transaction's tree is mutable --- you can use additional functions to create, delete and modify nodes as you please. When you've munged the tree to your satisfaction, you can commit the transaction; if there are no conflicts, the transaction's tree becomes a new revision of the filesystem.
This will require some fancy logic, mostly to conceal the sharing of nodes between a transaction and extant, committed revisions, but it should make the interface consistent and easy to learn. And hopefully make it simpler to implement WebDAV's `activities' on top of the Subversion filesystem.