...
- Necessary packages for the required features are developed and released to Development folder. (Also other regular developments and releases to packages continue )
- The selected packages for the next packaging release are selected and moved to testing launchpad.
- Packaging scripts are updated with any required configuration changes. Most of the manual configurations required for the packages are automated through the scripts to reduce the load on end user.
- A new instance of DATIM4U node is setup using the new packaging scripts. This instance is alpha tested from end to end to ensure existing and new functionalities are available for the end user.
- A developer instance is setup for developers and a demo instance is setup for the community (one of these can be the alpha tested server used in the earlier system). This acts as a alpha user testing.
- If any issues are encountered through step 3-5 the process repeats from 1 through 6. followed by alpha testing and developer nodes completely rebuilt and demo nodes are patched.
- After successful alpha testing, the packages and the scripts are promoted to production and the testing team are notified to begin their end to end testing, considered beta testing.
- If any issues are encountered by the testing team, most likely they are included in the consequent packaging release excepting minor modifications.
...