Difference between revisions of "Policies/Minor Point Release Policy"

(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...')
 
(Replaced content with "{{Moved To Community}}")
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
KDE Provides minor point releases approximately every month after a major point release.
+
{{Moved To Community}}
−
 
 
−
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
 

Latest revision as of 18:28, 10 March 2016

This page is now on the community wiki.

Retrieved from "https://techbase.kde.org/index.php?title=Policies/Minor_Point_Release_Policy&oldid=87012"

This page was last edited on 10 March 2016, at 18:28. Content is available under Creative Commons License SA 4.0 unless otherwise noted.