Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| releng:release-policy [2009/05/28 12:42] – jannis | releng:release-policy [2009/05/28 14:51] – jannis | ||
|---|---|---|---|
| Line 65: | Line 65: | ||
| of the cycle. This is explained in more detail in the Release Team section of | of the cycle. This is explained in more detail in the Release Team section of | ||
| this document. | this document. | ||
| + | |||
| + | == Release Team == | ||
| + | |||
| + | The release team consists of at least two people: one release manager who can | ||
| + | be assisted by others to actually perform the release (tagging, creation of | ||
| + | tarballs, writing release notes and announcements) and another person for | ||
| + | quality assurance (checking if all components compile, tags are in place, | ||
| + | release notes are up to date and so on). This is defined in more detail | ||
| + | below. | ||
| + | |||
| + | These are the release team roles and their responsibilities: | ||
| + | |||
| + | **Release Manager** | ||
| + | |||
| + | - Organization of the release cycle | ||
| + | - Announce deadlines to developers and translators (repeatedly and early enough) | ||
| + | - Overseeing of maintainance and development releases | ||
| + | - Tagging of Xfce-X.Ypre1, | ||
| + | - Generate tarballs from tags (possibly automated) | ||
| + | - Write release notes | ||
| + | - Write release announcements | ||
| + | - Approve fixes of blocker bugs during code freeze | ||
| + | |||
| + | **Release Assistant(s)** | ||
| + | |||
| + | - Update the website(s) | ||
| + | - Make sure API documentation is up to date | ||
| + | - Create bugzilla tags | ||
| + | |||
| + | **QA Official** | ||
| + | |||
| + | - Have an eye on libtool versions of maintanance and development releases | ||
| + | - Remind maintainers about missing NEWS updates | ||
| + | - Double-check the generated tarballs | ||
| + | - Proof-read release announcements | ||
| + | |||
| + | **Individual Maintainers** | ||
| + | |||
| + | - Create component-specific tags for their maintainance and development releases | ||
| + | - Generate tarballs for their maintainance and development releases | ||
| + | - Write ChangeLogs and update NEWS files | ||
| + | - Write component-specific release announcements | ||
| === Dependency Freeze === | === Dependency Freeze === | ||
| Line 74: | Line 116: | ||
| At the end of this, a decision is made on which dependencies the next | At the end of this, a decision is made on which dependencies the next | ||
| - | stable release of the Xfce core desktop will depend | + | stable release of the Xfce core desktop will depend. In particular this |
| includes the minimum required versions for all essential dependencies of the | includes the minimum required versions for all essential dependencies of the | ||
| - | Xfce core desktop | + | Xfce core desktop. |
| Maintainers who were not available during the first 2 weeks of the planning | Maintainers who were not available during the first 2 weeks of the planning | ||
| Line 215: | Line 257: | ||
| master (where the development for the next release takes place) and into e.g. thunar-1.2 | master (where the development for the next release takes place) and into e.g. thunar-1.2 | ||
| or xfwm4-4.8. | or xfwm4-4.8. | ||
| - | |||
| - | ==== Release Team ==== | ||
| - | |||
| - | The release team consists of at least two people: one release manager who can | ||
| - | be assisted by others to actually perform the release (tagging, creation of | ||
| - | tarballs, writing release notes and announcements) and another person for | ||
| - | quality assurance (checking if all components compile, tags are in place, | ||
| - | release notes are up to date and so on). This is defined in more detail | ||
| - | below. | ||
| - | |||
| - | These are the release team roles and their responsibilities: | ||
| - | |||
| - | == Release Manager == | ||
| - | |||
| - | - Organization of the release cycle | ||
| - | - Announce deadlines to developers and translators (repeatedly and early enough) | ||
| - | - Overseeing of maintainance and development releases | ||
| - | - Tagging of Xfce-X.Ypre1, | ||
| - | - Generate tarballs from tags (possibly automated) | ||
| - | - Write release notes | ||
| - | - Write release announcements | ||
| - | - Approve fixes of blocker bugs during code freeze | ||
| - | |||
| - | == Release Assistant(s) == | ||
| - | |||
| - | - Update the website(s) | ||
| - | - Make sure API documentation is up to date | ||
| - | - Create bugzilla tags | ||
| - | |||
| - | == QA Official == | ||
| - | |||
| - | - Have an eye on libtool versions of maintanance and development releases | ||
| - | - Remind maintainers about missing NEWS updates | ||
| - | - Double-check the generated tarballs | ||
| - | - Proof-read release announcements | ||
| - | |||
| - | == Individual Maintainers == | ||
| - | |||
| - | - Create component-specific tags for their maintainance and development releases | ||
| - | - Generate tarballs for their maintainance and development releases | ||
| - | - Write ChangeLogs and update NEWS files | ||
| - | - Write component-specific release announcements | ||
| ==== Maintenance Process ==== | ==== Maintenance Process ==== | ||