From 64fe8f30d9b75b78f6dd81359b14f5ac95abce93 Mon Sep 17 00:00:00 2001 From: Tom Bereknyei Date: Sat, 12 Aug 2023 20:29:05 -0400 Subject: [PATCH] fix: minor fixes --- rfcs/0136-stabilize-incrementally.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rfcs/0136-stabilize-incrementally.md b/rfcs/0136-stabilize-incrementally.md index e8972beca..e626f80ee 100644 --- a/rfcs/0136-stabilize-incrementally.md +++ b/rfcs/0136-stabilize-incrementally.md @@ -180,7 +180,7 @@ To stabilize a piece of functionality (experimental -> stable in flowchart in li - **Whole feature flag, not part of a feature flag** - It should be possible to enable just the experimental that is ready for stabilization *in isolation*, without also enabling other unstable functionality that is not ready for stabilization. + It should be possible to enable just the experimental feature that is ready for stabilization *in isolation*, without also enabling other unstable functionality that is not ready for stabilization. We are not allowed to propose to stabilize part of an experimenal feature and do so immediately. We have to first break out the candidate functionality to be stabilized so it is just guarded by one feature flag. @@ -379,7 +379,7 @@ None at this time. # Future work [future]: #future-work -Generalization features to work without Flakes, like pure eval and search, might be desired by the Flake-skeptic faction, but is purposely left as future work in order to not delay stabilization. +Generalizing features (live pure eval and search) to work without Flakes might be desired by the Flake-skeptic faction, but is purposely left as future work in order to not delay stabilization. General feature stability lifecycle: https://discourse.nixos.org/t/potential-rfc-idea-stability/27055