doc: include stage 0 in patch release process.
Co-Authored-By: Alan Shaw <alan.shaw@protocol.ai>
Steven Allen committed
Aug 5, 2019 at 05:21 UTC
d6abfb8016e0478d807a219786f040a03fbbad07
1 file changed
+1
-1
docs/releases.md
+1
-1
@@ -63,7 +63,7 @@ If we encounter a serious bug in the stable latest release, we will create a pat
63
64
Patch releases will usually follow a compressed release cycle and should take 2-3 days. In a patch release:
65
66
-1. Internal testing will be compressed into a few hours - ideally less than a day.
66
+1. Automated and internal testing (stage 0 and 1) will be compressed into a few hours - ideally less than a day.
67
2. Stage 2 will be skipped.
68
3. Community production testing will be shortened to 1-2 days of opt-in testing in production (early testers can choose to pass).
69