[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Re: Flag day

From: Timothy Brownawell
Subject: [Monotone-devel] Re: Flag day
Date: Mon, 26 Feb 2007 17:59:23 -0600

On Tue, 2007-02-27 at 09:36 +1100, William Uther wrote:
> On 26/02/2007, at 6:54 PM, Paul Crowley wrote:
> > Monotone has a flag day coming up in any case, because of the move  
> > away from SHA-1.  Graydon (rightly) wants to change the certificate  
> > format; since that's also a flag day event that should probably be  
> > done on the same day.  We should move towards policy-named branches  
> > at the same time.
> I've got some netsync changes I'd like to make:
>    - treat unkown keys as anonymous connections
>    - auto fallback from 'sync' to just 'pull' if that's all you have  
> perms for

Netsync needs a bit more of an overhaul than that. A couple of things
off the top of my head are:
        1 a better refinement algorithm for revisions (to avoid the case
          where the merkle tries don't cover all relevant revisions, as
          can happen with propagates and very restrictive include
        2 automate commands available through the same mechanism as
        3 decoupling authentication from the sync part of the network
          protocol, because we need it for both the netsync part and
          the automate part
        4 allow different versions of the protocols to be requested,
          such that netsync upgrades don't have to be done all at once

> Is this the sort of thing to go in the flag day too?  Or is a netsync  
> change much less of an issue?

A netsync change is slightly less of an issue, in that it's possible
(but annoying) to not make everyone upgrade together. Basically, you run
a server on the new version and one on the old version, and have an old
and a new client alternate syncing a shared db to each server.


Free (experimental) public monotone hosting:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]