Creating a release

Prepare the repository

• Edit serendipity_config.inc.php to adjust $serendipity['version’]

• Update docs/NEWS adding release date

• Commit and push to Github.

• (Deprecated, but for now) Log in to SF.Net, create a new release directory, e.g. "2.3.0"

Cut the release

• Execute release packaging script:

# Check out GITHUB code
# create and isolate release.tar
# $BRANCH is "master" for alpha-beta-first releases, 2.3 or another feature branch for stable maintenance releases
cd git/$BRANCH/Serendipity
git pull
git archive --output release.tar --prefix serendipity/ $BRANCH
mv release.tar ../../../

# Remove probably existig files
cd ../../../
rm -rf serendipity
tar -xvf release.tar
rm serendipity-*.tar.gz
rm serendipity-*.zip

# Execute s9y release script
# $VERSION is the version number for the release, e.g. 2.3.1-alpha1 or 2.4.0
cd serendipity/bundled-libs
./create_release.sh serendipity-$VERSION.tar.gz serendipity nobody nogroup

# Generate release file(s)
cd ../../
zip -9 -r serendipity-$VERSION.zip serendipity

# DEPRECATED for now, Transmit release files to SourceForge
tar --owner=nobody --group=nogroup -cjf "serendipity-$VERSION.tar.bz2" serendipity
scp serendipity/docs/NEWS [email protected]:/home/frs/project/p/ph/php-blog/serendipity/$VERSION/README
scp serendipity/docs/NEWS [email protected]:/home/frs/project/p/ph/php-blog/serendipity/README
scp serendipity/docs/NEWS [email protected]:/home/frs/project/p/ph/php-blog/README
scp serendipity-$VERSION* [email protected]:/home/frs/project/p/ph/php-blog/serendipity/$VERSION/
# Login to SF.Net again, make the new release the default

# Create MD5 Checksums [save and use it for copy & paste]
md5sum serendipity-$VERSION.zip

Prepare and put release on Github

• Change docs/RELEASE file in master and 2.3 branch to point to new release, commit and push to Github.
• Create a tag for the release and push it to Github:

git tag $VERSION
git push origin --tags

• Create a Github release from the tag
• Upload created release file serendipity-$VERSION.zip to Github and attach it to the release item
• Add text and remember to put "(MD5: ...)" in the plain text body - DO NOT FORGET THE PARANTHESES, the auto-updated checks for it
• (Check the draft and) post the release

Prepare repository for the next version

• Increment version number to $VERSION+1 in serendipity_config.inc.php
• Add new heading in NEWS with this version number, but without a date

Update website, write release announcements

• Edit s9y.github.io download section (downloads.md), add MD5 checksums, update latest release recommendation (or new beta)
• For new stable releases:
  • Edit s9y.github.io button (_includes/showcase.html)
  • On www.s9y.org edit .htaccess to make the rewriterule latest point to the latest release.
• Write a blog.s9y.org release announcement, make sidebar point to latest release
• Write a board.s9y.org release announcement, point to blog posting

Update infrastructure

• Update blog.s9y.org to latest version