-
Notifications
You must be signed in to change notification settings - Fork 511
Closed
Description
💺 Preparation
- Check all milestones don't have priority issues still open
- Check there are no pending backports: https://github.com/nextcloud/spreed/pulls?q=is%3Apr+label%3Abackport-request+is%3Aclosed
- On major releases create a test package and check if a new development file needs to be added to the packaging exclude list in
Makefilemake appstore
- Create a PR against master
CHANGELOG.mdwith the changelog of all milestones that are subject to the release - Merge the PR
🚀 v15.0.0-beta.2
Start with the oldest version here, so the appstore and github releases show the newest version as "Last release"
- Make sure you pull the latest stable branch:
git checkout master git pull origin master
- 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
- Create tag
make create-tag version=15.0.0-beta.2
- Push the git tag to https://github.com/nextcloud-releases/spreed
git push releases v15.0.0-beta.2
- Mark the tag as a (pre-)release in https://github.com/nextcloud-releases/spreed/releases
- Add the respective
CHANGELOG.mdsection
- Add the respective
- Mark the tag as a (pre-)release in https://github.com/nextcloud/spreed/releases
- Add the respective
CHANGELOG.mdsection - 🛑 Do NOT re-upload the binary here.
- Add the respective
- Check that the GitHub Action started: https://github.com/nextcloud-releases/spreed/actions
- Rename milestone
💚 Next Beta (25)tov15.0.0-beta.2 - Unless last release of the stable branch:
- Create a follow up milestone for
💚 Next Beta (25)(Due date in ~1 weeks) - Move all open PRs and issues from milestone
v15.0.0-beta.2to💚 Next Beta (25)
- Create a follow up milestone for
- Close the
v15.0.0-beta.2milestone - In case there were security issues fixed ping the security team