Define release strategy for FilecoinWarmStorageServices

[rjan90]

Overview

Recent discussions around contract upgrades have highlighted the we now need a formal release strategy. A couple of things we need to define are:

• Versioning Strategy
• Breaking Change Management
  • Define what constitutes a breaking change
  • Timeline requirements for advance notice of breaking changes
• Communication & Documentation
  • Release notes template and process
  • Downstream notification process

[BigLep]

Some pointers that have some more info about the current process:

• All the deployments steps that were needed for M3 are linked from M4 Release checklist #254 (comment)
• chore: FWSS Contract Upgrade Dependencies Document #224 is the start of a document for the steps that need to be taken for updating dependencies
• feat: add automated draft release on version change pdp#195 has some relevant discussion as well

Note:

• this contract repo currently relies on git submodules per https://github.com/FilOzone/filecoin-services/tree/main/service_contracts/lib
• there is a proposal to switch to a monorepo: Proposal: monorepo & no git submodules #229