Difference between revisions of "Projects/Release Team/Release Process Responsibilities"

Jump to: navigation, search
 
(One intermediate revision by one user not shown)

Latest revision as of 21:39, 6 May 2012

Contents

[edit] KDE SC Release Packaging Responsibilities

[edit] The KDE Continuous Integration (CI) System

 1. all the KDE SC modules are built continuously
 2. no packaging unless all modules build ok
    (even better would be to force all make tests too)
 3. the packaging tools run on the CI system generating "test" tarballs
 4. the "test" tarballs could be downloaded from the CI system
 5.

[edit] The KDE Sysadmin Team

 1. provides and manages the CI system
 2. will transfer "test" tarballs to the public ftp site
 3. prepares the public ftp site for bandwidth requirements at release announce time
 4.

[edit] The KDE Promo Team

 1. writes and distributes release announcements through normal channels
 2. deals with the media
 3. manages public expectations
 4.

[edit] The KDE i18n Team

 1. maintains the languages list
 2.

[edit] The KDE Release Team

 1. coordinates the entire release effort
 2. sets release milestones and dates
 3. communicates important dates to the community and to distros
 4. communicates important news to the community and to distros
 5. creates "test" tarballs using the CI system and handles distro feedback
 6. adds hot and security patches to the tarballs before the final release
 7. creates "final" tarballs using the CI system
 8. pushes tags to the module repositories in a timely manner
 9. writes and maintains the necessary tools
 10. writes and maintains the release process documentation

This page was last modified on 6 May 2012, at 21:39. This page has been accessed 1,375 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal