On 01/19/2017 03:59 AM, Friedrich W. H. Kossebau wrote: > Given this is a policy affecting all of the KDE projects, please first > propose > it officially in a separate own thread, with a proper subject. Perhaps even > on > kde-community, as kde-core-devel might not be read by many, given it used to > be focussed on kdelibs/core apps. Even people reading kde-core-devel might > have missed it, as this thread here started to become heated and long, so > most > free time contributors might not have invested time into reading more than > the > first.
Agreed - I'll be writing a separate mail to k-c-d and kde-devel very soon. More communication is almost always better! > Some feedback on the policy itself: > "Dependency changes for software covered by the CI system should be submitted > through code review" > -> I would propose to additionally recommend contacting sysadmin as soon as > one knows that a new dependency is coming up, not only first at the time the > official review request is made. That should give sysadmin some more time in > advance to handle the needed new dependency in CI, and perhaps also give > feedback on issues. > Ideally it might even result in the new dependency already being available at > the time of the review request, so if the review itself is done quickly, CI > does not block the merge. > > IIRC this would also reflect what has been done now and then :) Sounds good, I'll add a small bit. > Cheers > Friedrich Cheers, Eike
