On 08/17/2015 04:06 PM, Dimstar / Dominique Leuenberger wrote:
On Sat, 2015-08-15 at 16:59 +0200, Bernhard Voelker wrote:
On 08/14/2015 04:20 PM, Dominique Leuenberger / DimStar wrote: I've incidentally followed that growth ... and I'm wondering if "adding packages until no errors" is the fastest strategy?
It is to a certain point - then we generally start splitting stuff up again.
Staging:A started with ~5-8 packages 25 days ago. As there were some errors, other packages with fixes got added - now we're at 47 packages. Wouldn't it have been easier at some point to move some packages out for a while, thus splitting the problem?
If we'd not add the fixes to the same staging directly, the fix would first have to go through any other staing, be accepted into factory and the the first staging be completely rebased (stagings are not building against 'openSUSE:Factory', but contain frozen links to a 'snapshot in openSUSE:Factory'; so fixes do not auto-propagate).
I see, thanks. I just thought that it might be easier to move packages out into other staging projects which are "supposedly highly unlikely to be related to current problems", thus keeping the problematic staging project small and concentrated to the origin of the problem and its (and only its) fixes. Maybe the world is not ideal. ;-)
In some cases it's over-eager devs causing some more delays (like, superseding a request when a staging is almost ready.. meaning we have to redo the integration test with the new submission).
BTW: why is it that some of the original requests are regularly superseeded by a new request with the same content by factory-maintainer, e.g. 318007 superseeding 317472? Does this require such double work? Thanks & have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org