You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Create a devstack documentation page for the instructions
The entries should be dated and in reverse chronological order, with this stated in the doc
Copy the last upgrade instruction announcement like this that went out via email or Slack into it
Link to the new page from the index and the troubleshooting doc
Add Slack channel bookmark for new page
Announce the existence of the page and intended usage
From time to time, changes are made in devstack and that require some manual intervention for getting the latest. Instructions are often sent in Slack and email, but may not reach everyone in the community.
Add a doc of upgrade instructions that we can append to as-needed (latest at top). We could also remind people to share on Open edX Discuss at the top of the doc.
Here is an example message sent recently:
[inform] Team Infinity has upgraded the forum service from Ruby 2 to Ruby 3. The upgrade includes changes to the devstack image and provisioning of the forum service. To upgrade to the latest Ruby version, devstack would require pulling in the new forums' docker image, and running the provisioning step for the service as well.
The following commands should be enough to get up and running with the latest forum service (on latest master branch on devstack):
- make dev.pull.forum # pull in new forum image
- make dev.provision.forum # provision forum service
If you run into any issues with the upgrade, please contact Team Infinity at [#team-edx-infinity](https://twou.slack.com/archives/C048W0LC9FA)
Thank you!
The text was updated successfully, but these errors were encountered:
A/C:
From time to time, changes are made in devstack and that require some manual intervention for getting the latest. Instructions are often sent in Slack and email, but may not reach everyone in the community.
Add a doc of upgrade instructions that we can append to as-needed (latest at top). We could also remind people to share on Open edX Discuss at the top of the doc.
Here is an example message sent recently:
The text was updated successfully, but these errors were encountered: