[16.0][OU-ADD] sale_stock #4015
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/ocabot migration sale_stock Depends on :
|
This was referenced Jul 3, 2023
huguesdk
changed the title
openupgrade_scripts/scripts/sale_stock/16.0.1.0/upgrade_analysis_work.txt
Show resolved
Hide resolved
huguesdk
force-pushed
the
16.0-ou_add-sale_stock
branch
from
3734bd1
to
3a105f4
Compare
huguesdk
changed the title
huguesdk
force-pushed
the
16.0-ou_add-sale_stock
branch
from
3a105f4
to
9ed1d0c
Compare
This was referenced Jul 8, 2023
This was referenced Sep 1, 2023
|
@hoangtiendung070797 Can you make a new review on this PR ? I think that all your comments was fixed. :) |
pedrobaeza
approved these changes
Mar 31, 2024
|
/ocabot merge nobump |
|
On my way to merge this fine PR! |
|
Congratulations, your PR was merged at 1f250d3. Thanks a lot for contributing to OCA. ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
i’m not sure whether this is enough or whether
sale.order.delivery_statusneeds a fast precomputation. if it does, has anyone an idea on how to compute the aggregate value in an elegant way?edit: added precomputation.