Changes

Jump to navigation Jump to search
278 bytes added ,  12:23, 1 September 2011
Line 115: Line 115:  
And there are arguments against:
 
And there are arguments against:
 
* Some people might interpret the number 1.0 as indicating a higher level of maturity than what the developers feel
 
* Some people might interpret the number 1.0 as indicating a higher level of maturity than what the developers feel
 +
* Some developers have very specific ideas about what should be included in Sugar-1.0, even if development of such items is barely even on the horizon
 
* Some people want a much longer lead-up time to Sugar-1.0 so that the API can be refined/reworked/perfected
 
* Some people want a much longer lead-up time to Sugar-1.0 so that the API can be refined/reworked/perfected
    
Tomeu, Simon and Marco agreed that the 1.0 version number could be used here, and communicated in a slightly different sense: "we are really still in the first iteration and 1.0 will be when that first iteration reaches maturity, without big changes in the API. After 1.0 we can start working on what will be one day 2.0 which should be the second iteration of Sugar, hopefully using what we have learned during these years."
 
Tomeu, Simon and Marco agreed that the 1.0 version number could be used here, and communicated in a slightly different sense: "we are really still in the first iteration and 1.0 will be when that first iteration reaches maturity, without big changes in the API. After 1.0 we can start working on what will be one day 2.0 which should be the second iteration of Sugar, hopefully using what we have learned during these years."
   −
The migration of sugar-toolkit, sugar, datastore, etc, is likely to take more than 1 release cycle, but the above scheme can still apply. When each component is ported to GTK3, it would then pick up the 1.0 tag. For example, the first major release that includes any GTK3 may well include sugar-toolkit-1.0 (GTK3 ported) alongside sugar-datastore-0.96 (not yet ported).
+
However, current Sugar developers feel strongly that the changes described here are not significant to warrant a major version bump and have specific ideas about what should be included in a 1.0 release. Therefore, in the interest of being slightly less intrusive, this feature does not ultimately propose a version numbering change - it is planned that sugar-toolkit-0.96 will be released as the first with GTK3 support, and once we reach sugar-0.98, the next releases will be 0.100, 0.102, etc.
    
=== Retaining the 'sugar' module name ===
 
=== Retaining the 'sugar' module name ===
105

edits

Navigation menu