The release consists of the test case description in XML format which is compatible with MeeGo test case template and can be executed under testrunner tool and test cases scripts for automated test cases. For each release, a release note will be composed, which indicates the changes in the release and known issues.
The handset-ux-test consists of packages. For each package, there is a named maintainer who is responsible to ensure that the quality criteria is met for the package for a release. Typically, one maintainer is responsible for multiple packages. The maintainer must also ensure that the package is be able to merged to the handset-ux-test master tree at release time.
The package maintainer manages his/her set of packages in a separate clones. Before release, the maintainer issues a merge request to handset-ux-test main git-tree. At release time, the maintainer issues merge requests to check in new code.
The handset-ux-test maintainer is responsible to create an handset-ux-test release. To achieve this, the handset-ux-test maintainer merges the pending merge requests at release time, pushes the merged codebase to main git-tree, tags git-tree and finalizes the release page in handset-ux-test test suite Wiki.
Monthly based release frequency is planned for handset-ux-test releases.
The detailed content of each releases and the content planned for next release will be maintained at handset-ux-test Releases page.
Please note that the handset-ux-test release process is evolving and not all details are complete. Feel free to suggest any improvements to the process.