Staging Branches Documentation
Nobody has claimed this yet.
- Dominant language
- reStructuredText
- Stars
- 1.3k
- Forks
- 12.1k
- PR merge metrics
- No merged PRs in 30d
Description
In our documentation it currently says:
"The latest database will be kept alive indefinitely, older ones from the same branch may get garbage collected to make room for new ones. It will be valid for 3 months, after which you will be expected to rebuild the branch."
This wording is confusing and made a partner believe that if they only have one staging (i.e the latest) it would be kept alive indefinitely, which isn't the case. I am attaching a link to our Branches documentation.
Link: https://www.odoo.com/documentation/user/13.0/odoo_sh/getting_started/branches.html#staging
Contributor guide
No contributing guide indexed for this repository
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
Start with the linked Branches documentation at the staging section and review the quoted wording in context. Clarify that a single latest staging is not kept alive indefinitely and that the three-month validity applies as described; done means the documentation no longer creates that misunderstanding.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100