feat(release strategy): Add archway protocol versioning and release strategy

[shahbazn]

This is a collaborative PR to converge on a comprehensive release strategy for archway protocol.

• Please feel free to add new sections to the PR as needed
• To change existing sections please add ideas as comments. Once an agreement has reached in comments, please free to push changes to existing sections.

[zanicar]

The final scenario needs to be further reviewed and discussed...

I completely see and understand the validity of such a scenario, but I do have concerns about running mainnet and public testnet on "different versions"; in this case it is something small and insignificant enough that it does not warrant an upgrade to mainnet. However, we should attempt to prevent any such scenarios from occurring at any sort of frequency as it may lead to complacency where the divergence between the two may come back to bite us;

For this reason I believe that if any such scenarios are identified or do occur, it should be taken into consideration for our formal verification process to detect and prevent any future such occurrences; i.e. any fixes required to testnet should precede deployment to mainnet so that both networks run the same version post release upgrade;

[shahbazn]

The final scenario needs to be further reviewed and discussed...

I completely see and understand the validity of such a scenario, but I do have concerns about running mainnet and public testnet on "different versions"; in this case it is something small and insignificant enough that it does not warrant an upgrade to mainnet. However, we should attempt to prevent any such scenarios from occurring at any sort of frequency as it may lead to complacency where the divergence between the two may come back to bite us;

For this reason I believe that if any such scenarios are identified or do occur, it should be taken into consideration for our formal verification process to detect and prevent any future such occurrences; i.e. any fixes required to testnet should precede deployment to mainnet so that both networks run the same version post release upgrade;

Agreed. The scenario merely presents an example hot-fix situation which is un-planned and unexpected. In normal ideal operations these situations will not occur.

[spoo-bar]

As mentioned in the above comment, for this situation, I think it would be best to export current constantine-1 state and adjust the token supply and start constantine-2 with the fixed state

[shahbazn]

This network is being used by dapp developers as a canary network. My only concern here is, would doing a state export imply that dapp developers would need to deploy all the daps again?

[spoo-bar]

No idts. export and import also handles the contract binaries and its state as well

[shahbazn]

Verifying the porposed workflow, will update the scenerio accordingly

[loverdos]

LGTM (pending fixing the automated checks)