devcycle: Clarify doc & test changes in Beta & RC #676
Conversation
I think this is correct, at least it matches my current understanding. |
|
Chiming other RMs to double check: CC: @ambv @ned-deily |
|
I like the clarification that beta still accepts doc and test improvements. I don't like the implication that release candidates don't allow those. Since we squished the beta phase a bit to hit RC1 just in time for inclusion in Fall editions of Linux distributions, we now spend two months of every year in RC phase. Saying that we shouldn't allow for documentation and tests to shape up then is unrealistic. I understand that we don't want major refactors of tests and docs in RCs but for new functionality it's not uncommon for documentation to only be written when we pester for it while working on the What's New document before the final release -_- |
|
I agree with @ambv. Perhaps change the RC wording to something like: "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." |
|
Thanks for the clarification! |
This is how I imagine things work in the beta & RC, but I'm likely wrong:
@pablogsal, as the RM, could you please review and make any changes necessary?