summaryrefslogtreecommitdiff
path: root/docs/internals/release-process.txt
diff options
context:
space:
mode:
authorTom V <tom@viner.tv>2014-11-21 16:43:39 +0000
committerTim Graham <timograham@gmail.com>2014-11-21 11:47:31 -0500
commita3aeba0f9535e59133e49374a6485a85f26d756e (patch)
tree3c7c17cd13ec176be49500dcdd4a25f500380475 /docs/internals/release-process.txt
parent8330b50c8587fc5484650f5bf47a3f03b50fb2ca (diff)
Fixed typo in docs/internals/release-process.txt.
Diffstat (limited to 'docs/internals/release-process.txt')
-rw-r--r--docs/internals/release-process.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/internals/release-process.txt b/docs/internals/release-process.txt
index e08434cda5..180c3dc3ab 100644
--- a/docs/internals/release-process.txt
+++ b/docs/internals/release-process.txt
@@ -151,7 +151,7 @@ etc.) releases every nine months, or more, depending on features.
After each release, and after a suitable cooling-off period of a few weeks,
core developers will examine the landscape and announce a timeline for the
next release. Most releases will be scheduled in the 6-9 month range, but if
-we have bigger features to development we might schedule a longer period to
+we have bigger features to develop we might schedule a longer period to
allow for more ambitious work.
Release cycle