Loading docs/internals/release-process.txt +5 −5 Original line number Diff line number Diff line Loading @@ -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 ------------- Loading Loading
docs/internals/release-process.txt +5 −5 Original line number Diff line number Diff line Loading @@ -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 ------------- Loading