From Rokymotion Wiki
Contents |
20 Inch Release Specification
General
Tarball
- REALLY well tested
- Build on common distros with all deps
Notification Addresses
- amarok-devel @ k (restricted information - actual release day announced on IRC)
- amarok-promo @ k (restricted information - actual release day announced on IRC)
- amarok-packagers @ gg
- i18n-doc @ k (restricted information)
Page Updates
Major + Minor
alpha cycle
- Sort major feature issues
beta cycle
- All important issues get solved
- Sort as many small issues as possible
rc cycle
- lasts until everything is in perfect shape for a release
l10n
- Announce the same time as the pre announces for -packagers and -devel
- Freeze strings 30 days before release
- Evaluate translation status while the freeze is up and take action if needed (e.g. notify very unfinished translations)
release news for amarok.kde.org
- Highly self-promotional
- List hotest new features
- Link to download page
- Mention the series' name
- To be finished 7 days before release -> call for translations
short release news for dot.kde.org
- Focus on KDE people
- List hotest new features
- Mention stuff which is especially important to KDE (new interactions)
open news for use on any site
- (Neutral) 3rd party point of view
- For use on any site (news, blogs, forums)
- No self-promotion
- List hotest new features in a easy and understandable way
- To be finished 15 days before the release (time for translation)
l10n of the open news
- Ask KDE l10n by mail
- Include a "where to ask" in case someone needs help with understanding
- Also ask to send the translated news to local news sites as soon as we announce the release.
distribution of open news
Patch + Beta
l10n
- An announcement of the up coming release (which doesn't have to include the final date) should be send out to the KDE translation team as soon as the date is set (also include: the date when string freeze starts). A string freeze of at least 4 days is preferable. As part of the tarball testing the status of translations should be checked as well - totally unfinished language's translators should get informed separately about the release. Therefore should the realease candidate of the tarball be built within a meaningful time till release (start of string freeze for example).
release news for amarok.kde.org
- The release news for amarok.kde.org should be highly self-promotional. It has to include a list of hotest new features. The news has to include a link to the amaroK download page in the amaroK wiki. For better looking the news should have a cool release image. The news has to be finished 2 days before the release.
Status updates
- To ensure higher success when promoting stuff important for the community (including us), a special section with status updates from and about the community should be add. This alos includes annoucements of new services not concerning amaroK it self (big topic, or high important stuff should still get it's own annoucement).
short release news for dot.kde.org
- For releases with important changes or for example first beta release a news for the KDE Dot should be prepared. It has to include a short overview of hotest new stuff and link to the news at amarok.kde.org and the download section. The dot.kde.org news has to be finished 1 day before the release.
release process indication
- PHASE Red: tarball testing
- CODE Zero: final tarball build
- Silence: everything focused on upcoming release - last promotional activites and news polishing
- Genesis: official release
- Alpha Wolf: final version