Release todo 15.0.0-beta.3

[danxuliu]

Get branches/versions to release from https://github.com/nextcloud/spreed/milestones

💺 Preparation

• Check all milestones don't have priority issues still open
  • https://github.com/nextcloud/spreed/milestone/156
• Check there are no pending backports: backport-request
• On major releases create a test package and check if a new development file needs to be added to the packaging exclude list in Makefile

  make appstore

• Create a PR against master CHANGELOG.md with the changelog of all milestones that are subject to the release
  • Changelog for 15.0.0 beta.3 #7881
• Merge the PR

🚀 v15.0.0-beta.3

Start with the oldest version here, so the appstore and github releases show the newest version as "Last release"

• Make sure you pull the latest stable branch:

  git checkout master
  git pull origin master

• Clean the dev instance and update all dependencies with the lock file versions and build the production javascrip:

  make clean-dev composer-install-production npm-init build-js-production

• Do a quick smoke test by starting a call with:
  • Chrome
  • Edge
  • Firefox
  • Safari
  • Android app
  • iOS app
• Create tag

  make create-tag version=15.0.0-beta.3

• Push the git tag to https://github.com/nextcloud-releases/spreed

  git push releases v15.0.0-beta.3

• Mark the tag as a (pre-)release in https://github.com/nextcloud-releases/spreed/releases
  • Add the respective CHANGELOG.md section
• Mark the tag as a (pre-)release in https://github.com/nextcloud/spreed/releases
  • Add the respective CHANGELOG.md section
  • 🛑 Do NOT re-upload the binary here.
• Check that the GitHub Action started: https://github.com/nextcloud-releases/spreed/actions
• Rename milestone 💚 Next Beta (25) to v15.0.0-beta.3
• Unless last release of the stable branch:
  • Create a follow up milestone for 💚 Next RC (25) (Due date in ~4 weeks)
  • Move all open PRs and issues from milestone v15.0.0-beta.3 to 💚 Next RC (25)
• Close the v15.0.0-beta.3 milestone
• In case there were security issues fixed ping the security team