Milestone 1 Release Criteria

[jimmarino]

@paullatzelsperger and I created this issue to compile the criteria for our Milestone 1 release, which we are doing in partnership with Catena-X.

We have broken down the deliverable into two top-level categories: EDC Functionality; and the Catena-X Milestone Deliverable. All items are currently set to mandatory.

1. EDC Functionality Deliverable

Contract Offer

• IDS Multipart handlers need to be cleaned up and merged (Denis, PR #285 ) Due Monday
• Verify contract offer request flow (message dispatchers and handlers) (Denis, Dominik, #306) Due Tuesday
• Verify that asset Index supports IN criterion (Jim and Paul, #307) Due Monday
• Verify Policy subsystem integration (Jim #308) Due Tuesday

Contract Negotiation

• In progress (Julia and Ronja, #284 ) Due Wednesday
• Implement Cosmos ContractNegotiationStore (Paul #309) Due Thursday

Data Transfer

• Data transfer needs to use TPM instead of TPS (Brendan and Paul, #301) Due Tuesday

Control API

• Implement a security filter (Denis #302) Due Monday
• Implement a control endpoint to return contract offers to a client (Denis, #303) Due Monday
• Implement a control endpoint to handle contract negotiation (Ronja and Julia, #304) Due Wednesday

Artifact Release Pipeline

(Paul, Andrea #305)
Due Wednesday

• Version EDC starting at 0.0.1
• Every successful build on main creates a snapshot (Not mandatory, workaround is to publish to Maven local)

Samples and Documentation

(Andrea)
Due Thursday

• Verify all samples and documentation

2. Catena-X Milestone Deliverable

(Andrea and Paul)

The Milestone Deliverable consists of a Repository, Sample Data, and an Azure Deployment. The repository will be a dedicated one for Catena-X outside of the EDC organization. This will demonstrate how to consume EDC published binaries. This should be done by one of the participants. Andrea, can you?

Build System

• Create a simple Gradle multi-module build.

Launchers

Due Wednesday

• Consumer/provider launchers (based on sample 5)
• Properties configuration (for local execution)
• Docker file for Azure deployment
• Publish Docker images to a Docker repo

Data Loaders

Due Wednesday

• Sample assets, contract definitions (policies) are generated.

Deployment

Due Thursday

• Terraform files for populating Vault
• Data Loaders are executed through Terraform (?)
• DAPS is deployed and configured through Terraform
• Terraform is used to deploy any other required resources

Documentation

Due Thursday

• How to build the repository and set up a local and Azure-based deployment environment