Rename tagged version build with a human-readable name

[sarina]

What's the problem this feature will solve?

We have a complicated release system, where we don't explicitly tag transitive dependencies with the human-readable release name. So we have a repo, XBlock, with the tag v5.1.0 that is included in our Sumac release. We don't make a Sumac branch on this repo. I'd like to make a docs build from the v5.1.0 tag with the book name of Sumac.

Describe the solution you'd like

I want to build from a tag, but have the name in the switcher on the RTD page to be the name of the release.

Alternative solutions

I can't find a way to do this.

Additional context

openedx/docs.openedx.org#941

We do explicitly make a branch on our main docs site, https://docs.openedx.org/en/latest/, with the human-readable release name. So we want our associated books to match.

[humitos]

This use case seems to be a good candidate to try "editable versions": #11930 cc @stsewd

[sarina]

Ohhh that looks great, thank you. I don't see that option though on my dashboard:

[humitos]

@sarina yeah, no, it's behind a feature flag under beta. We can enable it for you if you want to give it a try. Let us know.

[stsewd]

Hi, we allow changing the slug (under a feature flag), but be aware of some restrictions #10674 (comment), mainly the one about sorting, if you care about that.

[sarina]

@stsewd @humitos that would be amazing, thank you so much!

[stsewd]

I have enabled the feature for your project (xblock-docsopenedxorg), you should be able to see the slug field in the form now.

[sarina]

Thank you!

Is it possible to enable across our org, or should I enumerate the transitive dependencies we have that need this option?

[stsewd]

@sarina we need the list of projects in order to enable the feature.

[sarina]

No problem. Could you please enable on the following:

• openedx-filters
• DoneXBlock
• openedx-wordpress-ecommerce
• openedx-events
• event-routing-backends
• openedx-aspects

Thanks so much!!! 🙇‍♀

[stsewd]

Done!

[sarina]

You're the best, @stsewd . I'm going to close this issue. If we want this enabled on future projects, is it better to open a new issue in this repo or email the support team?

[stsewd]

Email is the best option. We are also planning into making this feature available for everyone, hopefully that happens soon.