🚀 Release todo 20.0.0-beta.2

[nickvergessen]

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

💺 Preparation

• Check there are no pending backports:
  • backport-request
• Check all milestones don't have priority issues still open
  • https://github.com/nextcloud/spreed/milestone/265
• Check there are no important PRs open against the branch
  • https://github.com/nextcloud/spreed/pulls?q=is%3Apr+is%3Aopen+base%3Amaster

🚀 v20.0.0-beta.2

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

• Backport the changelog

  • Release 20.0.0 beta.2 #12876
  • Remove changelog entries in CHANGELOG.md of higher versions
  • Bump the version in appinfo/info.xml
  • Bump the version in package.json. The following command will return a new version name, make sure it matches what you expect:

  # Make sure the printed version matches the info.xml version
  npm version --no-git-tag-version $(xmllint --xpath '/info/version/text()' appinfo/info.xml)

• Merge the backport

• 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 javascript:

  make production-setup
  # On 24 and older versions run:
  # make dev-setup build-js-production

• Do a quick smoke test by starting a call with:

  • Chrome
  • Edge
  • Firefox
  • Safari
  • Desktop client (Talk 16+)
  • Android app
  • iOS app

• Create tag (note that the leading v in v20.0.0-beta.2 will be automatically added to the tag)

  make create-tag version=20.0.0-beta.2

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

  git push releases v20.0.0-beta.2

  Make sure you have access rights to the remote repository, and it is set up on your machine:

  git remote add releases git@github.com:nextcloud-releases/spreed.git

• Prepare a (pre-)release in https://github.com/nextcloud/spreed/releases/new?tag=v20.0.0-beta.2

  • Make sure that chosen tag is v20.0.0-beta.2, target is master, and previous tag is v20.0.0-beta.1
  • Add the respective CHANGELOG.md section from merged PR
  • Use the Generate release notes button and wrap the output result into

    ## What's Changed
    
    <details>
    	<!-- insert the output here -->
    </details>
    

  • Set as a pre-release / as the latest release
  • Publish release

• Prepare a (pre-)release in https://github.com/nextcloud-releases/spreed/releases/new?tag=v20.0.0-beta.2

  • Copy the full content from the release description of the previous step
  • Set as a pre-release / as the latest release
  • Publish release

• Check that the GitHub Action started: https://github.com/nextcloud-releases/spreed/actions

• Rename milestone 💙 Next Beta (30) to v20.0.0-beta.2 in https://github.com/nextcloud/spreed/milestones
  Unless last release of the stable branch:

  • Create a follow up milestone for 💙 Next Beta (30) (Due date in ~4 weeks, ~4 days for beta/RC)
  • Move all open PRs and issues from milestone v20.0.0-beta.2 to 💙 Next Beta (30)

• Close the v20.0.0-beta.2 milestone

• Ensure that the GitHub Action finished successfully: https://github.com/nextcloud-releases/spreed/actions

• In case there were security issues fixed ping the security team

• Post the changelog in 💬 Talk team public 👥

[nickvergessen]

Must-have

• Fix silent call notifications in federated calls #12856
• …

Nice-to-have

• fix(MessageList): rewrite CSS layout of chat #12823 (and two follow-ups based on it)