friendica

Table of Contents

From @tobiasd

Preparations

Finalize the Changelog
update the credits and prevent the double entries to happen (multiple email addresses from a single author etc.).
Last minute check for late translations
Take the current code into a clean VM with the minimal requirements and test the installation process as written in de docs
Write the release notes down in Markdown as it needs to be copied at 3 places. Luckily WordPress can now parse Markdown so it can be copied there as well and does not need extra editing in the blog. Some part are copy and paste (esp. the information in the end)

Last pull from RC branches
merge RC into master
raise the version in VERSION, boot.php and CHANGELOG to the release version. Tag the repositories to the new version
create the tar.gz archive (see below)
push the tags to github.
edit the released tag information at github with the written release notes. Recheck that every link works.
force update/synchronization of both repositories at git.friendi.ca
add the release notes to git.friendi.ca tag release as well
add the release notes to the blog at friendi.ca.
Mark the release notes "sticky" in the blog and remove the sticky from the last versions release notes.

Create the tar.gz archive, strip all unnecessary git stuff, editorconfig, transifex, Vagrant etc files but remember to run the composer with minimal required PHP version
- Suggested command: bin/composer.phar archive --format=zip --file=friendica-full-XXXX.XX
Upload the archive to friendi.ca and add the sha256 sum to the list of downloadable archive files

merge master into develop
raise develop version (VERSION, boot.php)
Update the CHANGELOG file in develop accordingly with the new, unreleased version number and commit the changes
check that the translation source at Transifex is again the development branch and not the RC branch anymore
delete the old RC branch