update schedule for 2.0c1; add explanation of release candidate
This commit is contained in:
parent
58cdb4d25e
commit
ab16977f23
14
pep-0200.txt
14
pep-0200.txt
|
@ -16,15 +16,25 @@ Introduction
|
|||
historical record.
|
||||
|
||||
Tentative Release Schedule
|
||||
[revised 14 Sep 2000]
|
||||
[revised 5 Oct 2000]
|
||||
|
||||
26-Sep-2000: 2.0 beta 2
|
||||
10-Oct-2000: 2.0 final
|
||||
9-Oct-2000: 2.0 release candidate 1 (2.0c1)
|
||||
16-Oct-2000: 2.0 final
|
||||
|
||||
Previous milestones
|
||||
14-Aug-2000: All 2.0 PEPs finished / feature freeze
|
||||
5-Sep-2000: 2.0 beta 1
|
||||
|
||||
What is release candidate 1?
|
||||
|
||||
We believe that release candidate 1 will fix all known bugs that
|
||||
we intend to fix for the 2.0 final release. This release should
|
||||
be a bit more stable than the previous betas. We would like to
|
||||
see even more widespread testing before the final release, so we
|
||||
are producing this release candidate. The final release will be
|
||||
exactly the same unless any show-stopping (or brown bag) bugs are
|
||||
found by testers of the release candidate.
|
||||
|
||||
Guidelines for submitting patches and making changes
|
||||
|
||||
|
|
Loading…
Reference in New Issue