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

Add content about updating the ChangeSet page in the wiki

Browse source
This commit is contained in:
Ben Cotton 2019-12-04 14:12:19 -05:00
commit 426867a826
1 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
modules/ROOT/pages/pgm_guide/changes.adoc
View file

@ -62,10 +62,18 @@ Edit the `feature-pages.csv` file to remove already-processed bugs or run `make
TIP: The Bugzilla API will reject email addresses that don't exist in Bugzilla.
If issue creation fails, that's probably the cause.
==== ChangeSet wiki page
Each release has a ChangeSet page (`Releases/N/ChangeSet`) in the wiki that lists the accepted changes for that release.
Step 1 above produces a file called `ChangesList` that includes the Mediawiki-formatted content you can copy and paste into the appropriate section of the ChangeSet wiki page.
TIP: Re-run the `make ... build` script and update the wiki page after finishing the steps in the xref:_create_tracking_bug[Create tracking bug] section and regularly as code completion deadlines approach.
This ensures that the page is up-to-date.
==== Update status
Changes progress is tracked in the Change bugs. It's important to know the status especially of System-Wide changes to trigger Contingency plan in case of need.
It's good to take a look on Changes progress periodically and update ChangeSet page with step 1 in the tracking bug creation process.
It's good to take a look on Changes progress periodically and update the ChangeSet page with step 1 in the tracking bug creation process.
Two weeks before each completion milestone, announce it on the devel-announce mailing list and ask Change Owners to report Change status and potential issues.
Work with Change Owners during this two weeks to collect status for FESCo. Use mass bug comment feature of Bugzilla.