Meego Wiki
Views

Quality/QA-tools/OTS/Roadmap

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→OTS Roadmap)
Line 13: Line 13:
Study the viability of lower level extension points on the test results.
Study the viability of lower level extension points on the test results.
 +
 +
'''In progress'''
=== Goals ===
=== Goals ===
Line 24: Line 26:
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.
 +
 +
'''Released on 28th of January 2011.'''
=== Goals ===
=== Goals ===
Line 35: Line 39:
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.
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)
+
'''Released on 28th of september 2010.'''
=== Goals ===
=== Goals ===

Revision as of 14:00, 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.

In progress

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.

Released on 28th of January 2011.

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.

Goals

  • Fully functioning test system with installation documentation.
  • Anybody can setup an OTS instance and execute testruns.
  • Development moved to open source mode.
Retrieved from "http://wiki.meego.com/Quality/QA-tools/OTS/Roadmap"
Personal tools