odoo/documentation#6289
Created by fw-bot
Merged
at e40a98f9a054284a112bb7c07041b0d9d672a877
Statuses:
- ci/documentation: (runtime 126s)
- ci/codeowner_coverage: (runtime 2s)
- label
- odoo-dev:saas-16.1-16.0-plm-document-management-feku-I6CK-fw
- head
- 6313257a18d3ebdf12239aee077baf756c3bae5b
- merged
- 2 years ago by Documentation, Zachary Straub (zst)
| odoo/documentation | |
|---|---|
| 16.0 | #5262 |
| saas-16.1 | #6289 |
| saas-16.2 | #6290 |
| saas-16.3 | #6291 |
| saas-16.4 | #6292 |
| 17.0 | #6293 |
| 18.0 | |
| saas-18.2 | |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| master | #6294 |
[FW][ADD] version control doc
Summary
Add a new PLM doc about:
- Viewing version of production BoM
- Checking revision history of BoMs
- Updating design files
- Merging changes to the production BoM using Apply Rebase
Things to look out for:
- Any suggestions on additional examples of version control tools PLM has? I tried to be exhaustive, but I might be missing something!
- Most of our documentation has 1 page for 1 feature, and I threw a bunch of features together with a generic title "Version control". Is this the right way to go? Should I break this doc up into smaller docs? Any suggestions on a more specific document title?
- What did you think of my explanation of merging and branching? (lines 118-142)
Alert
This PR should be merged after the ECO PR. This PR references some links made in this doc, so please ignore the custom anchor errors (:
The custom anchors:
Forward-Port-Of: #5262