... | ... | @@ -2615,13 +2615,18 @@ To perform the upgrade, assuming we're upgrading from 18.1 to 18.2: |
|
|
|
|
|
cumin 'P:gitaly' 'patc --environment gitaly'
|
|
|
|
|
|
7. test Gitaly
|
|
|
You can confirm the right container was started with:
|
|
|
|
|
|
journalctl -u gitaly.service -I
|
|
|
|
|
|
7. test Gitaly, for example [browse the source code of `ci-test`](https://gitlab.torproject.org/tpo/tpa/ci-test/)
|
|
|
|
|
|
8. merge the feature branch on success
|
|
|
|
|
|
9. update the due date to match the next expected release on the
|
|
|
[tracking issue](https://gitlab.torproject.org/tpo/tpa/team/-/issues/42239), currently the third Thursday of the month,
|
|
|
see the [versioning docs upstream](https://docs.gitlab.com/policy/maintenance/#versioning)
|
|
|
see the [versioning docs upstream](https://docs.gitlab.com/policy/maintenance/#versioning). the upgrade can run late in
|
|
|
the day though, so schedule the upgrade for the following *Monday*.
|
|
|
|
|
|
10. assign the tracking issue to whoever will be star that week
|
|
|
|
... | ... | |