Smart server plans for 1.7: effort tests, single RPC for branch opening, server-side autopacking.

[Talden]

>  * server-side autopacking.  I previously sent a hackish (and buggy) patch as an
>   RFC; I think it shouldn't be too hard to polish this.  It's an interim
>   solution (long term a single "Repository.insert_revisions" verb would be
>   better than manipulating pack files directly), but it's a cheap improvement.

This is a big one for me...

We've got a plan to move from CVS to Subversion and with all the
scripting for migration, reorganisation and testing I used bazaar to
track my own work - and as a subversive little side-effect had two of
the dev managers using it to track and contribute to my work... They
loved it until, on a slow link from home they start seeing 1-5KB
commits back to the server from checkouts (over bzr://...) producing
15-30minute repacking on the server (which, with no progress
indication results in "It's hung... CTRL-C" responses from these
users).

Suddenly Bazaar is 'too immature for serious consideration'... It
doesn't take much to sour an impression of a tool and these are
definitely the wrong people to let see any negatives so soon...

I hope, with Bazaars stellar rate of improvement (new indexes,
compression, server-side repacking, EOL/keywords support, tortoisebzr
support, numerous performance tweaks, eventual copy-with-history
support, ...) that I can show them that Subversion is just the
stepping stone to something much better.

--
Talden