KDevelop/Release Process
Appearance
< KDevelop
Release process for publishing a new KDevelop version
Checklist
This checklist should be processed in the respective order.
- Website
- Prepare release announcement for kdevelop.org (don't publish yet)
- Repositories (needs to be done for each repository we release)
- Verify unit tests are working
- Using the ReleaseMe script
- Generate tarballs
- Tag the version
- Adjust codebase for next dev cycle
- Bugzilla
- Add new versions in bugzilla
- Add new milestones in bugzilla
- Publishing
- Upload tarball to KDE FTP (see ftp://upload.kde.org/README)
- File sysadmin ticket to publish files
- Wait for it to be uploaded
- When files are uploaded
- Update download page on the website (https://www.kdevelop.org/download)
- Publish release announcement on the website
- Share blog post on Reddit/Hackernews/Twitter/whatever
- Mail release announcement to kde-announce-apps@ & kdevelop@ & kdevelop-devel@
- Update IRC channel topic
- Optional stuff
- Update Wikipedia (release date, feature comparison)
- Update screenshots (website, kde.org, kde-apps, freshmeat, facebook)
- Update OpenHub (app icon/logo)
More information can be found here: https://techbase.kde.org/ReleasingExtragearSoftware