procurement module (where stock.move.group was defined) does not depend on the stock module
the same grouping system could be used for services too
procurement.group
removed sequence_id field
put a default values on the name field, using a defined sequence
renamed "Move Group" into "Procurement Requisition"
procurement object:
location_id should not come from the customer property but should be stored on the procurement (set by the sale order, using the customer property)
bzr revid: fp@tinyerp.com-20130629091328-5gc39647aa2pymlf
A programming error during an older refactoring lead to
the scheduler working with a single monolithic transaction.
This could cause unnecessary resource contention, plus
undesired rollback of all previous operations in the event
of an exception during scheduling.
bzr revid: odo@openerp.com-20130701163532-8bekn7sbb99ua08c