Release Criteria Trial-2: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 6: Line 6:
# No kernel or X Window System crashes during test
# No kernel or X Window System crashes during test
# <5 High Priority bugs, that have a work around
# <5 High Priority bugs, that have a work around
# <20 Normal Priority bugs




'''Performance and System Criteria for release:'''
'''Performance and System Criteria for release:'''
# Every activity must meet basic functionality with and without network connectivity
# 3 activites can be opened, with wait times <10 seconds for any basic functionality
# Every activity that has been part of a group activity can work properly without connectivity to collaborator(s)
# Up to 5 XOs can collaborate on any one of the basic Activities
# Up to 5 XOs can collaborate on any one of the basic Activities
# XOs can successfully activate with school server
# XOs can successfully activate with school server
# XOs can backup user data to school server
# XOs can backup user data to school server
# B3s need to work in a mesh with B2s




Line 24: Line 25:




* Basic functionality - Each activity has basic functionality defined in the [[Activities]] page
NOTE: Basic and Secondary functionality - Each activity has basic and secondary functionality defined in the [[Activities]] page
* Secondary functionality - Activities must be able to use communications or collaboration capabilities. Must be able to open/edit/save across the mesh. This level of functionality would also include backup and restore of a file.

Latest revision as of 15:54, 24 May 2007

Release Criteria Trial-2

Bug Criteria for release:

  1. No known blocking bugs
  2. No kernel or X Window System crashes during test
  3. <5 High Priority bugs, that have a work around


Performance and System Criteria for release:

  1. Every activity must meet basic functionality with and without network connectivity
  2. Every activity that has been part of a group activity can work properly without connectivity to collaborator(s)
  3. Up to 5 XOs can collaborate on any one of the basic Activities
  4. XOs can successfully activate with school server
  5. XOs can backup user data to school server
  6. B3s need to work in a mesh with B2s


Definitions

  • Blocking bug - User cannot execute basic feature function
  • High Priority bug - User can work around or execute the basic feature, but is not able to perform a secondary function
  • Normal Priority bug - Should fix in this release; not affecting a basic or secondary functionality
  • Low Priority bug - Nice to fix, but not required for this release


NOTE: Basic and Secondary functionality - Each activity has basic and secondary functionality defined in the Activities page