[16.0][FIX] stock_available_to_promise_release: Refactor release_ready compute

[jbaudoux]

Fix missing migration of last commit in #808

@RodrigoBM @lmignon @sbejaoui @mt-software-de

[RodrigoBM]

Why does the test give error if it is corrected?

[mt-software-de]

Why does the test give error if it is corrected?

Good question. And why it was not raised here #808

[RodrigoBM]

Why does the test give error if it is corrected?

Good question. And why it was not raised here #808

I think the CI is running v16.0 code and not PR code. is it possible @sbidoul?

[sbidoul]

It's not normal indeed that stock_available_to_promise_release is installed in that preparation step. I'll have a look.

[sbidoul]

I see. It's a case of circular dependencies between repos.

Something here in OCA/wms depends on stock_move_auto_assign_auto_release (in OCA/stock-logistics-warehouse), which itself depends on stock_available_to_promise_release here in OCA/wms. This causes odoo-addon-stock_available_to_promise_release to be installed from PyPI in the preparation step. This would normally not be an issue, but since the released version does not even install we are stuck.

Strictly speaking it's a bug in OCA/oca-ci. I'll think about a solution.

[sbidoul]

It's not normal indeed that stock_available_to_promise_release is installed in that preparation step.

So to be precise, it is normal that it is installed in the preparation step, but we need to install the version of this repo.

[jbaudoux]

@sbidoul Thanks for the analysis. Can we already merge this PR? The tests are ok in local.

[sbidoul]

Merged manually to unblock. I'll need some time to test a proper fix for the CI.

[RodrigoBM]

Merged manually to unblock. I'll need some time to test a proper fix for the CI.

But @sbidoul if this is already merged why is it still giving error in my PR. I think there is something that I don't understand about CI!

Thank you very much for your time!!

[sbidoul]

When we merge manually, we need to wait for the nightly build.