Am Samstag, 4. August 2012, 11:34:20 schrieb Martin Schlander:
If patches are created upstream but did not get a review upstream yet, i.e. no "Ship it!", then they should not be added unless the submitter guarantees that he tracks the patch upstream, updating it and in case it gets rejected removing it from the repos. Since that's quite tedious to do I would prefer to simply not submit any upstream patch which did not get at "Ship it!" upstream yet.
That sounds like a lot of work and bureaucracy.
Tedious indeed, which is why I fear people just don't follow upstream patches after they submitted them to e.g. KDF. That's why I would like a simple and robust rule. Easy to follow, low risk of including patches/patch versions which never end-up in upstream code.
How about something managable like "stuff must exist in KDF for at least a week (or two?) before being linked from KR4x"
If a patch was accepted upstream, i.e. will be part of the next upstream release, it can go in. Having to wait for weeks before a crash is fixed does not sound sensible to me. Neither adding patches that could easily wait until the next upstream release. If a patch was not accepted upstream (yet), there is a reason for that, even if it is only that there was no review yet. Why would openSUSE's repos want unreviewed patches which might not even end-up in the upstream code and hence lead to confusion or openSUSE-specific regressions? Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org