Thread by @CryptoDelegate

There is a small bug in #Tezos Babylon. What do we do? Fix, resubmit, and start the whole vote process over adding many months to the update or fix the bug and promote a modified code version on the current schedule? (1/x)

https://twitter.com/awasunyin/status/1175035980610494466

Core question: How do we treat this issue type in the future? This situation will come up many times going forward & the outcome of Babylon will set the precedent. This means we may need to fundamentally amend the protocol upgrade process flow. Are we willing to do this? (2/x)

Does bug fix change fundamental reason why people voted ”yes” or is it a true code glitch? If Yes, start over on a new protocol proposal. If no, fix the bug & start testing phase over again. No code should ever pass the testing phase without 100% success from the start. (3/x)

If we do decide now to change the way in which protocol upgrades are handled then this also deserves a vote to officially amend the approval flow to allow for code bug fixes to reiterate and repeat the testing phase until the code is fully tested and then promoted. (4/x)

*Option A: stalls innovation.
*Option B: to simply amend & promote is not acceptable as it does not allow for a full retest of the new code.
*New Option C: fix, revert to test phase, repeat until perfect, then vote promote. Also update official #Tezos amendment workflow. (5/5)