[Initiatives.wiki] Update DevOps with Flatpak

[Jordan Petridis <jpetridis src gnome org>]

commit 0a9da1d73568044aa2d845a9964a7a10306c8e18
Author: Jordan Petridis <jpetridis gnome org>
Date:   Mon Dec 2 15:21:56 2019 +0000

    Update DevOps with Flatpak

 DevOps-with-Flatpak.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)
---
diff --git a/DevOps-with-Flatpak.md b/DevOps-with-Flatpak.md
index 1a51dea..973371d 100644
--- a/DevOps-with-Flatpak.md
+++ b/DevOps-with-Flatpak.md
@@ -343,4 +343,8 @@ Which assumes that if there is a profile set, it's going to be for development.
 This almost does what we would want, but not quite. If you build this way it will always try to fetch your 
modules from the source specified in the manifest, but we want to use our local checkout instead. This is 
fine if you only build the `master` branch but MRs need to be able to change the source to their checkout.
 
 To achieve this we use the `--stop-at=module` argument which will build all of the dependencies up to your 
module from the manifest. Then we take over and need to install the application ourselves. This is why your 
config
-s `CONFIGURE_ARGS` variable needs to be kept in sync with your module's config options in the manifest.
\ No newline at end of file
+s `CONFIGURE_ARGS` variable needs to be kept in sync with your module's config options in the manifest.
+
+**A previous version of the template had some extra `review` and `stop_review` jobs, what happened to those.
+
+They have been deprecated and replaced by a simpler feature that provides the same function. It should 
simplifies both the template setup, and the backend setup needed to run the previous jobs. For more you can 
refer to this 
[commit](https://gitlab.gnome.org/GNOME/citemplates/commit/544836ee58f91a735616ecb04ea857a66d2bb699)
\ No newline at end of file