Release Checklist 2.3.0

Mixxx 2.3.0 Release Checklist

#UNDER CONSTRUCTION#

This process is followed when it is time for a release (after betas and release candidates).

Release milestone summary

1. ✓ Ensure QA testing is complete and all tests pass.
2. ✓ Update translations
   1. Push and pull translations for Mixxx as described here: Internationalization
3. ✓ Take release screenshots for press page and blog post.
   1. Deere, LateNight, Shade, Tango
   2. Load up samplers, preview deck, etc.
   3. Make all the screenshots roughly uniform (same view, same tracks loaded, etc.)
   4. Take screenshots of the Mixxx window itself, not with your cluttered desktop in the background.
      1. macOS can produce particularly pretty drop-shadow screenshots with Shift-Command-4 followed by the spacebar, then click the window to screenshot.
4. ⌛ Update manual.
   1. ✓ Verify that https://github.com/mixxxdj/manual/tree/2.3 published the latest version to https://mixxx.org/manual/2.3/
   2. ⌛ Check that the manual is no longer marked as developer version
5. ⌛ Update files:
   1. ✓ LICENSE (update copyright year, version number)
   2. ⌛ CMakeLists.txt Update VERSION and MIXXX_VERSION_PRERELEASE
   3. ⌛ Check Debian Changelog and change PPA destination
6. ✓ Go through Git log, update credits in src/dialog/dlgabout.cpp.
7. ⌛ Build release packages with the build server.
   1. macOS Intel
   2. Ubuntu i386 / amd64
   3. Windows i386 / amd64
8. ⌛ Add a git tag with a GPG signature (release-2.2.0)git tag -s release-2.2.0 -m "Mixxx 2.2.0" git push --tags upstream release-2.2.0
   1. This can be done to a commit after it has been pushed or merged from a PR, so wait until you're sure you're ready to tag the release commit.
   2. Once pushed, a tag is forever. Never delete a tag from a remote.
9. ⌛ Upload packages.
   1. TODO ...
   2. Record SHA256sum of all packages in the Release Checksums Google Doc as a backup and record independent of downloads.mixxx.org (for forensic purposes).
   3. Update Launchpad
      1. Go to 2.3.0 Milestone.
      2. Mark milestone released
   4. Update the Stable and Beta PPAs.
      1. TODO ...
10. ⌛ Release announcement:
    1. Write to announcement in new forum thread. For the "Post topic as" option below the text box to type the post, select "Announcement".
    2. Cross-post to Zulip #announce stream
    3. Cross-post to mixxx-devel
    4. Cross-post to Facebook
11. ⌛ Update the website
    1. Update download page:
       1. Do this after posting the announcement forum thread so you can link to the announcement
       2. hide beta downloads
       3. move current release to previous
       4. replace current with new links
       5. update Google Analytics labels
    2. ✓ Update frontpage / features page / etc.
    3. ✓ Update screenshot downloads on Press page.
    4. Update screenshot in OpenGraph markup (so social shares have updated images!)
    5. Update credits for contributors to latest release.
    6. Update https://mixxx.org/manual/latest symlink to point to 2.3.
    7. ✓ Update copyright date here and on the blog
12. ⌛ Launchpad Updates
    1. Mark milestone released
    2. Change "Fix committed" bugs to "Fix released"

Promotion

1. ⌛ Email package maintainers
   1. Debian/Ubuntu - https://packages.debian.org/testing/mixxx
   2. Gentoo
   3. Arch - http://www.archlinux.org/packages/?q=mixxx
   4. Fedora
2. ⌛ E-mail bloggers
3. ⌛ Ask other Mixxx users to post on their blogs
4. ⌛ Send release email to everyone in the "Press Contacts" Google Doc.
5. ⌛ Update Wikipedia
6. ⌛ Update http://screenshots.debian.net
7. ⌛ Update software directories
   1. Freshmeat Freecode No longer maintained.
   2. OhLoh OpenHub
   3. Macupdate.com
8. ⌛ Social Media / Forums
   1. Facebook -- Boost Post ($$)
   2. Twitter
   3. LinkedIn Connected DJs group
   4. Reddit r/DJs
   5. DJTechTools Forums
   6. TranceAddict Forums
   7. omgubuntu.co.uk
9. ⌛ Update SourceForge to point people to the newest version

Post-Release

1. ⌛ Create 2.4 branch in mixxx manual and vcpkg
2. ⌛ Update main README, CMakeList.txt for 2.5
3. ⌛ Verify .github/workflow/build.yml