Prepare Release 3.9.0

[ann0see]

Target timeline

Phase	Target date	Original	Actual
Scheduled feature freeze / Start of translation process	2022-07-08	2022-07-01	2022-07-03
Targeted translation completion date	2022-07-22	2022-07-08	2022-07-081
Approximate release date	2022-07-29	2022-07-21	2022-07-29

Reminder: see jamulussoftware/jamuluswebsite#711

Current state: Released

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 if the list of translators in tools/create-translation-issues.sh. Make sure the details are up-to-date. Check against https://github.com/orgs/jamulussoftware/teams/translators and confirm that is up-to-date.
• Update the Changelog
• Tag a beta release
  • Inform emlynmac for signing on macOS, and upload signed binary from his repo to ours
  • Announce the beta release on Github Discussions. Pin the thread.
  • Get feedback on the stability and resource usage (memleaks?, crashes?, installation issues?) of the beta release
• Start App translations
  • Generate .ts files in master 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.
  • !! Notify translators about the new location of the translation files (.ts): They are now in src/translation. (Refactoring: move src/res/translation to src/translation #2576)
• Check ./Jamulus -h output against the Include-Client/Server-Commands.md pages (wiki/en) and man page (distributions/Jamulus.1). Update if necessary.
• Start Website translations
  • Check for broken links
  • 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 issue text in in tools/create-translation-issues.sh 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.
• Finish App translations
  • Review translation PRs according to release process checklist
    • (NOTE: This check produces output that does not assist with the release proces) Check for conflicting accelerator keys (see tools/checkkeys.pl)
  • Wait for all PRs to be merged (missing translations will revert to English automatically).
    • BR: Update pt_BR app translation for r3.9.0 #2728
    • CN: Update translation_zh_CN.ts #2719
    • DE: Partly update de_DE app translation for r3.9.0 #2748
    • ES: Update es_ES app translation for 3.9.0 #2706
    • FR: Some more directory server discovered in the french app translation... #2729
      • additional: Some more directory server discovered in the french app translation... #2729
    • KR: Add Korean translation #2685 (outside releases process)
    • NL: Update nl_NL app translation for 3.9.0 #2708
    • PL: Update pl_PL app translation for 3.9.0 #2735
      • merged with outstanding comments
    • PT: Update pt_PT app translation for 3.9.0 #2747
      • merged with outstanding comments
    • SK: Update sk_SK app translation for 3.9.0 #2732
    • No Swedish translation
  • Generate .qm files via lrelease Jamulus.pro
• Check the milestone for mergable stuff again
• Update the Changelog
• Tag a release candidate
  • Inform emlynmac for signing on macOS and upload signed binary from his repo to ours.
  • 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 version number in Jamulus.pro and add the release date to the Changelog header and commit
• Update the Changelog
• Finish Website translations
  • Wait for all PRs to be merged (missing translations (DE, IT, PT) will revert to English automatically)
    • NL: Update nl web translation for 3.9.0 jamuluswebsite#784
    • FR: Update fr web translation for 3.9.0 jamuluswebsite#780
    • ES: Update es web translation for 3.9.0 jamuluswebsite#785
  • Check for broken links
• Tag this commit as r3_y_z
  • Wait for the build to complete
  • 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?
  • Force tag that tag as latest and push.
  • Upload the artifacts to SourceForge and set defaults.
  • Update download links on the website by editing _config.yml in next-release
  • Publish Website release by merging next-release into release
• Announce the new release with a summary of changes (+ link to the changelog for details) and a link to the download page
  • Candidates for extra mentions: Changed Mac compatibility (<= 10.14 needs legacy now)
  • Windows Qt6 preview build (if done)
  • 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
• 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 (Release retrospective for 3.9.0 (Developers/Translators/Contributors/Users) #2766)

Footnotes

1. Some web site translations are to be completed after release:

   • Update pt web translation for 3.9.0 jamuluswebsite#779
   • Update it web translation for 3.9.0 jamuluswebsite#777
   • Update de web translation for 3.9.0 jamuluswebsite#774
   ↩

[ann0see]

Opened as requested by @hoffie

[ann0see]

Todo:

• Announce the iOS and arm .deb files too.
• Document ARM release in Checklist

[gilgongo]

We seem to be a bit far from a release at the moment, unless we de-tag a lot of stuff? There are 24 things in the backlog apparently not even being worked on, for example: https://github.com/orgs/jamulussoftware/projects/2?card_filter_query=milestone%3A%22release+3.9.0%22

Of course, if some of those are being worked on, please will those responsible update the project status, since without that we can't really shepherd the release.

[ann0see]

Probably it's worth doing a radical de-tag for stuff we don't think are ready or doable.

[ann0see]

@jamulussoftware/maindevelopers I'd like to move the release forward. Can we decide to de-tag some of the things in the milestone?

[ann0see]

@dtinth @Rob-NY There are still some JSON-RPC related open issues. Can you take care of them?

[pljones]

Linked jamulussoftware/jamuluswebsite#711 and removed 3.9.0 from that issue.

[pljones]

I've added target dates now. Hopefully the state of the code should be pretty stable by the end of the week and we won't hit too many bumps getting the translations in.

[pljones]

OK, I'm declaring the code freeze now for any changes requiring translation.

[pljones]

• Could someone (@gilgongo? if you're not available for this, please shout) check the "needs documentation" state on the marked tickets, please: milestone:"Release 3.9.0" label:"needs documentation"

If the documentation is complete, please remove the label. Thanks!

• Same with Check ./Jamulus -h output against the Include-Client/Server-Commands.md pages (wiki/en) and man page (distributions/Jamulus.1). Update if necessary. -- could someone who knows the documentation repo take that, please.

[ann0see]

We need to tell macOS users about the possibility they need to use the legacy build from now on on Mojave or earlier.

[pljones]

• Check if the list of translators in tools/create-translation-issues.sh is up-to-date

Oops, I missed that. Do we have somewhere to check against?