D22973: docs: introduce commit message guideline
Vlad Zagorodniy <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kwin |
|---|---|
| Message-ID | <[email protected]> |
zzag added inline comments. INLINE COMMENTS > romangg wrote in HACKING.md:161 > The "Breaking Changes" was copied over from the Angular guide lines, but maybe we should remove it here. For once because we don't really have defined what breaking changes are in KWin. Is a change to the Effects API/ABI a breaking change? Is a behavioral change for users one? We can drop this section as we check libkwineffects API version. > Is a change to the Effects API/ABI a breaking change? Third-party effects need to be recompiled if API version of libkwineffects is bumped. It's a good idea to compile your third-party effect against each major release of KWin. REPOSITORY R108 KWin REVISION DETAIL https://phabricator.kde.org/D22973 To: romangg, #kwin Cc: davidedmundson, yurchor, anthonyfieroni, zzag, ngraham, kwin, LeGast00n, sbergeron, jraleigh, fbampaloukas, GB_2, mkulinski, ragreen, jackyalcine, Pitel, iodelay, crozbo, bwowk, ZrenBot, alexeymin, himcesjf, lesliezhai, ali-mohamed, hardening, romangg, jensreuterberg, abetts, sebas, apol, mart