Policies/Minor Point Release Policy

From KDE Community Wiki
< Policies
Revision as of 11:50, 27 February 2011 by Albert Astals Cid (talk | contribs) (Created page with 'KDE Provides minor point releases approximately every month after a major point release. As stable releases these are recommended to a wide user base who expect a high degree of...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

KDE Provides minor point releases approximately every month after a major point release.

As stable releases these are recommended to a wide user base who expect a high degree of stability. Changes should therefore be verifiable, reliable and regression free.

These releases must only contain:

  • Severe bugs: security vulnerabilities, severe regressions from previous releases, data loss bugs
  • Fixes to bugs which are easy to verify
  • Updated translations
  • Updated manuals

They must not contain:

  • API changes in public libraries
  • New strings

In case you need absolutely new API or new strings to fix a important bug, approval from the relevant teams is needed.

  • For API changes in public libraries you need the approval of kde-core-devel
  • For new strings you need the approval of kde-i18n-doc
Retrieved from "https://community.kde.org/index.php?title=Policies/Minor_Point_Release_Policy&oldid=47704"