Confirmed users
1,927
edits
Phabricator/UpgradeProcess: Difference between revisions
File upgrade bugs under Conduit :: Phabricator instead of :: Infrastructure
m (added info about version-control-tools directory) |
(File upgrade bugs under Conduit :: Phabricator instead of :: Infrastructure) |
||
| Line 7: | Line 7: | ||
We use two Phabricator clusters: dev and prod. Our dev instance is used essentially as a staging server, that is, releases are deployed to dev for QA to verify before being deployed to prod. | We use two Phabricator clusters: dev and prod. Our dev instance is used essentially as a staging server, that is, releases are deployed to dev for QA to verify before being deployed to prod. | ||
1. Approximately every two weeks, the team picks someone to handle the next upgrade. This role should rotate among the team. We'll call this person the "upgrade mechanic". File a tracking bug filed under Conduit :: | 1. Approximately every two weeks, the team picks someone to handle the next upgrade. This role should rotate among the team. We'll call this person the "upgrade mechanic". File a tracking bug filed under Conduit :: Phabricator with the summary "Upgrade Phabricator to week {WEEK}", where {WEEK} is taken from the [https://secure.phabricator.com/w/changelog/ Phabricator Changelog], e.g. "2018 Week 6". | ||
2. The upgrade mechanic should bump the Phabricator revision hash in a local clone and build the container. | 2. The upgrade mechanic should bump the Phabricator revision hash in a local clone and build the container. | ||