[RFC] new format 1.12 (1.11?) enabling EOL & filtered views

[Ian Clatworthy]

John Arbash Meinel wrote:
> Ian Clatworthy wrote:

>> To be more precise, I'd like to decouple the introduction of this
>> from the CHK format related work by doing the following:
> 
>> 1. Adding 2 new experimental formats called 1.12preview and
>>    1.12preview-rich-root respectively. These formats will be
>>    the same as their 1.9 counterparts except that the WT will
>>    be (the new) WT5, not WT4.
> 
> The standard way of introducing a format that is "experimental" is to
> put it into the "--development" series. Say as a "--development5"
> format. I don't have a strict problem with your naming, though I may
> have gone 1.12-preview...

I'm certainly aware of the --development path. In this case, I think
there's very little development to do format wise: the new format
is simply a marker that certain capabilities are enabled. I'm also
wary about confusing people, e.g. using the name development5
implicitly suggests (to me at least) something that builds on
development4 and that isn't the case here.

>> 2. Resubmitting the content filtering patch so that it will
>>    only work with WT5 trees.
> 
>> 3. Submitting my filtered views patch.
> 
> Technically the functionality should land before the format, so that we
> don't have a someone running a bzr release that doesn't have the
> functionality, but does have the format.
> 
> That said, --development seems like a fine place to break compatibility
> *inside* of a release, so I don't think it has to happen in that order.
> I also realize that any manual testing is hard to do if you don't have a
> format that lets you do the testing :).

Precisely. :-) The new formats will be marked as experimental until
the functionality lands so I think the ordering is ok. We certainly
can't land the functionality before the format in any way I can see.

Ian C.