Content
View differences
Updated by Bruno Pagno 5 days ago
The goal is We want to replace version usage everywhere so that we represent a many to many relationship between WorkPackage & Version
A WorkPackage can rely on target\_versions as being the single source have many versions of truth. This should not cause any product behaviour changes, only transform how we use data. different types ("target"/"observed\_in")
A Version can be associated to many different WorkPackages
<br>
Goal:
create a new table work\_package\_associated\_versions with:
* make sure write operations properly persist the data in target\_versions id
* make sure all subsystems read from target\_versions, version\_id
* work\_package\_id
* kind (target | observed\_in)
This table can represent any associated versions (both target/observed\_in and ignore version
<br> any other types we may invent in the future)
A WorkPackage
<br>
Goal:
create a new table work\_package\_associated\_versions with:
* make sure all subsystems read from target\_versions,
* work\_package\_id
* kind (target | observed\_in)
This table can represent any associated versions (both target/observed\_in
<br>