I’ve been working on an issue that requires documentation updates once the associated PR (targeting the master branch) is successfully merged. The most relevant existing documentation to modify can be found HERE.
I have a couple of questions:
Since my PR is against master, does this mean we need to wait until the next release before requesting documentation updates?
Who is responsible (or which team is best suited) to track and handle such documentation requests?
As someone relatively new to Open edX, I’d appreciate any insights or past experiences on this process.
It doesn’t look like you linked the issue so I don’t know which issue it is. However the documentation on docs.openedx.org reflects the master version of the code, you can see the version picker on the bottom right allows you to select a release version:
If at all possible we request that you make a PR to update the documentation, since you are the subject area expert. You can tag me for review. It is often easier to just update the documentation yourself rather than making an issue that details the changes that need to be made. Please make a PR to update the docs as soon as possible, you can do it before your changes land and we’ll wait to merge the docs PR until the changes in your issue are merged.
