🚀 Release todo 17.1.10 | 18.0.9 | 19.0.4

[Antreesy]

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

💺 Preparation

• Check there are no pending backports:
  • backport-request
  • https://github.com/nextcloud/spreed/pulls?q=is%3Apr+is%3Aopen+stable29
• Check all milestones don't have priority issues still open
• Create a PR against master CHANGELOG.md with the changelog of all milestones that are subject to the release
  • chore(release): Changelog for 17.1.10 | 18.0.9 | 19.0.4 #12598
• Merge the PR

🚀 v17.1.10

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

• Backport the changelog
  • chore(release): v17.1.10 #12600
  • 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 stable27
  git pull origin stable27

• 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 v17.1.10 will be automatically added to the tag)

  make create-tag version=17.1.10

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

  git push releases v17.1.10

  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=v17.1.10
  • Make sure that chosen tag is v17.1.10, target is stable27, and previous tag is v17.1.9
  • 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=v17.1.10
  • 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 (27) to v17.1.10 in https://github.com/nextcloud/spreed/milestones
  Unless last release of the stable branch:
  • Create a follow up milestone for 💚 Next Patch (27) (Due date in ~4 weeks, ~4 days for beta/RC)
  • Move all open PRs and issues from milestone v17.1.10 to 💚 Next Patch (27)
• Close the v17.1.10 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 👥

🚀 v18.0.9

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

• Backport the changelog
  • chore(release): v18.0.9 #12601
  • 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 stable28
  git pull origin stable28

• 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 v18.0.9 will be automatically added to the tag)

  make create-tag version=18.0.9

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

  git push releases v18.0.9

  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=v18.0.9
  • Make sure that chosen tag is v18.0.9, target is stable28, and previous tag is v18.0.8
  • 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=v18.0.9
  • 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 (18) to v18.0.9 in https://github.com/nextcloud/spreed/milestones
  Unless last release of the stable branch:
  • Create a follow up milestone for 💚 Next Patch (18) (Due date in ~4 weeks, ~4 days for beta/RC)
  • Move all open PRs and issues from milestone v18.0.9 to 💚 Next Patch (18)
• Close the v18.0.9 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 👥

🚀 v19.0.4

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

• Backport the changelog
  • chore(release): v19.0.4 #12599
  • 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 stable29
  git pull origin stable29

• 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 v19.0.4 will be automatically added to the tag)

  make create-tag version=19.0.4

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

  git push releases v19.0.4

  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=v19.0.4
  • Make sure that chosen tag is v19.0.4, target is stable29, and previous tag is v19.0.3
  • 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=v19.0.4
  • 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 (29) to v19.0.4 in https://github.com/nextcloud/spreed/milestones
  Unless last release of the stable branch:
  • Create a follow up milestone for 💚 Next Patch (29) (Due date in ~4 weeks, ~4 days for beta/RC)
  • Move all open PRs and issues from milestone v19.0.4 to 💚 Next Patch (29)
• Close the v19.0.4 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 👥