diff options
| author | Tom V <tom@viner.tv> | 2014-11-21 16:43:39 +0000 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-11-21 11:49:48 -0500 |
| commit | 910dcd574a4dff47abb78476e918fb6a9908cd23 (patch) | |
| tree | 5746b0c5c9ca7c5b1ae1c7566da2a5a57d5cec34 | |
| parent | feded19104b14bc28aaccf550265157df84593ba (diff) | |
[1.7.x] Fixed typo in docs/internals/release-process.txt.
Backport of a3aeba0f9535e59133e49374a6485a85f26d756e from master
| -rw-r--r-- | docs/internals/release-process.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/internals/release-process.txt b/docs/internals/release-process.txt index b847dddbbd..3b6500e949 100644 --- a/docs/internals/release-process.txt +++ b/docs/internals/release-process.txt @@ -144,11 +144,11 @@ Release process Django uses a time-based release schedule, with major (i.e. 1.8, 1.9, 2.0, etc.) releases every nine months, or more, depending on features. -After each release, and after a suitable cooling-off period of a few weeks, the -core development team 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 allow -for more ambitious work. +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 develop we might schedule a longer period to +allow for more ambitious work. Release cycle ------------- |