[Monotone-devel] 0.17 "release candidate", last call for bugs...

[Nathaniel Smith]

Well, it's been a long time coming, but we're very close... as far as
I know, the currently available revision
    6f3b3b46b933acb2a0ffd59c21ce29125d1556f1
would make an acceptable 0.17.  Since it's been so long since the
last release, though, and since 0.17 is going to be a flag day, I'd
really like for it to be usable for people.  So, now would be a good
time to make sure it builds, passes its testsuite, your favorite nasty
bugs are fixed, etc...

Note that the above is the current head of the
net.venge.monotone.rebuild_tracking branch; this branch is not
compatible with any databases or netsync servers that are currently in
use.  This will all be in the release notes once I write them, but the
short version of getting your database into a form it will like is:
  # if you're using 0.16:
  $ monotone-0.16 --db=foo.db db dump | monotone-0.17 --db=test.db db load
  # if you've been tracking mainline and already switched to sqlite3:
  $ cp foo.db test.db
  # everyone:
  $ monotone-0.17 --db=test.db db migrate
  $ monotone-0.17 --db=test.db db rebuild

You can also run the testsuite with "make check", etc.

(I'd be curious just to know that the above migration stuff happens
without error, and any interesting messages printed during "rebuild",
like about optimizing out edges or splitting file histories.)

My hope is to release 0.17 in the next few days, as soon as I've had
time to write release notes and all that.  I'll do the x86 static
build and the debian unstable x86/source packages; volunteers for
other architectures, operating systems, distributions, etc., needed.

Cheers,
-- Nathaniel

-- 
In mathematics, it's not enough to read the words
you have to hear the music