Open nickvergessen opened 3 years ago
Start with the oldest version here, so the appstore and github releases show the newest version as "Last release"
CHANGELOG.md
of higher versionsappinfo/info.xml
git checkout stableX.Y
git pull origin stableX.Y
make dev-setup build-js-production
make release version=X.Y.Z
git push releases vX.Y.Z
CHANGELOG.md
sectionbuild/artifacts/
CHANGELOG.md
sectionCHANGELOG.md
sectionmake release version=X.Y.Z
π Next Patch (X)
to vX.Y.Z
π Next Patch (X)
(Due date in ~4 weeks)vX.Y.Z
to π Next Patch (X)
vX.Y.Z
milestone
Get branches/versions to release from https://github.com/nextcloud/spreed/milestones
πΊ Preparation
New in Talk TX
entries in theTalk updates β
conversationMakefile
CHANGELOG.md
with the changelog of all milestones that are subject to the release - [ ]π vX.Y.Z
Start with the oldest version here, so the appstore and github releases show the newest version as "Last release"
stableX.0
branch make sure to:l10n/
folder fromstableX
and commit itCHANGELOG.md
of higher versionsappinfo/info.xml
package.json
. The following command will return a new version name, make sure it matches what you expect:v
invX.Y.Z
will be automatically added to the tag)Make sure you have access rights to the remote repository, and it is set up on your machine:
[ ] Prepare a (pre-)release in https://github.com/nextcloud/spreed/releases/new?tag=vX.Y.Z
CHANGELOG.md
section from merged PR[ ] Use the Generate release notes button and wrap the output result into
π Next Patch (X)
tovX.Y.Z
in https://github.com/nextcloud/spreed/milestones Unless last release of the stable branch:π Next Patch (X)
(Due date in ~4 weeks, ~4 days for beta/RC)vX.Y.Z
toπ Next Patch (X)
: https://github.com/nextcloud/spreed/issues?q=is%3Aissue%20state%3Aopen%20milestone%3AvX.Y.ZvX.Y.Z
toπ Next Patch (X)
: https://github.com/nextcloud/spreed/issues?q=is%3Apr%20state%3Aopen%20milestone%3AvX.Y.ZvX.Y.Z
milestone