Release todo 20.1.0-rc.1

[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/278
• Check there are no important PRs open against the branch
  • https://github.com/nextcloud/spreed/pulls?q=is%3Apr+is%3Aopen+base%3Astable30
• On first RC of a major release
  • Create New in Talk T30 entries in the Talk updates ✅ conversation
  • Create a test package and check if a new development file needs to be added to the packaging exclude list in Makefile

  make appstore

  • Make sure the GDPR document is updated for new database tables/columns
  • Make sure dependabot.yml is sending patch updates to the stable branch
• Create a PR against master CHANGELOG.md with the changelog of all milestones that are subject to the release
  • chore(release): Add changelog for 20.1.0-rc.1 #13773
• Merge the PR

🚀 v20.1.0-rc.1

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

• 🛑 When releasing from a stable30.0 branch make sure to:
  • Adjust the branch checkout below
  • Copy the l10n/ folder from stable30 and commit it
• Backport the changelog
  • [stable30] chore(release): Add changelog for 20.1.0-rc.1 #13781
  • 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 stable30
  git pull origin stable30

• 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.1.0-rc.1 will be automatically added to the tag)

  make create-tag version=20.1.0-rc.1

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

  git push releases v20.1.0-rc.1

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

  git remote add releases [email protected]:nextcloud-releases/spreed.git

• Prepare a (pre-)release in https://github.com/nextcloud/spreed/releases/new?tag=v20.1.0-rc.1
  • Make sure that chosen tag is v20.1.0-rc.1, target is stable30, and previous tag is v20.0.2
  • 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.1.0-rc.1
  • 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 Minor (30) to v20.1.0-rc.1 in https://github.com/nextcloud/spreed/milestones
  Unless last release of the stable branch:
  • Create a follow up milestone for 🌠 Next RC (30) (Due date in ~4 weeks, ~4 days for beta/RC)
  • Move all open PRs and issues from milestone v20.1.0-rc.1 to 🌠 Next RC (30): https://github.com/nextcloud/spreed/issues?q=is%3Aissue%20state%3Aopen%20milestone%3Av20.1.0-rc.1
• Close the v20.1.0-rc.1 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 👥