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 http://techbase.kde.org/Projects/Release_Team If I missed something important, please add it as a reply. Thanks for the input already, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
