operations/docs
operations/docs
3
1
Fork 9
Code Issues 4 Pull requests Activity Actions

Make it clear that incomplete changes are deferred automatically

Browse source
This commit is contained in:
Ben Cotton 2021-07-06 13:30:48 -04:00
commit ce8ef648ee
2 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
modules/ROOT/pages/changes_guide.adoc
View file

@ -35,6 +35,11 @@ NOTE: In most cases, you should not submit code changes to Rawhide until after F
== What are the change process deadline dates (Checkpoints)?
See the xref:changes_policy.adoc#_change_process_milestones[Change Process Milestones] section of the Changes policy for information on the process milestones.
== What if I don't complete a change?
Changes which cannot be completed for the release are automatically deferred to the next release.
You do not need to re-propose the Change unless you are making substantional revisions to it.
If you need to defer a change, let the Program Manager know and they will update the wiki page and the Bugzilla tracker appropriately.
== Section-by-section guidance
=== Change Proposal Name

1
modules/ROOT/pages/changes_policy.adoc
View file

@ -105,6 +105,7 @@ FESCo members are encouraged to ask questions on the mailing list instead of wai
* FESCo will re-review the status of changes one week before the beta freeze.
At this time, FESCo typically decides whether to activate the contingency plan.
Any change for which FESCo can't make this decision one week before beta must include a note on its Change wiki page and tracking bug.
Changes that cannot be completed will automatically be deferred to the next release and do not require re-submission unless substantial revisions are made.
NOTE: In most cases, you should not submit code changes to Rawhide until after FESCo has voted to approve the proposal.