I personally think the concerns in Comment #1 do not apply, as we are not talking about dot releases or updates for regular releases, but for ESR jumps.
Bug 1529943 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I personally think the concerns in Comment #1 do not apply, as we are not talking about dot releases and probably also not about updates for regular releases, but for ESR jumps. Let us consider a Company, which is using Firefox 68 ESR and has finished their testing for Firefox 78 ESR only after Firefox 91 ESR has been released. They change the pin policy to 78 and nothing happens. Their instances do not update. I would not consider this a failure of the pin policy. To overcome this, they can manually deploy Firefox 78. This is even valid, if a company is indeed using the pin policy on regular releases.
I personally think the concerns in Comment #1 do not apply, as we are not talking about dot releases and probably also not about updates for regular releases, but for ESR jumps. Let us consider a Company, which is using Firefox 68 ESR and has finished their testing for Firefox 78 ESR only after Firefox 91 ESR has been released. They change the pin policy to 78 and nothing happens. Their instances do not update. I would not consider this a failure of the pin policy. To overcome this, they can manually deploy Firefox 78 ESR. This is even valid, if a company is indeed using the pin policy on regular releases.