Release team working process

This is the way the release team is supposed to work.

Overview

The release team process consists of the following activities:

• Opening
• Testing
• Reviews
• Release assembly

Opening

This are the first things that the team should do after the official sprint opening:

• Create a branch from the trunk. The name should be further determined(perhaps something like release01 or release01-pre-alpha-2)
• Create a wiki page for the release. This will be ITERATION_<it_number>/Release
• Select tasks for testing. Sort them by their testability and importance
• Merge back valuable changes done on the previous release branch into the trunk

Testing

This refers to the last phase of a task's revision lifecycle.

It includes th following:

• Writing user documentation for each user related task
  • User documets are something like help
  • They describe what Sophie 2.0 features are available and the way the user can use them
• Writing release documentation where applicable
  • It describes shortly the released features
  • Describes non-user features
• Making manual test cases in our TestLink instance.
  • Each feature should have at least one new test case each revision.
  • Related test cases should be found and listed.
• Executing test cases
  • Execute newly created test case
  • Execute related test cases
• Reporting bugs that were found during the tests
• Have a look at related bugs - not exactly sure what this is(pap)

Reviews

• We should do reviews on implementations done by functional teams
• It this is needed we could help with desgin reviews