Won't Do
Details
Assignee
Zak BurkeZak BurkeReporter
Zak BurkeZak BurkePriority
P2Development Team
ProkopovychRelease
Lotus (R1 2022) Hot Fix #1TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Zak Burke
Zak BurkeReporter
Zak Burke
Zak BurkePriority
Development Team
Prokopovych
Release
Lotus (R1 2022) Hot Fix #1
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 1, 2022 at 8:50 PM
Updated June 16, 2022 at 10:54 AM
Resolved June 7, 2022 at 3:28 AM
Backport recent translations for the locale
zh_TW
to Lotus.Given you have a repository cloned and checked out to its Lotus release branch, e.g.
b7.2
,b10.1
, etc., it's straightforward to collect the changes that have happened on master into a patch and then add those changes to the release branch:At this point, you should inspect the changes with
git diff
to confirm that no keys are being removed, i.e. that the changes are backwards compatible. If the changes look compatible, create a new branch, commit the changes, push them, and issue a PR targeted at the release branch. Once that PR is merged, you can then publish a patch release from that branch as usual. This closely mirrors our regular patch release process; the only difference is that changes will be applied viagit apply
instead ofgit cherry-pick
.