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 16.0.8, 17.1.3 and 18.0.0-rc.1 #10946

Closed
nickvergessen opened this issue Nov 20, 2023 · 0 comments
Closed

🚀 Release todo 16.0.8, 17.1.3 and 18.0.0-rc.1 #10946

nickvergessen opened this issue Nov 20, 2023 · 0 comments

Comments

@nickvergessen
Copy link
Member

nickvergessen commented Nov 20, 2023

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

💺 Preparation

🚀 v16.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 16.0.8 #10988
    • 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 stable26
    git pull origin stable26
  • 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 v16.0.8 will be automatically added to the tag)

    make create-tag version=16.0.8
  • Push the git tag to https://github.com/nextcloud-releases/spreed

    git push releases v16.0.8
  • Mark the tag as a (pre-)release in https://github.com/nextcloud/spreed/releases/new?tag=v16.0.8

    • Add the respective CHANGELOG.md section
    • Use the Generate release notes button and wrap put the result into
      ## What's Changed
      
      <details>
      
      </details>
      
  • Mark the tag as a (pre-)release in https://github.com/nextcloud-releases/spreed/releases/new?tag=v16.0.8

    • Copy the release description from before
  • Check that the GitHub Action started: https://github.com/nextcloud-releases/spreed/actions

  • Rename milestone 🧡 Next Patch (26) to v16.0.8 in https://github.com/nextcloud/spreed/milestones
    Unless last release of the stable branch:

    • Create a follow up milestone for 🧡 Next Patch (26) (Due date in ~4 weeks, ~4 days for beta/RC)
    • Move all open PRs and issues from milestone v16.0.8 to 🧡 Next Patch (26)
  • Close the v16.0.8 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

🚀 v17.1.3

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.3 #10989
    • 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.3 will be automatically added to the tag)

    make create-tag version=17.1.3
  • Push the git tag to https://github.com/nextcloud-releases/spreed

    git push releases v17.1.3
  • Mark the tag as a (pre-)release in https://github.com/nextcloud/spreed/releases/new?tag=v17.1.3

    • Add the respective CHANGELOG.md section
    • Use the Generate release notes button and wrap put the result into
      ## What's Changed
      
      <details>
      
      </details>
      
  • Mark the tag as a (pre-)release in https://github.com/nextcloud-releases/spreed/releases/new?tag=v17.1.3

    • Copy the release description from before
  • Check that the GitHub Action started: https://github.com/nextcloud-releases/spreed/actions

  • Rename milestone 💚 Next Patch (27) to v17.1.3 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.3 to 💚 Next Patch (27)
  • Close the v17.1.3 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

🚀 v18.0.0-rc.1

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.0 rc.1 #10990
    • 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 main
    git pull origin main
  • 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.0-rc.1 will be automatically added to the tag)

    make create-tag version=18.0.0-rc.1
  • Push the git tag to https://github.com/nextcloud-releases/spreed

    git push releases v18.0.0-rc.1
  • Mark the tag as a (pre-)release in https://github.com/nextcloud/spreed/releases/new?tag=v18.0.0-rc.1

    • Add the respective CHANGELOG.md section
    • Use the Generate release notes button and wrap put the result into
      ## What's Changed
      
      <details>
      
      </details>
      
  • Mark the tag as a (pre-)release in https://github.com/nextcloud-releases/spreed/releases/new?tag=v18.0.0-rc.1

    • Copy the release description from before
  • Check that the GitHub Action started: https://github.com/nextcloud-releases/spreed/actions

  • Rename milestone 💙 Next Beta (28) to v18.0.0-rc.1 in https://github.com/nextcloud/spreed/milestones
    Unless last release of the stable branch:

    • Create a follow up milestone for 💙 Next Beta (28) (Due date in ~4 weeks, ~4 days for beta/RC)
    • Move all open PRs and issues from milestone v18.0.0-rc.1 to 💙 Next Beta (28)
  • Close the v18.0.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

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

1 participant