You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Target timeline
Scheduled feature freeze / Start of translation process:
Targeted translation completion date:
Approximate release date:
Current state:
Checklist
Assign this issue to the release shepherd who is in charge of managing this checklist.
Pin this issue
Ensure that all issues/PR targeted for this release are done by checking the Project board with the appropriate filter for this release. Remind main developers to review entries in Waiting on team state.
Agree to de-tag unfinished Issues/PRs.
Declare a freeze for code and website by updating this Issue and adding a comment. PRs can still be worked on and may get reviewed, but must not be merged unless agreed explicitly.
Check the needs documentation label for any outstanding PRs flagged for this release and remove that label if done.
Check ./Jamulus -h output against the Include-Client/Server-Commands.md pages and [man page (distributions/Jamulus.1)[(https://github.com/jamulussoftware/jamulus/blob/main/distributions/Jamulus.1). Update if necessary.
Open a Pull Request from next-release to release, set it as "Draft", sanity check for conflicts and any obvious problems.
Declare a full freeze of the next-release and release branch. No changes should be made from now on to ensure translators don't have to work twice.
Check if the list of translators in tools/create-translation-issues.sh. Make sure issue text is up-to-date. Add any URLs that will need localisation into the "New/Changed screenshots" section.
Create a translation issue for each language with tools/create-translation-issues.sh using web argument (see notes in script).
If anyone finds critical issues now, all translators must be made aware of them and all languages should be updated.
Start App translations
Generate .ts files in main via lupdate
Check if the list of translators in tools/create-translation-issues.sh is up-to-date
Create a translation issue for each language with tools/create-translation-issues.sh using app argument.
Contact emlynmac for signing on macOS and upload signed binary from his repo to ours.
Do a smoke test for Windows/Mac/Linux -- Do the binaries start/connect properly? Can earlier Jamulus versions properly connect to a server based on the new release?
Update download links on the website by editing _config.yml in next-release
Disable branch protection rule of the release branch by clicking on "Edit" on the Branches page and adding a _ behind release.
Publish Website release by squashing and merging next-release into release
Enable branch protection rule of the release branch after the site and the .po files are published by removing the _ from the branch protection rule you edited on the Branches page.
Announce the new release with a summary of changes (+ link to the changelog for details) and a link to the download page
On Github Discussions in the Announcements section. Lock the announcement thread. Pin the thread. Unpin and lock release candidate thread.
On Facebook in the group "Jamulus (official group)". Turn off replies.
Trigger the update notification by updating both Update Check Servers with the new version (@pljones for update02, email corrados for update01)
[Prepare Jamulus.pro (dev suffix) and ChangeLog (add a header) for the next release
Check that all Issues and PRs tagged for this release are in Done/Closed state.
Close the release milestone in both jamulus and jamuluswebsite repos
Create a milestone for the next minor release in jamulus and jamuluswebsite repos
Target timeline
Scheduled feature freeze / Start of translation process:
Targeted translation completion date:
Approximate release date:
Current state:
Checklist
needs documentation
label for any outstanding PRs flagged for this release and remove that label if done.next-release
to release, set it as "Draft", sanity check for conflicts and any obvious problems.next-release
andrelease
branch. No changes should be made from now on to ensure translators don't have to work twice.tools/create-translation-issues.sh
. Make sure issue text is up-to-date. Add any URLs that will need localisation into the "New/Changed screenshots" section.tools/create-translation-issues.sh
usingweb
argument (see notes in script)..ts
files in main vialupdate
tools/create-translation-issues.sh
is up-to-datetools/create-translation-issues.sh
usingapp
argument.tools/checkkeys.pl
).qm
files vialrelease Jamulus.pro
tools/get_release_contributors.py
Jamulus.pro
and add the release date to the Changelog header and commitr3_y_z
latest
and push._config.yml
innext-release
release
branch by clicking on "Edit" on the Branches page and adding a_
behindrelease
.next-release
intorelease
release
branch after the site and the.po
files are published by removing the_
from the branch protection rule you edited on the Branches page.Jamulus.pro
(dev
suffix) and ChangeLog (add a header) for the next releaseThe text was updated successfully, but these errors were encountered: