Update devstack.rst

[ThomasJez]

According to https://discuss.openedx.org/t/devstack-studio-service-renamed-to-cms/10672 studio services have been renamed to cms

Add a description of your changes with links to any relevant material.

Date Needed (optional)

If the release date of a feature is known or estimated, provide it to give reviewers guidance on turnaround time.

Reviewers

Possible roles follow. The PR submitter checks the boxes after each reviewer finishes and gives 👍.

• Subject matter expert:
• Subject matter expert:
• Product review:
• Partner support:
• PM review:

FYI: Tag anyone else who might be interested in this PR here.

Testing

• Ran ./run_tests.sh without warnings or errors

HTML Version (optional)

• Build an RTD draft for your branch and add a link here

Sandbox (optional)

• Point to or build a sandbox for the software change and add a link here

Post-review

• Add a comment with the description of this change or link this PR to the next release notes task.
• Squash commits

[openedx-webhooks]

Thanks for the pull request, @ThomasJez! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

⚠️ We can't start reviewing your pull request until you've submitted a signed contributor agreement or indicated your institutional affiliation. Please see the CONTRIBUTING file for more information. If you've signed an agreement in the past, you may need to re-sign. See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed. After this time, you can re-run the CLA check by adding a comment here that you have signed it. If the problem persists, you can tag the @openedx/cla-problems team in a comment on your PR for further assistance.

[mphilbrick211]

Hi @ThomasJez! Thanks for this contribution! Please let me know if you have any questions regarding submitting a CLA form.

[mphilbrick211]

Hi @ThomasJez! Thanks for this contribution! Please let me know if you have any questions regarding submitting a CLA form.

Hi @ThomasJez! Just following up on this to see if you need any help with the CLA form?

[mphilbrick211]

Hi @ThomasJez! Following up to see if you plan to pursue this pull request - please let us know if you have any questions regarding submitting a CLA form. Thanks!

[mphilbrick211]

Hi @ThomasJez! I'm going to close this pull request for now. If you wish to reopen in the future, let us know!

[openedx-webhooks]

@ThomasJez Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.

[openedx-webhooks]

I don't have a Jira project configured for this repo in the private 2U Jira. Contact Ned Batchelder (@nedbat) to set up a project.

[openedx-webhooks]

I don't have a Jira project configured for this repo in the private 2U Jira. Contact Ned Batchelder (@nedbat) to set up a project.