[merge] tags in repository

[Martin Pool]

On 23 Jan 2007, Jelmer Vernooij <jelmer at samba.org> wrote:
> On Tue, 2007-01-23 at 11:50 +1100, Martin Pool wrote:
> >  * This adds them into the KnitRepository2 format.  I would like them to
> >    be in the default format for the next release, but I'm not sure if 
> >    all the changes in KnitRepository2 are in that class.
> Would it be a good idea to have a separate branch than bzr.dev that
> contained a new pending repository format that is still prone to
> changes? I notice there are a couple of things that are not being merged
> to bzr.dev at the moment just because they need a new repository format.
> It would be nice to be able to merge them and accumulate the changes for
> such a new format rather than block and have them in various places.

I think that we should have, in bzr.dev, a format called "experimental".
That format would be guaranteed to work in any particular revision, but
not to be compatible from one bzr release to the next, and not even have
any guarantee that it can be upgraded.  I think that would give us room
to play without requiring people to spend time making sure upgrades will
work, and without needing to make a commitment to long-term support
before it is merged at all.

We can then decide before a release candidate to promote some features
into a stable format.

Also repository.py is getting quite big and I'd like to split it
per-implementation.

-- 
Martin