First, change to the branch intended for the previous Fedora release. Then create a new branch for the upcoming release and change to the branch:

git checkout -b newbranch

Assuming that the content development for the upcoming release happened in the master branch, which is different from the release branch, you should merge the updates from the master branch:

git merge master

After successful merging, check that the resource configuration in the .tx/config file is still up-to-date and applies to the current documentation. Especially pay attention to changed, moved or removed chapters in your document. If you need to remove an unused resource, run the following command:

tx delete -r documentation.resource

For example, if you want to remove the resource Amateur_Radio from the Fedora Release Notes, execute the following command:

tx delete -r fedora-release-notes.Amateur_Radio

When you are done with all necessary changes, follow the usual procedure with updating POT files and pushing and pulling translations that is described in Section 7.9, “Updating POT Files” and Section 7.10, “Pushing and Pulling Translations”.