Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
releng:release-model [2009/08/16 18:03] – created jannisreleng:release-model [2010/10/02 17:26] – external edit 127.0.0.1
Line 40: Line 40:
   * xfwm4   * xfwm4
  
-All core components of the Xfce desktop have to adhere to the release policy defined in this document.+All core components of the Xfce desktop must adhere to the release policy defined in this document.
  
 ==== Essential Dependencies ==== ==== Essential Dependencies ====
Line 99: Line 99:
   - Write release notes   - Write release notes
   - Write release announcements   - Write release announcements
 +  - Create Bugzilla tags
   - Approve fixes of blocker bugs during code freeze   - Approve fixes of blocker bugs during code freeze
  
Line 104: Line 105:
  
   - Update the website(s)   - Update the website(s)
-  - Make sure API documentation is up to date +  - Help the release manager with his tasks
-  - Create bugzilla tags +
-  - Help the release manager+
  
 **QA Official** **QA Official**
Line 121: Line 120:
   - Write ChangeLogs and update NEWS files   - Write ChangeLogs and update NEWS files
   - Write component-specific release announcements   - Write component-specific release announcements
 +  - Create Bugzilla tags for their releases
 +  - Make sure API documentation is up to date
  
 === Dependency Freeze === === Dependency Freeze ===
Line 155: Line 156:
  
 Development releases usually give a feature preview for the next stable release.  Development releases usually give a feature preview for the next stable release. 
-They have to follow the X.Y.Z versioning format, where Y is an odd number (e.g. +They must follow the X.Y.Z versioning format, where Y is an odd number (e.g. 
 xfwm4-4.7.3 or thunar-1.3.10).  xfwm4-4.7.3 or thunar-1.3.10). 
  
Line 162: Line 163:
 of the SVN revision versioning we had in the past. If component A depends on a  of the SVN revision versioning we had in the past. If component A depends on a 
 new feature in component B, A may only be released if there is a development  new feature in component B, A may only be released if there is a development 
-release of B shipping this feature. For this to work, libtool versions have to +release of B shipping this feature. For this to work, libtool versions must 
 be updated properly with every development release. be updated properly with every development release.
  
Line 296: Line 297:
  
 There may be no API/ABI changes in maintenance releases compared to the corresponding final release  There may be no API/ABI changes in maintenance releases compared to the corresponding final release 
-of the Xfce core desktop. They also have to follow the X.Y.Z versioning format, where Y is an even+of the Xfce core desktop. They also must follow the X.Y.Z versioning format, where Y is an even
 number (e.g. xfwm4-4.8.4 or thunar-1.2.4). No new features or strings may be introduced in these number (e.g. xfwm4-4.8.4 or thunar-1.2.4). No new features or strings may be introduced in these
 releases. releases.