Practice Area | Checkpoint | Yes/No | Evidences |
---|
How to? |
|
---|
Product Management | Are committed Product Backlog Stories been coded and marked as "Done" in Jira? | Yes |
Link to JiraLink to JiraLink to evidence | Yes | - Pub/sub messaging metaphor to broaden data processing opportunities
- A single solution for most event distribution needs to support a range of environments
- Standardized topic names
- Implements a RESTful HTTP API for provisioning
- Implements a RESTful HTTP API for message transactions (i.e. pub, sub)
- Implements a RESTful HTTP API for transaction metrics
- Topic registry and discovery
|
|
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | N/A | Committed content delivered; Known issues and constraints are documented in Release Notes |
|
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | No open issues on DMaaP FOSS for Amsterdam Release |
|
Have all findings from previous milestones been addressed? | Yes |
Provide link to JIRA findingsProvide link to evidenceProvide link to evidenceGoal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT JobsProvide link to evidence | Provide link to evidence | Goal is to ensure the latest project commit has not broken the Integration Daily Build https://jenkins.onap.org/view/dmaap/ |
|
Has the project done the integration testing with related dependent projects? | Yes |
|
|
Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs: - Release Notes
- Project Documentation
| Yes |
Provide Link to ReadTheDocs Release Notes
Provide Link to ReadTheDocs Project Documentation