Talk:Policies

Jump to: navigation, search

Does it make sense to add a binary compatibility policy? I know that the libs are compatible until KDE 5 but this "Binary compatibility is not required. i18n string changes are allowed" on Schedules/KDE4/4.1_Release_Schedule was confusing until I found "Workspace interface freeze (source and binary compatibility until KDE 4.1)" on Schedules/KDE4/4.0_Release_Schedule. Apparently there are 2 binary compatibility guarantees. One for the libs which lasts over the entire 4 series and one for the workspace which lasts from 4.0 to 4.1 (and presumably then 4.1 to 4.2)

--Cbs

Contents

Thread titleRepliesLast modified
Git commit policy006:15, 11 September 2012

Git commit policy

With the recent move to Git, I assume there should be a policy for Git contributions. Currently there's only the SVN commit policy.

Mechanical snail (talk)06:15, 11 September 2012

This page was last modified on 4 February 2008, at 17:01. This page has been accessed 6,028 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal