CI Requirements - Lessons Not Learnt?

Sandro KnauƟ sknauss at kde.org
Sat Jan 7 16:18:46 GMT 2017


Hey,

> how about some simple rule like "new dependencies every first of the month",
> and 1 week notice. For the developer this would mean in the worst case 5
> weeks waiting, which is probably quite a lot.

I think this is not necessary. Because sysadmins can comment the dependency 
bump. I think Ben already said what is important from sysadmins side: 
* Inform the sysadmins as early as possible, that you plan to bump deps
* The sysadmins will react within some days
* If the update of deps is something that takes longer sysadmin will tell you 
this, than you still can decide not to wait for CI and make your builds RED on 
CI.

The main thing I learned from the QtWebEngine debacle is, that you should NOT 
see the CI-team as something, that work out things after they happen. Just 
include them into your planning as well. They are people and are happy to get 
mail from you, what you plan for the next release.

Best Regards,

sandro





More information about the kde-core-devel mailing list