[flatpaks/flatpak-runtime] f45: Remove a part from the README that's not needed anymore

[Tomas Popela <tpopela@redhat.com>]

            A new commit has been pushed.

            Repo   : flatpaks/flatpak-runtime
            Branch : f45
            Commit : 78e284481fcdd231de6ecc01b524ce8fdb3a4395
            Author : Tomas Popela <tpopela@redhat.com>
            Date   : 2022-12-13T16:50:55+01:00
            Stats  : +11/-14 in 1 file(s)
            URL    : https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/78e284481fcdd231de6ecc01b524ce8fdb3a4395?branch=f45

            Log:
            Remove a part from the README that's not needed anymore

The patch was merged and is part of current release.

---
diff --git a/README.md b/README.md
index 76cb475..785579b 100644
--- a/README.md
+++ b/README.md
@@ -78,30 +78,27 @@ Once done, please do the following steps in this exact order:
  3. Replace all occurrences of an old Fedora release with the new one in `modules/flatpak-runtime` - i.e. [f34 -> f35](https://src.fedoraproject.org/modules/flatpak-runtime/c/76972d6a76390f21e4e70fd960773e597d810de3) and [f35 -> f36](https://src.fedoraproject.org/modules/flatpak-runtime/c/ff05f48642694c1aaf70df1fdc0a5a6d8fb30939)
  4. Bump the required freedesktop and GNOME Flatpak SDKs versions if required in
     `tools/generate-files.sh`
- 5. Prepare the tooling - we have to apply patches from
-    https://pagure.io/modularity/fedmod/pull-request/112 to get a working
-    environment.
- 6. Download the metadata for a new Fedora release with `fedmod  --dataset=f36
+ 5. Download the metadata for a new Fedora release with `fedmod  --dataset=f36
     fetch-metadata` (replace f36 with the new release). You might need to update
     the `/etc/fedmod/fedora.yaml` file and add a new release there. If the new
     Fedora is already released, then duplicate the f36 part under the `releases:`
     section [example](https://pagure.io/fork/tpopela/modularity/fedmod/c/0df9ced507b8e9ce76a62cc35015c403073873ca). If the new version isn't released yet, do the same, but replace
     `fedora-stable` with `fedora-branched`.
- 7. Run `make new-runtime`. In case of any problems you will need to update the
+ 6. Run `make new-runtime`. In case of any problems you will need to update the
     `tools/resolve-files.py` to adapt it for new library versions and so on.
     Once the new runtime files are generated, consult the content of it and again
     modify `tools/resolve-files.py` to exclude any libraries, binaries or packages
     if needed.
- 8. Try to build the module and container locally with `flatpak-module local-build`
+ 7. Try to build the module and container locally with `flatpak-module local-build`
     to verify that the changes from previous step are working.
- 9. Commit the change and do the official build with `fedpkg module-build -w`
+ 8. Commit the change and do the official build with `fedpkg module-build -w`
     followed by `fedpkg flatpak-build`
- 10. Update and build modules/flatpak-common - i.e. [f35 -> f36](https://src.fedoraproject.org/modules/flatpak-common/c/17aeabbc448e3805a85e2c9313d40c608bc2611b?branch=f36)
+ 9. Update and build modules/flatpak-common - i.e. [f35 -> f36](https://src.fedoraproject.org/modules/flatpak-common/c/17aeabbc448e3805a85e2c9313d40c608bc2611b?branch=f36)
      and do an official build of with with `fedpkg module-build -w`. If you will
      hit any build problems you might want to try to build the module locally
      against the local packages with `flatpak-module build-module`. For that you
      have to [setup your environment](https://docs.fedoraproject.org/en-US/flatpak/troubleshooting/#_rebuilding_a_module_against_a_local_component)
- 11. Update modules/flatpak-sdk - i.e. [f35 -> f36](https://src.fedoraproject.org/modules/flatpak-sdk/c/83742941dc2b7e5c0cad78cb25c3ed9cc1b17d1a?branch=f36)
+ 10. Update modules/flatpak-sdk - i.e. [f35 -> f36](https://src.fedoraproject.org/modules/flatpak-sdk/c/83742941dc2b7e5c0cad78cb25c3ed9cc1b17d1a?branch=f36)
      and build it with `fedpkg flatpak-build` (no need to build a module for
      flatpak-sdk). On the other hand if you will need to make any changes to the
      flatpak-runtime defitions (to add more packages that are not pulled on
@@ -109,12 +106,12 @@ Once done, please do the following steps in this exact order:
      then you will need to again do a module build of flatpak-runtime and once
      it's done, you can start a new `fedpkg flatpak-build` of flatpak-runtime
      and flatpak-sdk.
- 12. Create a bodhi update for the new runtime and SDK - i.e. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2022-16d56b1bde
- 13. Move all applications to the new runtime - i.e. [Evince Flatpak moving from f35 -> f36 ](https://src.fedoraproject.org/flatpaks/evince/c/7fccbf4bb8cea2d258226dfbe490327c59a44564?branch=stable)
+ 11. Create a bodhi update for the new runtime and SDK - i.e. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2022-16d56b1bde
+ 12. Move all applications to the new runtime - i.e. [Evince Flatpak moving from f35 -> f36 ](https://src.fedoraproject.org/flatpaks/evince/c/7fccbf4bb8cea2d258226dfbe490327c59a44564?branch=stable)
      and build it with `fedpkg module-build -w` and `fedpkg flatpak-build`. Also
      it's a good time to update the `finish-args` from Flathub and update them
      in Fedora if needed. Also update the module packages with the changes from the new Fedora release - i.e. `fedmod rpm2flatpak --flatpak-common --force --flathub=gimp gimp`.
      You might find [the following howto useful](https://docs.fedoraproject.org/en-US/flatpak/tutorial/#_creating_application_yaml_and_container_yaml).
- 14. Create bodhi updates for moved applications
- 15. Switch to the new runtime for Anaconda - i.e. [f34 -> f35](https://pagure.io/pungi-fedora/c/d2e477b48368599834d6ec4adcc79f7115d98627?branch=main)
- 16. Once everything is moved, deprecate the old runtime and SDK - TBD
+ 13. Create bodhi updates for moved applications
+ 14. Switch to the new runtime for Anaconda - i.e. [f34 -> f35](https://pagure.io/pungi-fedora/c/d2e477b48368599834d6ec4adcc79f7115d98627?branch=main)
+ 15. Once everything is moved, deprecate the old runtime and SDK - TBD