Release check list

Aggiornato 5 anni fa

The goal is to produce release packages for the following platforms and advertise the new release

  • Windows (MSI, signed)
  • Windows Store (APPX)
  • AppImage for Linux (at least x86_64)
  • macOS (DMG, signed)
  • Source tarball (ZIP)

Steps

  • Write or update release notes

  • Prepare announcement, like e.g. https://musescore.org/en/2.2

  • Update translations: manually get translations from transifex and push them to github in the relevant branch

  • Convert the templates from mscx to mscz, e.g. by using mscore --templatemode -j share/templates/convert.json
  • Make sure that Windows CPACK_WIX_PRODUCT_GUID is different from previous versions in build/Packaging.cmake
  • Make sure the Product Version is right in WIX template
  • Mark MuseScore as stable, make sure the right version number is set in CmakeLists.txt and Makefiles and commit, like e.g. 9c73a21
  • Make sure the splash screen has the right version

  • Tag the release on GitHub

  • Travis should create AppImages and DMG file.

  • Verify AppImages
  • Verify DMG, in particular check that the signing is correct

  • Verify that the DMG uses the right MuseScore.com keys

  • On Windows, AppVeyor should create the MSI package and store it to mscore-nightlies FTP

  • For Windows store

    • Build with BUILD_FOR_WINSTORE = ON
    • Package using Microsoft tools and submit
    • Wait up to 2 days for MS to validate the build
    • Fix issue and resubmit until accepted…

  • For the source package, it's created by the test job on Appveyor and uploaded to mscore-nightlies FTP (src directory) It should contains the right version in revision.h and the correct soundfont.

  • Test packages on Virtual machines, especially the windows one.

  • Packages should all be on mscore-nightlies FTP share for example and have them tests by  the close community as much as possible. Stuff to test:

    • MSI, upgrade path
    • OS integration: sound…
    • MuseScore.com integration

  • When all packages are done, tested. Compute SHA 256 for each package. It will be used on download page to verify integrity

  • Upload to

    • ftp.osuosl.org
    • sourceforge.net

  • Upgrade our services

    • Upgrade MuseScore.com general and audio backend
    • Upgrade MuseScoreVideo and backend
    • Upgrade audiveris backend
    • Upgrade the mobile apps

  • Announce new release on MuseScore Connect

  • Update http://update.musescore.org
  • Mail announcement on developers mailing list
  • Announcement on IRC & Telegram

  • Mail to package managers : http://musescore.org/en/developers-handbook/distribution-maintainers

  • Make blog post for musescore front page

  • Translate and call for translators for post on musescore front page

  • Check and list Release Notes translation

  • Update http://musescore.org/en/download and translations

  •  MuseScore Newsletter

  • Update the pad.xml file

  • Whitelist request to antivirus companies

  • Update some of these product page, or verify they use the pad.xml file https://del.icio.us/musescore/productpage. In particular

    • Macupdate
    • majorgeek

  • Contact blogs and newspapers