Xavier Morel 0e0348e4df [IMP] runbot_merge: preserve batch ordering in stagings ... Batch ordering in stagings is important in order to correctly reconstitute the full project history. In the old mergebot, since batches are created on the fly during staging this information is reified by the batch ids. But since batch ids are now persistent and there is no relationship between the creation of a batch and its merging (especially not relative to other batches) it's an issue as reconstituting sub-staging git history would be impossible. Which is not the worst, but is not great. The solution is to reify the join table between stagings and batches in order for *that* to keep history (simply via the sequential PK), and in converting to the new system carefully generate the new links in an order matching the old batch ids.		2024-05-29 07:55:07 +02:00
..
ir.model.access.csv	[IMP] runbot_merge: preserve batch ordering in stagings	2024-05-29 07:55:07 +02:00
security.xml	[FIX] runbot_merge: work with admin[uid=2]	2018-09-03 13:16:36 +02:00