Define release strategy for FilecoinWarmStorageServices

[rjan90]

Done Criteria

This repo has public documentation on:

• Versioning Strategy
• Breaking Change Management
  • Define what constitutes a breaking change
  • Timeline requirements for advance notice of breaking changes
• How to perform a release
  • Scripts to take or steps to run
  • Release notes template and process
  • Downstream notification process

This also encompasses doing any setup of things like release-please in support of the release process.

Why Important

1. Being able to quickly and safely deploy changes is critical for release features and for our operational posture to respond to issues.

User/Customer

Maintainers

Notes

• This makes sense to do after the Monorepo setup/execution #360
• Define release strategy for FilecoinWarmStorageServices #212 (comment) has notes about steps that have been taken before the monorepo conversion.

[BigLep]

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

• All the deployments steps that were needed for M3 are linked from M3.5 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