The builds in your side-tag will be moved into ``<your-side-tag>-signing-pending`` and the update will be put in the ``Pending`` status.
RoboSignatory is notified that your builds landed in this tag by our message bus, it will take them, sign them and move them to the ``<your-side-tag>-testing-pending`` tag.
Bodhi is notified that your builds were signed and moved to this tag by our message bus, it will mark the builds as signed and once all the builds have been signed, it will move the update to the ``Testing`` status.
Tests will be run, their results will be reported to ResultsDB which will announce these results, making Greenwave consult each `gating.yaml` file to see if all the required criteria of these builds have been met or not. If they have, Greenwave will send a message to the message bus announcing its decision.
Bodhi will listen to the bus for the decision made by Greenwave about updates. Upon receiving them it will push the corresponding update into the final Koji tag (i.e. the stable tag) and mark the update as ``Stable``.
At this point, your builds have landed in the stable tag in Koji, it is therefore available in the buildroot for anyone to use and rely on and the corresponding Bodhi update has been marked as stable.
Note that the update being `stable` does not mean you will be able to install it via dnf/yum. It means the build is available in the Rawhide buildroot. It will be pushed to the mirror once the next Rawhide compose succeeds.
If you have created a side-tag and have no use for it (and did not create an update for it), please remove it so it does consume resources on the build infrastructure. You can simply remove side-tags you have created using ``fedpkg remove-side-tag`` and you can list your side tags using ``fedpkg list-side-tags --user=<username>``.
Simplified diagram of the multi-builds updates workflow