Re: [Chicken-hackers] Re: repository branching

[Alejandro Forero Cuervo]

> > As an end user I don't want new features showing up in old eggs. The
> > old egg should be exactly as it was when it was released baring
> > perhaps serious bug fixes. The old releases are kept around to keep
> > things *stable* for those who cannot change for some reason. Now, it
> > should also be possible to install any version of an egg on an old
> > version of chicken with a little manual intervention. 
> 
> No one is proposing that new features show up in old eggs.  Old eggs,
> once released, will never change.  Even serious bug fixes result in a
> new release, not an update to an old egg.  If you don't want upgrades,
> do not update your eggs.  Felix did not change this nor are we
> proposing that it is changed.

Ok, actually it can be argued that the releases/N change does make it
possible for new features to start showing up in old eggs, given that
you can one day release stream-wiki 1.12 in
releases/2/stream-wiki/tags/1.12 and then, one month later, release
stream-wiki 1.12 in releases/3/stream-wiki/tags/1.12, with a
completely different codebase (or the same thing swapping the /3/ and
the /2/).

The fact that the new system supports this is only one of the multiple
reasons why I think this change breaks chicken-eggs enough that I'm
right now seriously looking for other systems to move my code from
chicken-eggs into (with one option being simply just copying it all
into Svnwiki).

Alejo.
http://azul.freaks-unidos.net/