[UPG] Upgraded to version 8, fixed references to new 8.0 views and moved fields that were in product.product to product.template
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[UPG] stock available immediately, corrected the calculation method of
immediately_usable_qty to take in accountthe sign change in outgoing_qty
(from negative to positive) in version 8.
[FLAKE8]
[FIX] renaming of a class, comment removing, useless code.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[UPD] move out from unported to 8 for update
[fix] remove duplicate view and correct view name
[UPG][FIX] added outgoing field XML, that was in the base stock field in 7.0.
[FIX] renaming of a class, comment removing, useless code.
For weird reasons, force-assigning a move does not associate quants.
action_assign'ing the picking does, and is the same procedure that you
can do via the interface.
When setting the product quantities, force a small difference in the creation time.
This is important because Odoo then sorts the quantities by in_date, and when they all have the same time, sorting is a bit left to chance, and random integration errors are introduces
This is also closer to a real flow, as we woulnd't create 2 quantities at the same time.
