Skip to content

Release todo 14.0.11, 15.0.6, 16.0.4, 17.0.0-rc.2 #9587

@nickvergessen

Description

@nickvergessen

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

💺 Preparation

🚀 v14.0.11

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

  • Backport the changelog

    • Release 14.0.11 #9592
    • 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:
    # Normal patch releases
    npm version patch --no-git-tag-version
    
    # First beta releases
    npm version premajor --no-git-tag-version --preid=beta
    npm version prerelease --no-git-tag-version --preid=beta
    
    # Other beta releases
    npm version prerelease --no-git-tag-version --preid=beta
    
    # RC releases
    npm version prerelease --no-git-tag-version --preid=rc
  • Merge the backport

  • Make sure you pull the latest stable branch:

    git checkout stable24
    git pull origin stable24
  • 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 v14.0.11 will be automatically added to the tag)

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

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

    • 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=v14.0.11

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

  • Rename milestone 💛 Next Patch (24) to v14.0.11 in https://github.com/nextcloud/spreed/milestones
    Unless last release of the stable branch:

    • ~~Create a follow up milestone for 💛 Next Patch (24) (Due date in ~4 weeks, ~4 days for beta/RC)~~ => EOL
    • Move all open PRs and issues from milestone v14.0.11 to 💛 Next Patch (24) => EOL, close
  • Close the v14.0.11 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

🚀 v15.0.6

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

  • Backport the changelog

    • Release 15.0.6 #9593
    • 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:
    # Normal patch releases
    npm version patch --no-git-tag-version
    
    # First beta releases
    npm version premajor --no-git-tag-version --preid=beta
    npm version prerelease --no-git-tag-version --preid=beta
    
    # Other beta releases
    npm version prerelease --no-git-tag-version --preid=beta
    
    # RC releases
    npm version prerelease --no-git-tag-version --preid=rc
  • Merge the backport

  • Make sure you pull the latest stable branch:

    git checkout stable25
    git pull origin stable25
  • 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 v15.0.6 will be automatically added to the tag)

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

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

    • 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=v15.0.6

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

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

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

🚀 v16.0.4

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.4 #9594
    • 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:
    # Normal patch releases
    npm version patch --no-git-tag-version
    
    # First beta releases
    npm version premajor --no-git-tag-version --preid=beta
    npm version prerelease --no-git-tag-version --preid=beta
    
    # Other beta releases
    npm version prerelease --no-git-tag-version --preid=beta
    
    # RC releases
    npm version prerelease --no-git-tag-version --preid=rc
  • 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.4 will be automatically added to the tag)

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

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

    • 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.4

    • 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.4 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.4 to 💘 Next Patch (26)
  • Close the v16.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

🚀 v17.0.0-rc.2

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

  • Backport the changelog

    • Release 17.0.0 rc.2 #9595
    • 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:
    # Normal patch releases
    npm version patch --no-git-tag-version
    
    # First beta releases
    npm version premajor --no-git-tag-version --preid=beta
    npm version prerelease --no-git-tag-version --preid=beta
    
    # Other beta releases
    npm version prerelease --no-git-tag-version --preid=beta
    
    # RC releases
    npm version prerelease --no-git-tag-version --preid=rc
  • 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.0.0-rc.2 will be automatically added to the tag)

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

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

    • 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.0.0-rc.2

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

  • Rename milestone 💙 Next RC (27) to v17.0.0-rc.2 in https://github.com/nextcloud/spreed/milestones
    Unless last release of the stable branch:

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

Metadata

Metadata

Assignees

Type

No type

Projects

Status

☑️ Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions