Hi, In the plasma team, while working on the frameworks port, we run into "unexpected changes" quite often. In most cases, something in kdelibs[frameworks] or in e-c-m changed, and we only find out the hard way, and then have to sift through git logs, patches, cmake files etc. to sort it out and make-it-build again. That causes quite some work for us, much of which can I think be avoided.
Here's a couple of ways how you could make us happier: Whenever you apply a change in kdelibs[frameworks] that needs other components adopted: - do a clean build / install of kdelibs and plasma-frameworks - build of plasma-framework and make sure it at least builds and links - send an email to frameworks-devel, telling us what needs changing (that at least saves us detective work) - CCMAIL frameworks-devel on a commit that shows what needs changing (maybe from another piece, so we have an example to go by) - ping Aaron, Marco or me on IRC and tell us what to change (so at least *someone* knows it) (In order of preference. Any of the above is likely to save us a lot of work.) Also, please pay close attention to jenkins kdelibs *AND* plasma-frameworks builds. It doesn't catch everything (IME, not sure why), but the more, the merrier: kdelibs: http://build.kde.org/job/kdelibs_frameworks_qt5/ plasma: http://build.kde.org/job/plasma-framework_master_qt5/ I'll ask Ben to also send failure emails of plasma-framework to this list, so you've got even less an excuse. :) Tip: You can add a news feed Plasma widget to your desktop showing the above as feeds, no excuse to not check jenkins! Thanks in advance, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
