Skip to content

Commit

Permalink
Update LOTUS_RELEASE_FLOW.md
Browse files Browse the repository at this point in the history
Co-authored-by: Steve Loeppky <[email protected]>
  • Loading branch information
rjan90 and BigLep committed Aug 12, 2024
1 parent 2175cee commit d350be7
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions LOTUS_RELEASE_FLOW.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,6 +96,7 @@ The specific steps executed for Lotus software releases are captured in the [Rel
- For regular (i.e., no critical security patch) releases with no accompanying network upgrade, the RC period is typically around 1 week.
- For releases accompanying network upgrades, the release candiadte period is a lot longer to allow for more extensive testing, usually around 5 to 6 weeks.
- Releases rushing out a critical security patch will likely have an RC period on the order of hours or days, or may even forgo the RC phase. To compensate for the release speed, these releases will include the minimum delta necessary, meaning they'll be a patch on top of an existing release rather than taking the latest changes in the `master` branch.
- Releases rushing out a critical security patch will likely have an RC period on the order of hours or days, or may even forgo the RC phase. To compensate for the release speed, these releases will include the minimum delta necessary, meaning they'll be a patch on top of an existing release rather than taking the latest changes in the `master` branch.

## Security Fix Policy

Expand Down

0 comments on commit d350be7

Please sign in to comment.