2 This file contains a to-do-list for releases. In braces the responsible person; none given means everybody.
6 Blog about new features that have been added.
7 Also: Facebook http://www.facebook.com/pages/Kdenlive/168566469873278
13 Add blog entries to the discover page (http://kdenlive.org/discover/0.8 but with updated version number).
14 Add the changelog as well.
17 Prepare an article for http://dot.kde.org/ (may take some days until it is accepted) (they say)
20 * Notify devs, testers, and translators of the String/Feature Freeze
21 * Notify packagers about the new release when it's done
24 About two weeks before a new release feature and string freeze will be introduced. This allows:
25 * Translators to translate Kdenlive everything on time. (Strings must not be changed anymore
26 in the source code, otherwise the translators would have to fix it again and so on.)
27 * Testers on finding remaining bugs
28 * Developers to focus on bug fixing (and not introducing new bugs with new features)
31 Ideally mobilize as many testers as possible to find remaining bugs before the version is released!
34 Update the manual (push to git) from the Userbase
35 http://userbase.kde.org/Kdenlive
36 http://userbase.kde.org/How_To_Convert_a_UserBase_Manual_to_Docbook
40 Close all entries that have been resolved in this release.