Re: [Monotone-devel] Merging branch to allow duplicate key names, have certs use key hash

[hendrik]

On Sun, Aug 23, 2009 at 07:43:04AM +0200, Richard Levitte wrote:
> In message <address@hidden> on Thu, 20 Aug 2009 19:37:08 -0500, Timothy 
> Brownawell <address@hidden> said:
> 
> tbrownaw> On Fri, 2009-08-14 at 05:04 +0000, Timothy Brownawell wrote:
> tbrownaw> > I think branch net.venge.monotone.keys-by-hash is ready now.
> tbrownaw> > 
> tbrownaw> > The central change is that certs contain a key hash
> tbrownaw> > instead of a key name, to get rid of the problem with key
> tbrownaw> > collisions.
> tbrownaw> 
> tbrownaw> > This does require a netsync flag day, because certs on the
> tbrownaw> > wire contain a key hash instead of a key name now (just
> tbrownaw> > like certs in the db).
> tbrownaw> 
> tbrownaw> This is merged now.
> 
> Cool!
> 
> I wonder, what do you propose for a flag day for our repository?
> (and lets not forget to announce it clearly on http://monotone.ca/ and
> to make sure there's ample time for people to adapt, rebuild, yada
> yada yada)

Since it seems to be a flag day for the netsync protocol, and not for 
the database format (have I got this wrong) it would be possible to set 
up two monotone servers (one for the old and one for the new 
protocol) on a machine with two IP numbers, both operating on the very 
same copy of the data base .... no.  the server locks the data base, 
doesn't it.

Then have two servers for the general public to use during transition, 
and during that time, someone, somewhere, regularly syncs one local copy 
with each server (using a different version on monotone to access 
each server).

Then there will be a transition period of parallel operation, during 
which users can sync and rebuild their monotones at leisure.

-- hendrik