Re: [Monotone-devel] Time to think about a release?

[Thomas Moschny]

On Tuesday 25 March 2008, Markus Schiltknecht wrote:
> Thomas Moschny wrote:
> > Would you mind adding some words to NEWS about this, and especially about
> > any positive (or negative?) impact this might have on the end user or on
> > clients using the automation interface? Will all or some of the locking
> > issues go away in 0.40?
>
> Thanks for the reminder, I will do -right after fixing the
> schema_migration test...
>
> For the end user, this change should not have any noticeable effect,
> except mtn being a tiny bit faster and the database taking somewhat less
> space. Every other difference in automate or locking behavior should be
> considered a bug. :-)

How can the changes in nvm.experiment.encapsulation make the database take 
less space?

And why would would you consider changes in the locking behavior a bug?

In fact, the current behavior is buggy (imho), because mtn acquires 
coarse-grained write-locks to the database, so e.g. concurrent access via 
automate and mtn serve is not possible. And to me it seemed the efforts in 
nvmee were part of the plan to overcome this issue.

Regards,
Thomas

-- 
Thomas Moschny  <address@hidden>

signature.asc
Description: This is a digitally signed message part.