AAI R2 Deliverables for Release Sign-Off Milestone Checklist Template

DRAFT PROPOSAL FOR COMMENTS

The following items are expected to be completed for the project to Pass  Release Sign-Off Milestone.

Release Sign-Off Milestone overview is available in wiki.



Usage

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.

  2. Fill out the Yes/No column

  3. Provide link to evidence (when necessary)

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Product Management

Are committed Product Backlog Stories been coded and marked as "Done" in Jira?

Yes

Getting issues...



Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira?

Yes



Provide the project features list under the form of a bulleted list.

Yes

  • AAI-17 Seed code stabilization

  • AAI-20 Champ Library

  • AAI-22 Amsterdam User Case Schema Updates

  • AAI-23 Model Loader Support for R1

  • AAI-58 Define and build functional test cases for CSIT

  • AAI-72 External System Register

  • AAI-254 Documentation of REST APIs, dev guides, onboarding, etc.

  • AAI-280 Confguration enhancements



Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off

N/A





Release Management

Have all issues pertaining to FOSS been addressed?

Yes





Have all findings from previous milestones been addressed?

Yes

Provide link to JIRA findings



Development

Are all the Jenkins jobs successfully passed (verify + merge jobs)?

Yes





Are all binaries available in Nexus Release repository?

Yes

Provide link to evidence



Are all Docker images available In Nexus?

Yes

Provide link to evidence



Are the Java and Docker manifest updated with the same version as in Nexus Release repository?

Yes





Integration and Testing


Have all CSIT Use Cases (created by each project team) passed?

Yes

Provide link to evidence

Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs

Has the project code successfully passed the Daily Build process?

Yes

Provide link to evidence

Goal is to ensure the latest project commit has not broken the Integration Daily Build 

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:

  1. Release Notes

  2. Project Documentation

Yes

ReadTheDocs Release Notes

ReadTheDocs Project Documentation