Am 04.12.2013 18:34, schrieb Adrian Schröter:
Am Montag, 2. Dezember 2013, 13:38:52 schrieb Stephan Kulow:
On 02.12.2013 13:14, Adrian Schröter wrote:
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).
That sounds like a very sensible thing to do. I wonder how to manage it though. Any ideas?
we could start with creating a staging project for large submissions like entire KDE update.
And then have some collection projects, where we collect everything, which did not fit somewhere else for, let's say 2 weeks. After 2 weeks we do open the next staging project and continue to fix the former one until it settles.
What do you think?
I think that there is a lot to fix and enhance before we can handle it and discuss. E.g. I have no way to see if openSUSE:Factory:Staging:NoFam already contains changes or if its pure IMO we basically need to find out what problems are common to all models and start hacking. Once we're there, we can test different scenario. The models will only be as good as the tools to support them. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org