KDevelop/Release Process: Difference between revisions
< KDevelop
(Created page with "=Release process for publishing a new KDevelop version= ==Checklist== This checklist should be processed in the respective order. * Website ** Prepare release announcement...") |
(→Checklist: Add instructiosn for releaseme) |
||
| Line 10: | Line 10: | ||
* Repositories (needs to be done for each repository we release) | * Repositories (needs to be done for each repository we release) | ||
** Verify unit tests are working | ** Verify unit tests are working | ||
** Using the ReleaseMe script | ** Using the '''ReleaseMe''' script (see next paragraph) | ||
*** Generate tarballs | *** Generate tarballs | ||
*** Tag the version | *** Tag the version | ||
| Line 37: | Line 37: | ||
More information can be found here: https://techbase.kde.org/ReleasingExtragearSoftware | More information can be found here: https://techbase.kde.org/ReleasingExtragearSoftware | ||
==Using ReleaseMe== | |||
Setup: | |||
git clone kde:releaseme | |||
cd releaseme | |||
cat README.md | |||
Step 1: tarballing | |||
./tarme.rb --version 5.0 --origin 5.0 kdevplatform | |||
Step 2: tagging | |||
./tagme.rb 5.0.0 | |||
Rinse & repeat for kdevelop, kdev-php, kdev-python | |||
Upload the tarballs to the KDE FTP and notify the sysadmins: | |||
* Upload to ftp://upload.kde.org:21/incoming/ | |||
* Create ''one'' ticket at https://phabricator.kde.org/maniphest/task/edit/form/2/ | |||
Also add the sha256sum of the tarballs to the sysadmin ticket; also tell where sysadmins should upload the tarballs. | |||
* Example destination: http://download.kde.org/stable/kdevelop/5.0.0/src/ | |||
Revision as of 20:41, 18 October 2016
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 (see next paragraph)
- 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
Using ReleaseMe
Setup:
git clone kde:releaseme cd releaseme cat README.md
Step 1: tarballing
./tarme.rb --version 5.0 --origin 5.0 kdevplatform
Step 2: tagging
./tagme.rb 5.0.0
Rinse & repeat for kdevelop, kdev-php, kdev-python
Upload the tarballs to the KDE FTP and notify the sysadmins:
- Upload to ftp://upload.kde.org:21/incoming/
- Create one ticket at https://phabricator.kde.org/maniphest/task/edit/form/2/
Also add the sha256sum of the tarballs to the sysadmin ticket; also tell where sysadmins should upload the tarballs.
- Example destination: http://download.kde.org/stable/kdevelop/5.0.0/src/