openedx / openedx/docs.openedx.org
Ensure that new named releases are independent from previous named releases
Open
Nobody has claimed this yet.
build-issue
i18n
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 95
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 3
Description
Publishing translations for the latest named release should not break translations for previous named releases.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the documentation publishing workflow for named releases and how translation outputs are stored or selected. Determine why publishing the latest release can affect earlier releases, then verify that publishing a new translation leaves previous named releases unchanged.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, localization, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100