jamulussoftware / jamulussoftware/jamulus
Update to release process template to cut beta for screenshots
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 248
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 9
Description
> - [ ] Finish App translations
> - [ ] Review translation PRs according to [release process checklist](https://jamulus.io/contribute/Release-Process#3-update-the-ts-files-returned-by-translators)
> - [ ] 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](https://github.com/jamulussoftware/jamuluswebsite/blob/release/contribute/en/Release-Process.md#website-check-links)
>
> OK, so another thing we need to fix in the release process template is cutting another beta between `Finish App translations` and `Finish Website translations` so that the beta can be used for the screenshots.
_Originally posted by @pljones in [#3443](https://github.com/jamulussoftware/jamulus/issues/3443#issuecomment-3293182212)_
Contributor guide
Research direction
Start with the release process checklist linked in the issue and locate the template section containing the App and Website translation steps. Add a beta-cut step between those sections so the beta can be used for screenshots, while retaining the existing translation and tools/checkkeys.pl checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100