Do not batch updates for branched releases

[bowlofeggs]

It was suggested on the devel list that Bodhi should not batch updates for branched releases, because it increases the number of updates that miss the compose deadlines.

Here's the thread with a more detailed explanation:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/PCDKEGP2UIPKSYR4F62FJFK5I362EF64/#PCDKEGP2UIPKSYR4F62FJFK5I362EF64

[bowlofeggs]

The code around Bodhi's state machine is… let's say… spaghetti held together by duct tape. We could solve this by adding a bit more spaghetti and duct tape, but it might be easier to get it right if we fix
#1723 first. I wouldn't say that's necessarily a requirement, but I do think this could be painful and error prone without it.

[bowlofeggs]

Until we have this, a reasonable workaround is for release engineering to run the bodhi-dequeue-stable CLI tool before running the final push to stable before building "significant" composes. For example, if final freeze is about to happen, it would be good to do this:

1. Run sudo -u apache /usr/bin/bodhi-dequeue-stable.
2. Run a mash on the branched release.

The bodhi-dequeue-stable hunts the db for all batched updates and marks them for stable. Unfortunately, it does not have any arguments, so doing this will have the side effect of also marking batched updates for stable in all other releases. In my opinion, that's a minor side effect and is worth it.

[bowlofeggs]

We are dropping the batching feature in #2977 so I will close this issue.