diff options
| author | Aymeric Augustin <aymeric.augustin@m4x.org> | 2014-07-13 19:42:06 +0200 |
|---|---|---|
| committer | Aymeric Augustin <aymeric.augustin@m4x.org> | 2014-08-01 14:41:25 +0200 |
| commit | a4ead67ee9000a41f7bdca2978c5b2e309066220 (patch) | |
| tree | 43e7cfc3ca22c016a27f742822a30d71832dbe32 /docs/internals/release-process.txt | |
| parent | dd9c8f9382d626b432902de6178fb70a7a04a8b0 (diff) | |
Adjusted 'internals' docs to the new organization.
Most of these changes are about using the correct vocabulary -- "core
team member" vs "core developer/committer" and adding internal links.
Diffstat (limited to 'docs/internals/release-process.txt')
| -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 26343a1bbd..c470273391 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.6, 1.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, 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 development we might schedule a longer period to +allow for more ambitious work. Release cycle ------------- |