Difference between revisions of "Projects/Release Team"

Jump to: navigation, search
(change current activities to activities, to be reviewed on the list)
Line 16: Line 16:
 
Please contact the Release Team by [mailto:release-team@kde.org email] or join our public [https://mail.kde.org/mailman/listinfo/release-team mailing list].
 
Please contact the Release Team by [mailto:release-team@kde.org email] or join our public [https://mail.kde.org/mailman/listinfo/release-team mailing list].
  
== Current Activities ==
+
== Activities ==
 
+
* Make sure KDE is in a releasable state when we release it (this depends of course on the individual modules)
* The 4.1 branch is in bugfixing mode, preparing for 4.1.3 to be tagged by the end of October 2008. Bugfix / translation updates are being shipped on a monthly schedule.
+
* Plan and communicate when KDE releases happen, and intermediate steps to get there (betas, rcs, code freeze and unfreezes)
* Trunk is open for new features, new strings, bugfixing, and new artwork in preparation for 4.2.0 expected in Jan 2009
+
* 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
  
 
== Module Coordinators ==
 
== Module Coordinators ==

Revision as of 16:40, 26 June 2009

Contents

The KDE Release Team Project Page

Purpose

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.

Members

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 (dirk).

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.

Contact

Please contact the Release Team by email or join our public mailing list.

Activities

  • 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

Module Coordinators

Functions

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)

Coordinator List

Module Description Release Coordinator
kdelibs KDE foundational libraries help wanted
kdepimlibs KDE personal information libraries Allen Winter
kdebase-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
kdebase-workspace the UNIX/Linux desktop shell help wanted
kdebase-apps Essential apps needed to complement a desktop shell for basic functionality (web browser, file manager, ...) help wanted
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
kdegames Entertainment Matt Williams
kdegraphics Graphics viewing and editing Aaron Seigo
kdemultimedia Audio and video applications Matthias Kretz
kdenetwork Network-centric apps (IM, remote desktop, etc) Urs Wolfer
kdepim Groupware Allen Winter
kdeplasma-addons Plasma applets Aaron Seigo
kdereview Staging area Tom Albers
kdesdk Tools for software development Matt Rogers
kdetoys Fun distractions Stefan Böhmann
kdeutils Miscellaneous utilities Friedrich W. H. Kossebau
kdevplatform KDE Development Applications Platform libraries Andreas Pakulat
kdevelop KDE IDE Andreas Pakulat
kdewebdev Web development tool suite Andras Mantia
extragear Extragear Helio Chissini de Castro
l10n-kde4 Localization Albert Astals Cid
koffice KOffice Cyrille Berger

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal