[SCM] Samba Shared Repository - branch master updated

[Jeremy Allison]

On Mon, Jul 05, 2010 at 09:50:38AM -0400, simo wrote:
> 
> As far as I know we haven't decided about such a policy, but now that
> you better described the issue, I wonder if we should discuss if such a
> policy makes sense and if we should try to adopt one.

Not for this kind of case IMHO.

> But before even thinking of a database format compatibility rule we need
> to understand if we can achieve this goal of allowing rolling upgrades
> between one major version and the next. If we can't for other reasons
> that go beyond the mere database format, then it doesn't make sense to
> try to keep the db formats stable either.

I don't think allowing such rolling updates is possible, and
still allow us to add the features needed to keep Samba (non-clustered)
moving forward in a timely fashion.

> However assuming we do not keep DB formats stable, what will happen if
> someone tries to join a new samba version to a CTDB cluster ?
> Will it warn something in the logs and shutdown itself ? Or will it try
> to write database entries and compromise the functionality of all other
> nodes ? Or is there some other mechanism that will prevent harm in any
> way ?

An error message sounds good :-).

Jeremy.