Release team's activities

Sebastian Kügler sebas at
Fri Jun 26 19:12:15 CEST 2009

I've just updated the release team's techbase page, I think the changes are 
mostly trivial and just documenting what we actually do. I do want people to 
look over it to make sure we're all on the same page.

I've replaced "Current Activities" with "Activities", changing "we're now in 
the 4.1.3 freeze, ..." with a couple of points what we actually do on a 
regular basis.

* 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

If I missed something important, please add it as a reply.

Thanks for the input already,
sebas | | GPG Key ID: 9119 0EF9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: This is a digitally signed message part.
Url : 

More information about the release-team mailing list