ref-fvm
ref-fvm copied to clipboard
Create updated release process
Done Criteria
There is a clear set of documented steps that a "release engineer" can follow for cutting.
Outdated documents (example maybe) are updated or removed.
Why Important
Release processes as tribal knowledge have the problem of:
- Doesn't survive if tribe members leave or are away. Others "groping around" may make mistakes which takes more time later.
- Less likely that lessons learned or improvements will be captured and passed on.
User/Customer
Maintainers
Notes
- During the nv23 release process, it seemed that we didn't have the list of steps needed for cutting a release, especially when older versions also needed to be updated. See comment in https://github.com/filecoin-project/ref-fvm/issues/2013#issuecomment-2163858925 .
- There are steps around fvm_integration_tests. See https://github.com/filecoin-project/ref-fvm/issues/2013#issuecomment-2166834018 and https://filecoinproject.slack.com/archives/C029MT4PQB1/p1718240205547329
- There is currently this document form a couple of years ago: https://github.com/filecoin-project/ref-fvm/blob/master/doc/testnet-release-process.md that should be updated or removed.