From 1d893d66303311f8eb35763277883392b27a18b1 Mon Sep 17 00:00:00 2001 From: Alejandro Date: Tue, 26 Sep 2023 13:03:46 +0200 Subject: [PATCH] Completed TODO in code --- LOTUS_RELEASE_FLOW.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LOTUS_RELEASE_FLOW.md b/LOTUS_RELEASE_FLOW.md index 4a327125a7b..8bb02d3c599 100644 --- a/LOTUS_RELEASE_FLOW.md +++ b/LOTUS_RELEASE_FLOW.md @@ -73,7 +73,7 @@ All releases under an odd minor version number indicate **feature releases**. Th Feature releases include new development and bug fixes. They are not mandatory, but still highly recommended, **as they may contain critical security fixes**. Note that some of these releases may be very small patch releases that include critical hotfixes. There is no way to distinguish between a bug fix release and a feature release on the "feature" version. Both cases will use the "patch" version number. -We aim to ship a new feature release of the Lotus software from our development (master) branch every 3 weeks, so users can expect a regular cadence of Lotus feature releases. Note that mandatory releases for network upgrades may disrupt this schedule. For more, see the Release Cycle section (TODO: Link). +We aim to ship a new feature release of the Lotus software from our development (master) branch every 3 weeks, so users can expect a regular cadence of Lotus feature releases. Note that mandatory releases for network upgrades may disrupt this schedule. For more, see the [Release Cycle section](#release-cycle). ### Examples Scenarios