On 04/02/12 17:13, Kevin Krammer wrote:
On Monday, 2012-04-02, John Woodhouse wrote:What would be of more interest to many is pure bug fix releases rather than new features. I for instance am running Platform Version 4.6.00 (4.6.0) "release 6"That's the first release of the 4.6 series, which itself is one of the minor releases so it was allowed to have new features. Of course new features being allowes doesn't mean some were added or added in the sense of new functionality [1]. For example IIRC the current release series (4.8.x) is a "no features added" cycle for KDE Platform but I think KDE Workspaces got some. This, btw, also shows one of the problems of addressing the summary of all KDE products with a single name (currently "KDE SC"), since different products might have had different focus for a certain period. Cheers, Kevin [1] at the developer level things like restructuring are also counted as features, i.e. usually not allowed in update/patch releases. So it is actually more about how much can be changed and where (application code vs. library code). Sometimes user level features are a for-free consequence of a change like that, e.g. a change in image loading library because the current one resulted in too many bugs, can result in more formats being supported without that being the reason for the change. So 'feature release' may mean (apart form including absolutely new features) - 1) Restructuring the code (better management). 2) New backend or changed backend which may increase or decrease bugs. And bug fixes mean fixing small time bugs in library or directly in the app. |
___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
