release status - land new features before monday

[Ian Clatworthy]

Martin Pool wrote:
> On 4/12/07, John Arbash Meinel <john at arbash-meinel.com> wrote:
>> But you could write a plugin which supplies:
>>
>> bzrlib.bzrdir.format_registry.register_metadir('wt3-tags',
>>     'bzrlib.repofmt.knitrepo.RepositoryFormatKnit1',
>>     help='Combination of <0.15 WT and 0.15 Branch',
>>     branch_format='bzrlib.branch.BzrBranchFormat6',
>>     tree_format='bzrlib.workingtree.WorkingTreeFormat3',
>>     )
>>
>> And then you can do "bzr init --wt3-tags" and get what you want.
>
> I don't mind if someone wants to add that format into bzr.dev.  This
> is the kind of situation where being able to set the three object
> formats independently would be useful (as a stopgap, obviously we do
> not want people to have to do that.)
>
I can imagine setting the three formats separately being useful in the 
longer term as well. Like most of it's peers, Bazaar is useful out of 
the box for source code. But people being people and Bazaar being open 
source with "pluggable" formats, it will get stretched in ways we can't 
predict right now, e.g. large binary files, XML databases, CMS backends, 
text files with domain specific semantics that enable optimisations we 
could never make in the general case.

Is it worth having a --custom option that looks up logical names in a 
registry to get the details above? By registry, a local file would do me 
(bazaar.conf say) though I'd like the syntax to support remote lookup 
down the track.

Ian C.