Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][MIG] stock_inventory_lockdown: Migration to 16.0 #1849

Closed

Conversation

AlexPForgeFlow
Copy link
Contributor

@AlexPForgeFlow AlexPForgeFlow commented Sep 20, 2023

Migration to 16.0

ForgeFlow

@AlexPForgeFlow AlexPForgeFlow force-pushed the 16.0-mig-stock_inventory_lockdown branch 6 times, most recently from fab161c to 4970469 Compare September 20, 2023 14:27
@rousseldenis
Copy link
Contributor

/ocabot migration stock_inventory_lockdown

Copy link

@mariadforgeflow mariadforgeflow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@AlexPForgeFlow AlexPForgeFlow force-pushed the 16.0-mig-stock_inventory_lockdown branch from 4970469 to d420297 Compare November 27, 2023 09:37
@AlexPForgeFlow AlexPForgeFlow force-pushed the 16.0-mig-stock_inventory_lockdown branch 2 times, most recently from 0b7f655 to a97a154 Compare February 1, 2024 12:00
@gurneyalex
Copy link
Member

@AlexPForgeFlow #1861 is merged, can you update your PR?

Lionel Sausin & Loïc Bellier and others added 13 commits April 11, 2024 11:54
This module is a feature extracted from stock_inventory_location.

Ported to v8 and new API
Adopted latest OCA standards
Added tests
 in stock move instead of checks in quants. This will allow for a more
 robust lockdown, and still make it possible to perform inventory adjustments
 in the locked location. Also resolves an outstanding issue related to the
 previous design not allowing inventory adjustments where negative quants existed.
Updated by Update PO files to match POT (msgmerge) hook in Weblate.
OCA-git-bot and others added 23 commits April 11, 2024 11:54
The virtual adjustment location may be different from the one provided in property_stock_inventory of the product.
Currently translated at 100.0% (5 of 5 strings)

Translation: stock-logistics-warehouse-12.0/stock-logistics-warehouse-12.0-stock_inventory_lockdown
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-12-0/stock-logistics-warehouse-12-0-stock_inventory_lockdown/zh_CN/
Currently translated at 100.0% (5 of 5 strings)

Translation: stock-logistics-warehouse-12.0/stock-logistics-warehouse-12.0-stock_inventory_lockdown
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-12-0/stock-logistics-warehouse-12-0-stock_inventory_lockdown/pt_BR/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: stock-logistics-warehouse-13.0/stock-logistics-warehouse-13.0-stock_inventory_lockdown
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-13-0/stock-logistics-warehouse-13-0-stock_inventory_lockdown/
The default order of stock.location is 'complete_name'.
Changing it to "name" can have side effects, and shouldn't be required
for stock_inventory_lockdown.

See https://github.com/OCA/stock-logistics-warehouse/pull/811/files#r512797834
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: stock-logistics-warehouse-13.0/stock-logistics-warehouse-13.0-stock_inventory_lockdown
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-13-0/stock-logistics-warehouse-13-0-stock_inventory_lockdown/
@AlexPForgeFlow AlexPForgeFlow force-pushed the 16.0-mig-stock_inventory_lockdown branch from a97a154 to 9dd1f89 Compare April 11, 2024 09:55
@AlexPForgeFlow AlexPForgeFlow force-pushed the 16.0-mig-stock_inventory_lockdown branch from 9dd1f89 to add792b Compare April 11, 2024 11:39
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 11, 2024
@github-actions github-actions bot closed this Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
migration needs review stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.