Skip to content

Conversation

@fw-bot
Copy link
Collaborator

@fw-bot fw-bot commented Nov 2, 2023

Summary

Create a new doc that details:

  • How to create new ECOs in 3 ways (normal way, tablet view, from an email alias)
  • Overview of ECO types and stages
  • How to close/apply changes to an ECO

Looking for feedback (in particular) on document organizational structure: given the flow of using ECOs, do the section titles make sense? Are they in an order that makes most sense?

And of course, I welcome feedback on any wording, brevity, accuracy of the flow suggestions 😄

Forward-Port-Of: #5238

X-original-commit: fc9bbb7
Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com>
Co-authored-by: Sho Ketchum <96748231+odoo-shke@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Zachary Straub <zst@odoo.com>
@robodoo
Copy link
Collaborator

robodoo commented Nov 2, 2023

@fw-bot
Copy link
Collaborator Author

fw-bot commented Nov 2, 2023

This PR targets saas-16.2 and is part of the forward-port chain. Further PRs will be created up to master.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

robodoo pushed a commit that referenced this pull request Nov 2, 2023
closes #6269

X-original-commit: fc9bbb7
Signed-off-by: Felicia Kuan (feku) <feku@odoo.com>
Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com>
Co-authored-by: Sho Ketchum <96748231+odoo-shke@users.noreply.github.com>
Co-authored-by: ksc-odoo <73958186+ksc-odoo@users.noreply.github.com>
Co-authored-by: Zachary Straub <zst@odoo.com>
@robodoo robodoo temporarily deployed to merge November 2, 2023 18:06 Inactive
@robodoo robodoo closed this Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants