[Monotone-devel] 0.10 released

[graydon hoare]

hi,

I've released (well, shoved) a version I'm calling 0.10 to the net. this 
version is about a month late, and probably has some warts (eg. still 
doesn't build against boost 1.31.x) but it *does* include an immature, 
but seemingly "working" version of the stateless "netsync" protocol.

I have a netsync server running on off.net. it is running under 
supervise, so even if you manage to knock it over (which I hope is less 
trivial than it was) it should restart immediately. I'll watch the logs 
to see how well it handles being out on the Big Scary Internet. 
hopefully all will be ok.

if you want to talk to it you will need to import this public key.

[pubkey address@hidden
MIGdMA0GCSqGSIb3DQEBAQUAA4GLADCBhwKBgQCkVU7BYI5bRRJmkJc8gomO9WdTTGG10Lmh
PdAEqD6sSdsMkTC9okfsQQ8obE+GODrFa70fX5PJNevNoE+Ryxzu+xtJjmuR2tYTeRNwNa0F
dIo/QLteQ4Vwh5162It1kPhLKb1Ki62ZG8aw6ATS4GQVJPci2g1lpn1RG0Z+fFdFJQIBEQ==
[end]

I am being intentionally obtuse in not making this part of the current 
self-hosting page. I would like some feedback and experimentation with 
netsync from patient people who are already familliar with monotone, not 
newcomers attracted from the release announcement. I included just 
barely enough documentation to cover how to use netsync commands. once 
you've imported this key, built a new monotone and migrated to the new 
schema I would recommend you try:

  $ monotone --key="" pull off.net net.venge.monotone

that should hook you up with the newest-latest, anonymously, and 
there'll be no more need to use the depot. if it doesn't, or it crashes, 
or hangs, or goes funny, please just send me a private mail with a log. 
 the protocol is far from bullet proof yet. if you want write access to 
that server obviously I'll need a public key from you. also make sure 
you put a hook entry of the following sort in your .monotonerc so that 
the server's data can be written to your database during the pull:

function get_netsync_write_permitted(collection, id)
        return (id == "address@hidden")
end

there are a number of other changes -- test improvements and small 
bugfixes -- and a fleshing out of the QA stuff. notably: you can now 
approve or disapprove of an edge in the ancestry graph and have it 
*mean* something, as wel as post test results from an autotester key and 
have it considered in future updates.

anyways I'm a little pooped so I'm going to bed.

-graydon