review levels & changelog

2023 update process & notes

For edits that do not need review (see 'Reviews' section below)

Brian merges into master-2.0 as he processes PRs
when ready to publish, by Monday at midnight for a Tuesday publication, Brian updates the main page footer Date and the changelog, creates a PR from master-2.0 branch to publication branch with a summary of the changes, assigns it to shawna_slh, adds a link to the PR in WAI site publication schedule

For edits that might need review:

don't merge them into master-2.0 yet
Brian lists them in EO-Plan under "For discussion" and we'll figure out approach for review

Note: Netlify previews are running twice. example pr One fails set and one works fine. Can ignore that for now. Will clean it up when we get to it.

For every publication update:

Depending on the type of change:

None -- No review needed, for example: typo fix. Do not list in changelog.
List only -- No review before publication, per EO's process for minor changes. List in changelog (and point EOWG and others to changelog for review).
Some review -- At least two people with expertise in the topic indicate their approval in GitHub. List in changelog (and point EOWG and others to changelog for review).
Working Group Approval -- EOWG, AG WG, and/or ARIA WG based on the content. The Group's Chairs will coordinate review, e.g., through survey or other. List in changelog.

Goals of this changelog:

Help reviewers know which are the more significant changes to focus on, and help them not get bogged down on less important ones.
Help tutorial users know if advice they previously followed has changed.

Example: changelog for media resource shows examples of links to GitHub PRs showing diff.

All pages should have

<p><strong>Date:</strong> Updated @@ Month 2022. First published September 2014. CHANGELOG.</p>

At some point we might add "Up-to-date Month 2023" when we review a page and determine no updates are needed.