[Template] 🚀 Release todo X.Y.Z

[nickvergessen]

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

💺 Preparation

• [ ] Check there are no pending backports:
  • [ ] https://github.com/nextcloud/spreed/labels/backport-request
• [ ] Check all milestones don't have priority issues still open
  • [ ]
• [ ] Check there are no important PRs open against the branch
  • [ ]
  • [ ] https://github.com/nextcloud/spreed/pulls?q=is%3Apr+is%3Aopen+base%3AstableX
• [ ] On first RC of a major release
  • [ ] Create New in Talk TX 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 - [ ]
• [ ] Merge the PR

🚀 vX.Y.Z

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

• [ ] 🛑 When releasing from a stableX.0 branch make sure to:
  • [ ] Adjust the branch checkout below
  • [ ] Copy the l10n/ folder from stableX and commit it
• [ ] Backport the changelog
  • [ ]
  • [ ] 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 stableX.Y
  git pull origin stableX.Y

• [ ] 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 vX.Y.Z will be automatically added to the tag)

  make create-tag version=X.Y.Z

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

  git push releases vX.Y.Z

  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=vX.Y.Z

  • [ ] Make sure that chosen tag is vX.Y.Z, target is stableX.Y, and previous tag is vX.Y.[Z-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=vX.Y.Z
  • [ ] 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 Patch (X) to vX.Y.Z in https://github.com/nextcloud/spreed/milestones Unless last release of the stable branch:
  • [ ] Create a follow up milestone for 💚 Next Patch (X) (Due date in ~4 weeks, ~4 days for beta/RC)
  • [ ] Move all open PRs and issues from milestone vX.Y.Z to 💚 Next Patch (X): https://github.com/nextcloud/spreed/issues?q=is%3Aissue%20state%3Aopen%20milestone%3AvX.Y.Z
• [ ] Close the vX.Y.Z 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]

Legacy before 23

🚀 vX.Y.Z

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

• [ ] Backport the changelog
  • [ ]
  • [ ] Remove changelog entries in CHANGELOG.md of higher versions
  • [ ] Bump the version in appinfo/info.xml
• [ ] Merge the backport
• [ ] Make sure you pull the latest stable branch:

  git checkout stableX.Y
  git pull origin stableX.Y

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

  make dev-setup build-js-production

• [ ] Do a quick smoke test by starting a call with:
  • [ ] Chrome
  • [ ] Edge
  • [ ] Firefox
  • [ ] Safari
  • [ ] Android app
  • [ ] iOS app
• [ ] Build release tarball

  make release version=X.Y.Z

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

  git push releases vX.Y.Z

• [ ] Mark the tag as a (pre-)release in https://github.com/nextcloud-releases/spreed/releases
  • [ ] Add the respective CHANGELOG.md section
  • [ ] Upload the tarball from build/artifacts/
  • [ ] 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.
• [ ] Upload the app release in the appstore: https://apps.nextcloud.com/developer/apps/releases/new
  • Link to the tarball on https://github.com/nextcloud-releases/spreed/releases
  • Signature that was printed by make release version=X.Y.Z
• [ ] Rename milestone 💚 Next Patch (X) to vX.Y.Z
• Unless last release of the stable branch:
  • [ ] Create a follow up milestone for 💚 Next Patch (X) (Due date in ~4 weeks)
  • [ ] Move all open PRs and issues from milestone vX.Y.Z to 💚 Next Patch (X)
• [ ] Close the vX.Y.Z milestone
• [ ] In case there were security issues fixed ping the security team