(→Goals) |
(→OTS Roadmap) |
||
| Line 26: | Line 26: | ||
* No functional changes from 0.1 release | * No functional changes from 0.1 release | ||
* APIs are stable enough for 3rd party plugin development in ots.server | * APIs are stable enough for 3rd party plugin development in ots.server | ||
| + | |||
| + | == OTS 0.9 unstable == | ||
| + | |||
| + | This release aims to collate the features of 6Pack and OTS. | ||
| + | |||
| + | The Conductor will be the main focus with particular attention paid to the variation points in the architecture and configurability. | ||
| + | |||
| + | Aim to have Python APIs in the Conductor (rather than the CL) | ||
| + | |||
| + | Study the viability of lower level extension points on the test results. | ||
| + | |||
| + | === Goals === | ||
| + | |||
| + | * Bring reliability of ots.server up to 0.1 standards | ||
| + | * A more coherent system | ||
| + | * 6Pack integration | ||
| + | * APIs are enough for 3rd party plugin development in ots.server | ||
Contents |
There are currently two main branches of development ongoing in OTS project.
This release is based on legacy code. Only minor refactoring is done. API:s are subject to change and development documentation will be very limited.
Released on 28th of september 2010. (Tag 0.1.0 in gitorious)
This release aims to address the issues that will naturally arise in moving from a closed source system maintained in-house to a widely distributed Open Source system. i.e. documentability support, a code base that supports distributed development.
Development goes on in "dev_branch_0.8"
This release aims to collate the features of 6Pack and OTS.
The Conductor will be the main focus with particular attention paid to the variation points in the architecture and configurability.
Aim to have Python APIs in the Conductor (rather than the CL)
Study the viability of lower level extension points on the test results.