"bzr branch" and repository.

[David Allouche]

On Mon, 2006-05-01 at 08:14 +1000, Robert Collins wrote:
> On Sat, 2006-04-22 at 07:45 +0200, Matthieu Moy wrote:
> > David Allouche <david at allouche.net> writes:
> > 
> > > For example: Arthur uses bzr-0.7 and publishes frobo.dev on his website.
> > > Bruce uses bzr.dev and has one big repository with everything, he
> > > branches frobo.dev as frobo.br, hack a bit on it, and ask Arthur to
> > > merge. Arthur cannot read frobo.br.
> > 
> > I don't think bzr is already mature enough to encourrage people to
> > stay with an old version. If Bruce wants to make his archive
> > accessible to Artur, he'd better either put it outside his repository
> > or tell him "Hey, man, why don't you upgrade to 0.8 ?" (which I would
> > find inacceptable in the post-1.0 phase, for sure).
> 
> Its not about encouraging people to stay with an old version. Its about
> not forcing a watershed on projects where one person chooses to upgrade.

I do not see how changing that behaviour would force a watershed.

If a user upgrades and publishes branches in a new format, that's not
readable by the rest of the project, it's a social problem. If the rest
of the project wants to stay with 0.7, that person can make a minor
setup change to preserve compatibility.

-- 
                                                            -- ddaa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060504/c2e122e5/attachment.pgp