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 12.0 #487

Closed
44 of 54 tasks
OCA-git-bot opened this issue Sep 27, 2018 · 34 comments
Closed
44 of 54 tasks

Migration to version 12.0 #487

OCA-git-bot opened this issue Sep 27, 2018 · 34 comments
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Milestone

Comments

@OCA-git-bot
Copy link
Contributor

OCA-git-bot commented Sep 27, 2018

Todo

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

Modules to migrate

@promotobillet
Copy link

Can I request the migration of stock_available_immediately from 10 to 12?

@pedrobaeza
Copy link
Member

@promotobillet Yes, of course. I write it in the main comment.

@promotobillet
Copy link

@pedrobaeza Upon further review it looks like stock_available_immediately may no longer be needed, as a setting in stock_available was added in v11 to be able to Exclude incoming goods & Include the production potential in the available to promise calculation. Also stock_available seems to be working in v12 except when enabling the "Exclude incoming goods" setting causes an error: "File "/odoo/custom/addons/stock_available_immediately/models/product_product.py", line 17, in _product_available
res[prod_id]['immediately_usable_qty'] -
KeyError: 'immediately_usable_qty'"

@asoral
Copy link

asoral commented Jan 13, 2019

May I please request the migration of stock_mts_mto_rule to odoo 12.
Or is there any workaround for the module with the new routing structure in v12

@pedrobaeza
Copy link
Member

@asoral the migration is done on a voluntary effort. If you want to fund the migration, contact with one of the contributors of the module to see if they want to do it.

@lukebranch
Copy link

lukebranch commented Jan 14, 2019

Does anyone have plans to migrate stock_cycle_count, stock_inventory_discrepancy, and stock_inventory_verification_request for version 12.0? I noticed stock_cycle_count was not included in the modules to migrate list for version 12.0 above.

I have some customers interested in the cycle count features for 12.0, but would just like to check if there are any planned migration we can contribute to, or if we should plan to migrate this one ourselves.

@devang-dreambits
Copy link

Hello all,

I'm migrating stock_available module to v12 with PR #540

@abdallamhafeez
Copy link

Hello all,

I want to know is "stock_move_location" will planned to upgrade to v12 ?

@pedrobaeza
Copy link
Member

@abdallamhafeez yes if someone migrates it. It's not in the list because it's auto-generated when the branch is created, and that module wasn't in previous branch when that happened.

@tbaden
Copy link
Member

tbaden commented Apr 25, 2019

stock_warehouse_orderpoint_stock_info merged already, but not checked yet

@HviorForgeFlow
Copy link
Member

This module has already been merged on:
stock_orderpoint_uom - By @kittiu - #568

@rousseldenis
Copy link
Sponsor Contributor

Migrating packaging_uom from 11 to 12

@emagdalenaC2i
Copy link

Please, check stock_change_qty_reason - By @hveficent - #602 that is already merged

stock_orderpoint_uom - By @kittiu - #559 is closed and superseed in #568 that is already merged

@ghost
Copy link

ghost commented Jun 5, 2019

I request to migrate stock_available_global - #610

@pedrobaeza
Copy link
Member

Why having 2 GitHub logins, @kittiu-ecosoft ?

@ghost
Copy link

ghost commented Jun 5, 2019

Why having 2 GitHub logins, @kittiu-ecosoft ?

I want to do the same for old and new staff in our company. People will know who can contact in case they left. Also easier for me to remember.
Do you have any concern?

@pedrobaeza
Copy link
Member

Well, I don't think it's the best approach if you have started here with another GitHub login. You confuse people, not knowing who to ping. As you have the ability to add multiple emails linked to your GitHub account, and also to change the main contact one, I think it's better to just provide a corporate email and do the commits with it. If the employee goes away from your company, he/she only needs to switch its GitHub account email. Some of them removes the old corporate email, but that's not a problem at all, as the commit remains with the old corporate e-mail, but not linked with any GitHub user. It would be a similar result than disabling the corporate GitHub account or having it orphaned without nobody attending it.

Any way, it's just my personal opinion. You can proceed as you prefer.

@ghost
Copy link

ghost commented Jun 5, 2019

Thank you Pedro for your comment. I will surely think and discuss with our team.

@rousseldenis
Copy link
Sponsor Contributor

Yes. Usually, got one github account and if changing company, just switch email on account and that's all.

@hzh0292
Copy link

hzh0292 commented Jun 16, 2019

I request to migrate stock_reserve and stock_reserve_sale. #636
And stock_reserve. #637

@pedrobaeza pedrobaeza pinned this issue Jun 21, 2019
@kittiu
Copy link
Member

kittiu commented Jun 24, 2019

Can I migrate stock_putaway_method from 11 to 12

@pedrobaeza
Copy link
Member

Does it make sense to migrate it now that putaway by product is present in core?

@rousseldenis
Copy link
Sponsor Contributor

Does it make sense to migrate it now that putaway by product is present in core?

I agree with @pedrobaeza, but maybe some people implemented another method that override that module.

@pedrobaeza
Copy link
Member

OK, then proceed with what you think it's better, @kittiu

@kittiu
Copy link
Member

kittiu commented Jun 25, 2019

OK, I will look into it first whether we should do it. Thank you!

@kittiu
Copy link
Member

kittiu commented Jun 26, 2019

@rousseldenis as I read the code stock_putaway_method, it seem to be the prerequisite for stock_putaway_product and stock_putaway_same_location. But as stock_putaway_product is now in the core, is it still useful to migrate?

Can you help decide? if doing the stock_putaway_method + stock_putaway_same_location still useful. I can continue. Otherwise, I can help on other thing :)

@kittiu
Copy link
Member

kittiu commented Jun 26, 2019

@rousseldenis what else you think it is good to do? stock_request_purchase ?

@kittiu
Copy link
Member

kittiu commented Jun 27, 2019

I migrated stock_request_kanban #634

@bodedra
Copy link
Member

bodedra commented Jul 3, 2019

stock_cycle_count #625 [Merged]

stock_inventory_discrepancy #622 [Merged]

stock_inventory_verification_request #630 [Merged]

@lukebranch @kittiu @ghost @emagdalenaC2i @hveficent @ageficent @aheficent may you help us here.

@microsound1
Copy link

Hi All,

Is it possible to have stock_inventory_revaluation for version 12.0?

@pedrobaeza
Copy link
Member

Well, this is a voluntary effort or driven by implementators' customers, so you can:

  • Migrate by yourself and propose a pull request here with the result.
  • Wait until another contributor does it.
  • Pay someone willing to do that migration.

@sotolucas
Copy link
Member

@kittiu are you planning to migrate stock_putaway_method and related?

@matt454357
Copy link

@microsound1,
I am planning to migrate stock_inventory_revaluation to version 12.0. I expect to have a PR in the next couple of weeks.

@rousseldenis rousseldenis unpinned this issue Oct 18, 2021
@github-actions
Copy link

github-actions bot commented Dec 5, 2021

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 Dec 5, 2021
@github-actions github-actions bot closed this as completed Jan 9, 2022
@rousseldenis rousseldenis reopened this Mar 10, 2022
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