{"push_id":980654387,"size":6,"distinct_size":6,"ref":"refs/heads/8.0","head":"5c69bbece16dc8564ed1b5d53160ae196940b887","before":"c961e59036d1d23dbd86595411d0a0c89259ac71","commits":[{"sha":"f35fd798f1f5c4846fabf004934202b833abedd0","author":{"email":"e7f5472e9a159f4d404f1091c7e345bf7ac1ddb0@odoo.com","name":"Odoo Translation Bot"},"message":"[I18N] Update translation terms from Transifex","distinct":true,"url":"https://api.github.com/repos/glovebx/odoo/commits/f35fd798f1f5c4846fabf004934202b833abedd0"},{"sha":"ce385829076e91ac31e452269e96e0c10741bd67","author":{"email":"8dd417b68ca1b41b9fae61f535fe0b5d847bdd55@odoo.com","name":"Denis Ledoux"},"message":"[FIX] mrp: update production quantity wizard factor\n\nUse the same factor than the one used when\ncomputing the products to consume at confirm.\n\nBefore, the quantity of products to consume was wrong\nwhen using a different unit of measure in the BOM\nthan in the production order.\n\ne.g.\n - BoM defined as:\n   - 1 dozen of milk\n   - BoM lines: 1 cow\n - Production order:\n   - 1 unit of milk\n   - BoM: The above one\nAt confirm, the quantity to consume is 0,083 cow (1 cow / 12, this is correct)\nBut, when updating the quantity to 2.0,\nit updated the quantity of cow to 24.0, instead of 0,16.\n\nopw-669447","distinct":true,"url":"https://api.github.com/repos/glovebx/odoo/commits/ce385829076e91ac31e452269e96e0c10741bd67"},{"sha":"5401345ce285c808d1b561e6a0256da9554b6924","author":{"email":"8dd417b68ca1b41b9fae61f535fe0b5d847bdd55@odoo.com","name":"Denis Ledoux"},"message":"[MERGE] forward port of branch 7.0 up to ce38582","distinct":true,"url":"https://api.github.com/repos/glovebx/odoo/commits/5401345ce285c808d1b561e6a0256da9554b6924"},{"sha":"7b445112bcab9288077fe1497d0dbce3f6f78ccb","author":{"email":"d7059304549ad870bd68ce8d2140db3326766135@roomsfor.hk","name":"Yoshi Tashiro"},"message":"[CLA] add contributor to roomsfor CLA\n\nAdding @manamirfhk\nCloses #10932","distinct":true,"url":"https://api.github.com/repos/glovebx/odoo/commits/7b445112bcab9288077fe1497d0dbce3f6f78ccb"},{"sha":"1d7c12022dcffce4792b9eec85706e19338cfa9f","author":{"email":"8dd417b68ca1b41b9fae61f535fe0b5d847bdd55@odoo.com","name":"Denis Ledoux"},"message":"[FIX] stock_account: valuation history with moves having multiple quant prices\n\nThe revision 29bd62252158803cdad351a2966af6eeac4cca74\naimed to improve the performance by changing\nthe view index, to use a BIGINT instead of a text.\n\nIt was assumed that the index used\n(`stock_move.id`) could not appear\nmultiple times with the JOINs and\ngroup bys defined.\n\nThis was in fact possible, if a\nstock move is associated to\nseveral quants with different costs,\nbecause of the JOIN on the many2many table\n`stock_quant_move_rel`\nlinking quants to moves,\nand the GROUP BY\n`price_unit_on_quant`\nthat caused the different moves/quants association\nnot to be merged within one unique line\nif the costs on the quants are different.\n\nInstead of the group by, we now aggregate the quants\ncosts, using the weighted average, so the index\nused can be unique, as expected.\n\nFrom now, the inventory value per line in\nthis report view can therefore\nbe different than what can be found on the quants,\nbut this report view is based on the stock moves\nrather than the stock quants, and this is therefore accepted.\n\nIn other words, the inventory value is computed for the stock move\nrather than for the stock quant.\n\nopw-658903","distinct":true,"url":"https://api.github.com/repos/glovebx/odoo/commits/1d7c12022dcffce4792b9eec85706e19338cfa9f"},{"sha":"5c69bbece16dc8564ed1b5d53160ae196940b887","author":{"email":"10dd0e7d18b53c78d54f0ba86a9f6926195ec858@163.com","name":"glovebx"},"message":"Merge pull request #148 from odoo/8.0\n\n8.0","distinct":true,"url":"https://api.github.com/repos/glovebx/odoo/commits/5c69bbece16dc8564ed1b5d53160ae196940b887"}]}