Meego Wiki
Views

Quality/QA-tools/OTS/Roadmap

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(OTS Roadmap)
Line 1: Line 1:
= OTS Roadmap =
= OTS Roadmap =
-
There are currently two main branches of development ongoing in OTS project.
 
-
== OTS 0.1 unstable ==
+
== OTS 0.9 ==
-
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.
+
[https://bugs.meego.com/showdependencytree.cgi?id=10866&hide_resolved=0 Status]
-
Released on 28th of september 2010. (Tag 0.1.0 in gitorious)
+
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 ===
=== Goals ===
-
* Fully functioning test system with installation documentation.
+
* Bring reliability of ots.server up to 0.1 standards
-
* Anybody can setup an OTS instance and execute testruns.
+
* A more coherent system 
-
* Development moved to open source mode.
+
* 6Pack integration
 +
* APIs are  enough for 3rd party plugin development in ots.server
-
== OTS 0.8 unstable ==
+
== OTS 0.8 ==
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.
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"
 
=== Goals ===
=== Goals ===
Line 27: Line 31:
* 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 ==
+
== OTS 0.1 ==
-
This release aims to collate the features of 6Pack and OTS.  
+
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.
-
The Conductor will be the main focus with particular attention paid to the variation points in the architecture and configurability.
+
Released on 28th of september 2010. (Tag 0.1.0 in gitorious)
-
 
+
-
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 ===
=== Goals ===
-
* Bring reliability of ots.server up to 0.1 standards
+
* Fully functioning test system with installation documentation.
-
* A more coherent system 
+
* Anybody can setup an OTS instance and execute testruns.
-
* 6Pack integration
+
* Development moved to open source mode.
-
* APIs are  enough for 3rd party plugin development in ots.server
+

Revision as of 13:54, 3 February 2011

Contents

OTS Roadmap

OTS 0.9

Status

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

OTS 0.8

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.

Goals

  • Good developer documentation
  • No functional changes from 0.1 release
  • APIs are stable enough for 3rd party plugin development in ots.server

OTS 0.1

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)

Goals

  • Fully functioning test system with installation documentation.
  • Anybody can setup an OTS instance and execute testruns.
  • Development moved to open source mode.
Personal tools