Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release todo 17.1.9, 18.0.8 and 19.0.1 #12405

Closed
danxuliu opened this issue May 23, 2024 · 0 comments
Closed

Release todo 17.1.9, 18.0.8 and 19.0.1 #12405

danxuliu opened this issue May 23, 2024 · 0 comments

Comments

@danxuliu
Copy link
Member

danxuliu commented May 23, 2024

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

💺 Preparation

🚀 v19.0.1

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

  • Backport the changelog
    • Release 19.0.1 #12409
    • 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 [email protected]: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
    • 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
    • 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)
  • 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 👥

🚀 v18.0.8

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

  • Backport the changelog
    • Release 18.0.8 #12408
    • 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 [email protected]: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
    • 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
    • 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)
  • 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 👥

🚀 v17.1.9

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

  • Backport the changelog
    • Release 17.1.9 #12407
    • 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 [email protected]: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
    • 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
    • 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)
  • 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 👥
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants