The KDE Release Team Project Page
The purpose of the KDE Release Team is to define and execute the official software releases of KDE.
The Release Team is responsible for setting release schedules for the official KDE releases. This includes release dates, deadlines for individual release steps and restrictions for code changes.
The Release Team coordinates release dates with the marketing and press efforts of KDE.
The Release Team is composed of Module Coordinators, Marketing Team liaison (sebas), and the people who actually do the work of tagging and creating the releases (aacid, tnyblom, winterz).
As is our tradition, decision making is an open and public process and we welcome input from all concerned parties, including our partners, the packagers, and the distros.
Please contact the Release Team by email or join our public mailing list. The release-team mailinglist is moderated by Richard Moore (IRC: richmoore) and Dirk Müller (IRC: dirk). They will (need to) approve email sent by people not subscribed. In case they miss something (which can always happen as we're all busy people), please ping them on IRC.
- Make sure KDE is in a releasable state when we release it (this depends of course on the individual modules)
- Plan and communicate when KDE releases happen, and intermediate steps to get there (betas, rcs, code freeze and unfreezes)
- Providing packagers with sufficient information to package and ship KDE (information about dependencies, for example)
- Decide on exemptions for the code freezes (often boils down to granting it if the translation team OKs it)
- Collecting the set of features for the next release
- Take the final decision if a feature enters the release, or not
The Release Process
Module coordinators perform the following duties:
- primary point of contact for the Release Team concerning issues with the module
- help determine release schedules
- communicate release schedules with the module developers
- provide feedback from developers to the Release Team
- review new applications for inclusion in the module
- review old, unmaintained applications for removal from the modules and help find new maintainers
- review external dependencies for the module
- help set and review goals for major and feature releases
- help with release preparation (eg. update application version numbers)
|kdelibs||KDE foundational libraries||David Faure|
|kdepimlibs||KDE personal information libraries||Allen Winter|
|kde-runtime||Applications required by KDE apps to function properly at runtime, such as a help browser, framework (e.g. phonon, solid) backends, and certain configuration modules||Olivier Goffart|
|kde-workspace||the UNIX/Linux desktop shell||Aaron Seigo|
|kde-baseapps||Essential apps needed to complement a desktop shell for basic functionality (web browser, file manager, ...)||help wanted|
|kate||The KDE editor||Christoph Cullmann|
|konsole||The KDE Console||Kurt Hindenburg|
|kdeaccessibility||Accessibility applications||Gunnar Schmi Dt|
|kdeartwork||Additional icons, styles, etc.||Riccardo Iaconelli|
|kdeadmin||Tools for system administration||Nicolas Ternisien|
|kdeedu||Applications with educational content||Anne-Marie Mahfouf|
|kdegraphics||Graphics viewing and editing||Aaron Seigo|
|kdemultimedia||Audio and video applications||Harald Sitter|
|kdenetwork||Network-centric apps (IM, remote desktop, etc)||Urs Wolfer|
|kdeplasma-addons||Plasma applets||Aaron Seigo|
|kdesdk||Tools for software development||Friedrich Kossebaum|
|kdetoys||Fun distractions||Stefan Böhmann|
|kdeutils||Miscellaneous utilities||Raphael Kubo da Costa|
|kdewebdev||Web development tool suite||Andras Mantia|
|extragear||Extragear||Helio Chissini de Castro|
|l10n-kde4||Localization||Albert Astals Cid|
|calligra||Calligra Office Suite||Cyrille Berger|