Pavel Shukhman
Pavel Shukhman
Took a stab at combining Olle's original proposal with what I had in the API based on our research at Reliza and definitions above. Would appreciate feedback. _Component is a...
Alternative chart version that fits some additional use-cases: _Here a Variant is a physical package that the client receives. And a Collection is a set of Variants that are marketable...
That came up in conversation with Steve on a Koala's call when you were away. The reason is that certain fields differ between BOMs and attachments. It's possible to unify...
Also refer to #155 (this is partly duplicating).
@ppkarwasz This model can work, but I feel it leads to some undesired duplication. In your scenario, I would have separate entry for **Server A** as a Product and **Server...
The key point here is that in Piotr's example **Server A** itself may consist of multiple components - thus being a **Product**. However, treating it as a **Component** in **All...
> This discussion also makes me question whether we should even differentiate between TEA Products and TEA Components. After all, they share the same data model fields. Great point! On...
This will be resolved with #196 - you can have multiple TEIs per product release.
As also mentioned in the other thread I would suggest **Release** -> **Deliverable** model, where a Deliverable is an actual packaged representation of what is released, i.e. a .zip file....
There are great ideas here, but I feel like the logic breaks when we try to define the concepts of "unversioned product" and "latest versions of components". Observe that: -...