On Tue, Feb 23, 2010 at 09:00:14AM +0100, Sylvain Thénault wrote: > ... IMO this is way too much pain. We've hard time to keep test of the > *currnently developped* version to green. IMO we should simply keep working > on stable / default and to have those two branches coherent across packages > and green tests. That's it (and already a lot of work).
Even this can not work. You can not prevent stable on logilab common from evolving faster than stable on cubicweb for example. "stable branch" has a local meaning and in the current configuration of our test bot, we use it as if it meant "stable distribution" as it is used in Debian for example. I gave more thought to the problem since I wrote its description yesterday and came up to the conclusion that the only option is to define a "cubicweb distribution" as a list of versions. The execution will not depend on a vcs branch any more, but on a "distribution". When things are proved to work with the rest of the distribution, we can manually update the distribution to include them. -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
