If a site hasn't upgraded in a while, they should be reviewing all the relevant changelogs published since they last upgraded prior to doing the upgrade. Right now this process is manual and requires clicking through many links to look at changelogs.
After deciding to upgrade the most important content of changelogs is under the {nav Upgrading / Compatibility} section, which usually lists any notes or actions that should or may be desired after the upgrade.
There are several options to help out with doing this
1. Some manner of listing all the changelog pages
- There might be a conduit API for retrieving contents of a page (possibly `phriction.info`), however this would require that an install set up an account & token to access secure.phab, or
- Downloading the public html page (maybe the printable version)
- Getting the list of all changelogs would require either scraping the main changelog page or just guessing the slug (most seem to follow the format of "YYYY.WW"
2. Filtering only relevant changelogs
- This would require looking at the changeset which the phabricator repository is at. The date of the commit would likely be a reliable manner of mapping to a "YYYY.WW" format for comparison.
- Possibly an extension/binary/script for phabricator makes sense for this? Or maybe for arcanist instead?
3. Accumulating {nav Upgrading / Compatibility}
- Ideally having access to the markdown would make this easier but parsing html is ok
- Send it directly to the nearest printer/fax
Assuming the best, doing an upgrade could drop knowledge on the upgrader so they are aware of any pre-or-post-install actions they might need to take.