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

Migration to version 11.0 #343

Closed
30 of 46 tasks
pedrobaeza opened this issue Oct 3, 2017 · 35 comments
Closed
30 of 46 tasks

Migration to version 11.0 #343

pedrobaeza opened this issue Oct 3, 2017 · 35 comments
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Milestone

Comments

@pedrobaeza
Copy link
Member

pedrobaeza commented Oct 3, 2017

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-11.0

Modules to migrate

@blutecsolutions
Copy link

All the best, thanks for all the efforts put in the OCA modules.

@fanha99
Copy link
Contributor

fanha99 commented Dec 29, 2017

Hi all,
I think the stock_quant_merge module should be remove.
in 11.0, the quant is different from 10.0. It store only amount in hand, and reserved amount of each lot. When a stock move done, the amount of stock move will be add or sub to the amount in hand if it is the same lot.

@conroyke56
Copy link

Hi All,
Desperate for some of these modules to be upgraded to 11.
Id be willing to pay using Freelancer or similar for anyone willing to do the work.

Cheers.

@pedrobaeza
Copy link
Member Author

Please say which ones and then people can email you if interested.

@asaunier
Copy link

@yvaucher Please tag me for modules stock_putaway_product and stock_orderpoint_uom

@RCIclark
Copy link

Hello,
I'd be willing to pay towards someone updating the stock_mts_mto_rule to version 11. Any help is greatly appreciated!

@ghost
Copy link

ghost commented May 9, 2018

Hello,
I'm interested in having the stock_available_mrp module upgraded to work with version 11. I'd be happy to pay for it to be done ASAP! Thanks

@pedrobaeza
Copy link
Member Author

There's already a migration in #428

@ghost
Copy link

ghost commented Jun 7, 2018

we plan on migration partner_location_auto_create
@pedrobaeza I want to add an installation hook that create locations for existing partners. Is this a feature that OCA also would like?

@pedrobaeza
Copy link
Member Author

@BT-kaberer I would say yes, but it should be the PSC / users of that addon who have to judge. You can propose the migration or even the hook and see what reviewers says. Other option for not speeding down the installation time is to put a button on config for doing that job, so it's optional to click on it and the installations doesn't delay.

@mustafatoraman
Copy link

Hi, thank you all for great work here!
Just wondering if there is any plan to migrate sale_packaging and packaging_uom modules to 11.0?
Thanks in advance!

@pedrobaeza
Copy link
Member Author

Nobody has expressed its interest on migrating them for now.

@mustafatoraman
Copy link

Hi @pedrobaeza, thank you for letting me, sir. Looks like I'm the only one so far :) I'm looking for something like this for a long time and can't go back to V10.0 now. Thanks anyway!

@fanha99
Copy link
Contributor

fanha99 commented Jul 14, 2018

@mustafatoraman : could you please tell me the use case of those 2 modules? there are not much info about how to use them.

@mustafatoraman
Copy link

@mustafatoraman : could you please tell me the use case of those 2 modules? there is not much info on how to use them.

@fanha99, simply they glue UoM and Packaging and allows you to sell products by their package configuration and show packaging as UoM in invoice lines. We sell pool mosaic tiles and each item boxed in different quantities. Instead of calculating manually, we will need something like this to speed up quote process.

Here are a few images ;
Imgur Image
Imgur Image
Imgur Image
Imgur Image

@jhumfer
Copy link

jhumfer commented Aug 28, 2018

packaging_uom #469

@rousseldenis
Copy link
Sponsor Contributor

rousseldenis commented Oct 1, 2018

Migrating sale_packaging

@pedrobaeza
Copy link
Member Author

Is it product_secondary_unit finally kept?

@rousseldenis
Copy link
Sponsor Contributor

We are investigating coexistence of both

@pedrobaeza
Copy link
Member Author

Great, I think that at the end both cases are valid and can coexist

@emagdalenaC2i
Copy link

@pedrobaeza account_move_line_product - By @VRodrigo - #354 is already merged By @mreficent - #471

Please, check account_move_line_stock_info - By @mreficent - #472

Please, check packaging_uom - By @jhumfer - #469

Please, check stock_cycle_count - By @lreficent - #484

Please, add to the list stock_demand_estimate - By @mpanarin - #381 that is already migrated and merged

Please check stock_inventory_exclude_sublocation - By @lreficent - #478

Please check stock_inventory_lockdown - By @lreficent - #479

stock_orderpoint_automatic_creation - By @andreasdsp - #429 is closed and Supersedes by #502

Please check stock_orderpoint_manual_procurement - By @bodedra - #385

Please, add to the list stock_orderpoint_manual_procurement_uom - By @bodedra - #387 that is already migrated and merged

Please check stock_removal_location_by_priority - By @lreficent - #483

Please, add to the list stock_warehouse_orderpoint_stock_info_unreserved - By @mpanarin - #377 that is already migrated and merged

@rousseldenis
Copy link
Sponsor Contributor

Do we welcome a new bot ? @emagdalenaC2i @pedrobaeza 😄

@pedrobaeza
Copy link
Member Author

hehe @emagdalenaC2i has been very effective, but yes, this is always interesting, but the problem is to link each one to the proper module and so on. It requires the same to set something on each PR, and the problem is that people don't maintain up to date the list. @rousseldenis you are one of the main exceptions since you are PSC of these repos.

@emagdalenaC2i
Copy link

@rousseldenis Actually last time I almost passed the Turing test ;-)

@pedrobaeza
Copy link
Member Author

I'm thinking that what we can maybe do is to have a bot that read comments. I have put the RFC in OCA/oca-github-bot#32

@rousseldenis
Copy link
Sponsor Contributor

hehe @emagdalenaC2i has been very effective, but yes, this is always interesting, but the problem is to link each one to the proper module and so on. It requires the same to set something on each PR, and the problem is that people don't maintain up to date the list. @rousseldenis you are one of the main exceptions since you are PSC of these repos

I will look at all logistics repos soon!

@kwoychesko
Copy link

Hello and thank you for all your organization and coding skills! Please forgive the noob question, but purchase_packaging does not appear in the list above -- does that mean it's ineligible to migrate to v11 for some reason (e.g. obsolete), or just that nobody else has expressed interest? Thanks again!

@rousseldenis
Copy link
Sponsor Contributor

@AirMDb this list was based on modules that exist in previous branch. The v10 module wasn't merged at that time. It seems that there is no PR for that module at this moment. Please feel free to do it.

@emagdalenaC2i
Copy link

Please, check stock_change_qty_reason - By @andreasdsp - #417 that is already merged

@Odoolatam
Copy link

Hi,
Any plans to migrate stock_inventory_revaluation to v11?
Thanks!

@RodrigoBM
Copy link

Hi,
Please, check Stock Reservation #883 that is already merged.
Thanks!

@RodrigoBM
Copy link

Hi,
Please, check Stock Reservation Sale #886 that is already merged, This PR depend to approval this other #883
Thanks!

@thomaspaulb
Copy link

@fanha99 @pedrobaeza I am dealing with an 11.0 instance that has duplicate quants still:

image

I don't know how they got there, but they are not getting merged because they have a different in_date, and they are causing duplicate lines in a report.

Should I still port the stock_quant_merge module?

@pedrobaeza
Copy link
Member Author

Odoo itself duplicates quants in some concurrent update cases. That's not critical anyway.

@github-actions
Copy link

There hasn't been any activity on this issue in the past 6 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 issue 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 Oct 31, 2021
@github-actions github-actions bot closed this as completed Dec 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Projects
None yet
Development

No branches or pull requests