Accepted criterias for release

Get Started. It's Free
or sign up with your email address
Accepted criterias for release by Mind Map: Accepted criterias for release

1. JIRA

1.1. All issues regarding this release are complited and closed

1.2. Next release is created in JIRA

1.3. All not complited issues that have fix version of this release are moved to the next release/backlog

2. Customization description documents

2.1. Issue for updating customization description documents is created in JIRA

2.2. Documentation branch for the current release is created

2.3. Customization description documents are created based on the previous release documents

2.4. Contains info about all new features that can be congifured

2.5. Contains correct properties

2.6. The documents are approved (A/B/C revision)

2.7. PDF versions of the documents are created and committed to SVN

2.8. Tag for documentation branch is created

3. Product shelf

3.1. Test report is created

3.1.1. Contains the following sections

3.1.1.1. Summary

3.1.1.2. Test types

3.1.1.3. Outstanding issues

3.1.1.4. Functional testing

3.1.1.5. Regression testing

3.1.1.6. Compatibility testing

3.1.1.6.1. Contains info about devices'

3.1.1.7. Integration testing

3.1.1.7.1. Contains info about all systems used during testing

3.1.1.8. Documentation testing

3.1.1.9. Open bugs

3.1.1.10. Release recommendation

3.2. Confluence page for the current release (Mobile Games x.x.x.x)

3.2.1. Customization documents are attached and linked to the page (PDF versions)

3.2.2. Invalid links for documentation are removed

3.2.3. Release packages (games and helps) are available on Hanna

3.2.3.1. Smoke test of the games from the release package is done (itf it is neccessary)

3.3. Release notes

3.3.1. The following properties are defined

3.3.1.1. product

3.3.1.2. release number

3.3.1.3. release tags for games and help

3.3.1.4. archives' names in deliverables

3.3.1.5. another data should be changed as in the previous IPRN