Am Sonntag, 1. Dezember 2013, 19:04:11 schrieb Christian Boltz:
Am Sonntag, 1. Dezember 2013 schrieb Robert Schweikert:
problem with the staging model is that the "potentially
risky interactions" knowledge is an implicit set of interactions that
the staging tree managers happen to know. This is not expressed
anywhere and thus makes it difficult for other people to learn. We
have this problem today and from my point of view this will not be
resolved with more staging trees.
Except for "staging tree for everything" - but I'm quite sure we'll
overload OBS if we create a staging project for every typo fix in a
README file ;-)
I do not see the need for this actually. It is perfectly fine to run
the staging approach, but replace more then one package in it.
We may should have a staging project for collecting such small changes.
But we should release them altogether to Factory after validating it
with one rebuild (plus possible QA checks if we have some in future).
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org