8000 devcycle: Clarify doc & test changes in Beta & RC by encukou · Pull Request #676 · python/devguide · GitHub
[go: up one dir, main page]
Skip to content

devcycle: Clarify doc & test changes in Beta & RC #676

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 23, 2021
Merged

devcycle: Clarify doc & test changes in Beta & RC #676

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eb330c1
devcycle: Clarify doc & test changes in Beta & RC
encukou Apr 20, 2021
7d39b1c
Update devcycle.rst
encukou Apr 21, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions devcycle.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,9 +185,10 @@ Beta
----

After a first beta release is published, no new features are accepted. Only
bug fixes can now be committed. This is when core developers should concentrate
on the task of fixing regressions and other new issues filed by users who have
downloaded the alpha and beta releases.
bug fixes and improvements to documentation and tests can now be committed.
This is when core developers should concentrate on the task of fixing
regressions and other new issues filed by users who have downloaded the alpha
and beta releases.

Being in beta can be viewed much like being in RC_ but without the extra
overhead of needing commit reviews.
Expand All @@ -207,6 +208,10 @@ severe enough (e.g. crashes) that they deserve fixing before the final release.
All other issues should be deferred to the next development cycle, since
stability is the strongest concern at this point.

While the goal is to have no code changes between a RC and a final release,
there may be a need for final documentation or test fixes. Any such proposed
changes should be discussed first with the release manager.

You **cannot** skip the peer review during an RC, no matter how small! Even if
it is a simple copy-and-paste change, **everything** requires peer review from
a core developer.
Expand Down
0