9.1.0 requirements: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
(328 intermediate revisions by 32 users not shown)
Line 1: Line 1:
<b><font color=red><big>For information on current and future OLPC software releases, see [[Releases]]</big></font></b>
= Release 9.1.0 Overview =
This is a time based release per the process at: <br>
http://wiki.laptop.org/go/Release_Process_Home


[http://lists.laptop.org/pipermail/devel/2009-February/023079.html 9.1.0 was cancelled]. However, many of the planned features found their way into newer OLPC OS [[releases]].
The process is not final. It is a set of rough guidelines still being worked out and subject to change.


{{Deprecated}}
The goal (not confirmed) is to make this release public sometime between December, 2008 and June, 2009.
{{RightTOC}}


This page defined the requirements, schedule and overall planning for a release 9.1.0.
== Technical Strategy ==
Faster, more robust, better integration of activities, more collaboration...


[[Feature requests]] tracked features, requirements, and requests, and plans by customer;
== Sales - Deployment Strategy ==
[[Feature roadmap]] tracked all software features by technical strategy.
See customers below.


See also notes from [[XOcamp 2]] technical conference.
== Pedagogical Strategy ==
....


= Overview =
= Target Deployments =
This release is the first major new feature release after [[8.2.0]] Its is the first of two major feature releases we want to deliver in 2009. The target date for this release is March 7, 2009 (Note: date and feature set not final and subject to change).


This release must run on all existing XO hardware.


= Technical strategy =
This section outlines the main areas of technology that we will focus on improving. All of the specific features should address one of these primary concerns. The choice of these comes from listening to users and deployment leads and hearing what their concerns are.


The strategic priorities are to make the XO work the way users expect and help get the XO deployed more quickly in more countries.
= Priorities from Deployments =
Should list what, who and why on each item. Should link to detailed requirements and use cases eventually.


== Easier to deploy and maintain ==
== Touchpad ==
'''Easier to deploy''' focuses on facilitating the imaging of XOs, their activation, the installation and extension of custom leases and anything else needed to get the XOs from the factory in to the schools.
Some examples include: <br>
# Creating customization images (to include language packs and rpms)
# Installing images in the warehouse
# Activation and Leases


'''Easier to maintain''' focuses on upgrading, keeping the XOs working, monitoring them and allowing recovery of data from errors.
== Collaboration ==
Some examples include: <br>
# Upgrade in the schools
# Updating activities
# Reducing power consumption


== Performance and Reliability ==
== Greater reliability and performance ==
* No loss of data. Fewer crashes and fewer open bugs than 8.2 and previous releases. See also: http://wiki.laptop.org/go/User:Gregorio/8.2.0_release_criteria
Faster activity launching
* At the time of the release, works the way the manual says it works. That is, all of the things explained and listed in these manuals must work as described. <br>
6472
http://www.laptop.org/manual/ <br>
* Better performance includes faster GUI interactions. Includes launching activities, switching from one activity to another, using the journal and using the frame. GUI, activities, back ups.


== File Management ==
== Primary release drivers ==
Date: March 7, 009


Customers: [[Rwanda]], [[Peru]], [[Ethiopia]], [[Uruguay]], [[Haiti]], [[OLPC Birmingham]], [[Mongolia]], [[Ghana]], [[Dubai]], [[Lebanon]]
== Security Activation and Deployability ==


== Features ==


=== Top Priority ===
== Network Manager Connections ==
The following are critical must-deliver features for this release. The categories are listed in priority order. <br>
G1G1 encryption.


'''See all top priority features with details on one page [[Feature_roadmap/Page_of_all_features_that_target_9.1.0|here]]'''
802.11i (AKA 802.1x) Uruguay


Feature categorized in to the four main areas are list below: <br>


1 - Rebasing on F10 and allowing "regular" Fedora window managers and applications to run. <br>
== Unadorned or unedited user feedback ==
6th grade kids feedback on build 656: <br>
[[Feature roadmap/Rebase on Fedora 10|Rebase on Fedora 10]] <br>
[[Feature_roadmap/Run_Fedora_applications_on_XO|Run_Fedora_applications_on_XO]] <br>
http://sextosdela37.blogspot.com/2008/04/analizando-el-uso-de-las-laptop-en-el.html


2 - Activation/lease/signing/image customization. A subset of the features in [[:Category:Security, activation and deployability]] <br>
[[Feature_roadmap/Activation_lease_security|Activation_lease_security]] <br>
[[Feature_roadmap/Image_customization|Image_customization]] <br>
[[Feature_roadmap/Image_signing_key_delegation|Image_signing_key_delegation]] <br>
[[Feature_roadmap/Faster_imaging|Faster_imaging]] <br>
[[Feature_roadmap/Activation_via_wireless|Activation_via_wireless]] <br>


3 - Power management. Some key features in [[:Category:Power management]] <br>
Comments from technical user in Ecuador: <br>
[[Feature_roadmap/Improved_battery_life|Improved_battery_life]] <br>
http://lists.laptop.org/pipermail/olpc-sur/2008-July/000408.html
[[Feature_roadmap/No_power_regressions|No_power_regressions]] <br>
[[Feature_roadmap/Shutdown_menu|Shutdown_menu]] <br>


4 - Localization/translation. <br>
Not a teacher (I don't think) but a nice clear statement and format.
[[Feature_roadmap/SCIM]] <br>
[[Feature roadmap/Better Arabic Support]] <br>
[[Feature roadmap/RTL support]] <br>


=== Second Priority ===
# La XO no viene con un cliente IRC instalado por defecto.
These are very important features which benefit priority deployments. Any available engineer is encouraged to help with these, provided it does not take time away from working on the top priority features.
##It has no useful channels set to default activity news reader.
# La XO no tiene un portal que fomente la colaboración y el intercambio como página por defecto de la actividad Navegar.
##There is not an inventory of what activities can be used with mesh, nor what ways.
# No tiene canales útiles fijados por defecto para la actividad news reader.
##It has no useful channels set to default activity news reader.
# No existe un inventario de qué actividades se pueden utilizar con la malla, ni de qué maneras.
##There is not an inventory of what activities can be used with mesh, nor what ways.
# La malla sólo soporta algún tipo de colaboración en pequeños grupos.
##The mesh is only capable of certain forms of collaboration in small groups.
# Para cambiar la fecha es necesario clave de root.
##To change the date it is necessary to root password.
# Las XO no valen para imprimir.
##The XO is not able to print.
# Varias actividades que van por defecto en la XO no están localizadas.
##Several defauly installed activities on the XO are not localized.
# Los maestros tiene dificultad para subir imágenes a Blogs y Wikis.
##Teachers have trouble uploading images to blogs and wikis.
# Los maestros reportan que no se pueden guardar páginas de internet.
##Teachers report that they cannot save websites (bookmarks?).
# Muchas páginas web con Flash (en especial YouTube, y el webmail proporcionado en Uruguay) no funcionan.
##Many websites with Flash (especially YouTube, and webmail provided in Uruguay) do not work.
# Ninguna página con Java funciona.
##No pages with Java work.
# El formato de videos de la XO es incompatible con el estandar de facto de internet.
##The format videos of the XO is incompatible with the de facto Internet standard.
# No existe un método a nivel de usuario común para liberar espacio en disco.
##There is no method for the common user to free up disk space.
# La actividad Pippy no permite guardar programas propios.
##The activity Pippy does not allow programs to save themselves.
# La actividad para crear texto no tiene corrector ortográfico.
##The activity to create text does not have a spell checker.
# La XO no viene con una hoja de cálculo por defecto.
##The XO does not come with a spreadsheet by default.
# La XO no viene con un lenguaje de programación que los niños puedan aprender por defecto. Scratch viene por defecto? (no está en la imagen que yo tengo)
##The XO does not come with a programming language that children can learn by default. Scratch comes by default? (not in the image that I have)


# Performance http://wiki.laptop.org/go/Feature_roadmap/General_UI_sluggishness
== GUI and Usability ==
# Synchronous collaboration (reliability) http://wiki.laptop.org/go/Feature_roadmap/Synchronous_collaboration
Request from Uruguay for HW alerts: <br>
# Asynchronous collaboration http://wiki.laptop.org/go/Feature_roadmap/Asynchronous_collaboration
http://lists.laptop.org/pipermail/sugar/2008-July/007086.html
# Flash


= Activities =
Designs ideas from Scott and Eben in thread.
Sign in to the wiki and leave your suggestion for any activities you think we should install by default here.
e.g. I hope our alert system will use the freedesktop.org standard:
http://www.galago-project.org/specs/notification/index.php


Each activity will need a maintainer, latest version, and a [[Test_cases|test case]] to be considered for the release.
= Priorities from Engineering =
4662 needed for better activity capabilities. <br>
2447 caps lock <br>
1997 flashing in write <br>
NAND full crashes system:<br>
I think analyzing performance of non-JFFS2 file systems and picking
a replacement should be a high-priority item for 9.1 update.<br>
from: http://lists.laptop.org/pipermail/devel/2008-July/016994.html


The maintainer is the [[Property:Contact person]] on the activity's wiki page (click [Edit with form] and modify "Maintainer's user page" to update). The .xo URL and version for 9.1.0 should be in the activity's Activities/''My activity''_(latest) fragment, e.g. [[Activities/Chat_(latest)]]. ''(If this latest version is incompatible with [[8.2.0]], make sure that [[Activities/G1G1/8.2]] does not reference it.)''
= Key Modules and Relevant Module Roadmaps =

{|class="wikitable"
|+ '''Default Activities for 9.1.0'''
|-
!Name
!"(latest)" fragment
!Documentation
!URL to Test Case
!License status
!Status
! Comments
|-

|-
|[[Chat]]
|[[Activities/Chat (latest)]]
|[[Chat]]
|
|GPLv2+
|Accepted pending final tests.
|

|}

''' Please help add all potential activities to this table. Add as much info as you have and leave the rest blank.'''

=== Nominations ===
''(sign your nominations with <tt><nowiki>--&nbsp;~~~~</nowiki></tt>)''
* I nominate [[Develop]]. Version and test case upcoming. [[User:Homunq|Homunq]] 15:04, 10 December 2008 (UTC)

* I nominate [[StarChart]] (http://www.wa1gsf.net/downloads/XO/StarChart-5.xo) version 5 maintained by [[User:davewa|David Wallace]], licensed under GPLv2+. Note that Version 6 is in development and will have 2 more features and should be i18n-ed. Release of v.6 was planned for 1/1/09 but is slipping (because I don't understand how to get the mouse click event). -- [[User:Davewa|Davewa]] 19:39, 10 December 2008 (UTC); edited Jan 6, 2009
* I nominate SimCity http://wiki.laptop.org/go/Simcity and/or Micropolis, preferably Micropolis if we can get good response from a maintainer. [[User:Gregorio|Gregorio]] 15:21, 11 December 2008 (UTC)

* I nominate [[Image_Viewer]] and [[Jukebox]]. [[User:Sayamindu|Sayamindu]] 20:30, 17 December 2008 (UTC)

=== Lists of possible candidate activities ===
* [[Activities/G1G1/8.2]] is the list of activities that the [[Software updater]] installs and upgrades on [[G1G1]] machines running [[Release notes/8.2.0|Release 8.2.0]].
* The following activities have [[Property:Activity group|Activity group]] Activities/G1G1 checked on their wiki page, as of 2008-12-10 the names exactly match [[Activities/G1G1/8.2]] (good!):
: {{#ask: [[Activity group::Activities/G1G1]] | format = list}}
* [[Activity queries]] has a sortable list of every wiki page in [[:Category:Activities]], and other counts and queries of activities.
* As of December 3rd 2008, the following activities have test pages but aren't in the Activities/G1G1 list above.
: [[Clock]], [[Colors!]] (was Color?) [[Comic]] (not sure what this is), [[GCompris]]-Chess, [[GCompris]]-Sudoku, [[License]], [[x2o]]
:: (The full list of activities with test pages is<br>Analyze, Browse, Calculate, Clock, Color, Comic, Distance (now Acoustic Tape Measure), Etoys, Gcompris-Chess, Gcompris-Sudoku, Help, Implode, Log, Maze, Measure, Memorize, Moon, Paint, Pippy, Read, Record, TurtleArt, x2o )
* During [[8.1.0]] ("Update.1") planning around March 2008, [[Elements]], [[License]], and [[Xo-get]] were to be considered for a future [[G1G1 activity pack]]
* The following activities are (misplaced) in [[:Category:Activity bundle]] but don't use the the semantic form; so they have a .xo file yet are not in many queries
:: [[Comic Maker]], [[Firefox]], [[Games/Productive]], [[HablarConSara]], [[HelloMesh]], [[Image Viewer]], [[Lambda]], [[Pacman]], [[Physics]], [[PlayGo]], [[Rollcats]], [[Turtle Art/lang-es]], [[XO-GCC]], [[Xo-get/Xo-get-gtk]], [[XoIRC]]
* [[Activities]] claims to be the full set of OLPC hosted activities.
* [[Activities/All]] is inaccurately titled, it's a manually-updated list of activities.
* a previous listing of activities and status on Google Docs (on the "Matrix deprecated" tab) is at http://spreadsheets.google.com/ccc?key=p_Xhb6KcXLyEViA50CnCaDg&hl=en

= Schedule =
* December 5 - Agree and document on Trac usage. Tag critical features for 9.1.0 on roadmap page and linked on 9.1.0 page.
* December 12 - Trac scrub underway bugs targeted for inclusion in 9.1.0 flagged. First pass at requirements definition done for all main features.
* December 19 - Scrub of all past Trac bugs completed. Last round of comments on requirements. First pass at specification write ups. Rough scoping recorded and engineers assigned.
* December 24 - Branch strategy defined and check in branch chosen (Joyride?). Weekly bug triage begun.
* January 7 - Presentations for XO Camp shared. All specifications posted and reviews scheduled. Code reviews scheduled as needed. Designs of major features shared with key customers for confirmation and comment.
* January 12 to 15 - XO Camp held. http://wiki.laptop.org/go/XOcamp_2.
* January 16 - Sugar 0.83 string/API/feature freeze. See: http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap
* January 23 - Code for all major features in branch. Alpha test begun. Daily bug triage begun. Something similar to [[Release_Process_Home#Steam_Milestone|Steam]] milestone announced.
* January 30 - Beta test begun. Must fix bugs listed in Trac. Release notes started.
* February 9 - First Release Candidate built. Regression test defined. List of target activities to include in default image chosen. Something similar [[Release_Process_Home#Water_Milestone|Water]] milestone announced.
* February 16 - Second release candidate chosen. Default activities tested. Something similar to [[Release_Process_Home#Ice_Milestone|Ice]] announced. Penultimate regression test set. Release notes new feature section, final edit. Open bugs section started.
* February 28 - Final release candidate chosen. Image sent to Quanta for factory verification. Final regression test done. Upgrade tests done for release notes.
* March 7 - Quanta ships first XO with new image. Final release notes written and reviewed. On time release!
* March 8 - Release announcement sent out.


Possible QA milestones: <br>
- Start creating test cases for each feature. <br>
- Finish creating test cases. <br>
- Execute all test cases once. <br>

First stab at schedule done by [[User:Gregorio|Gregorio]] 18:50, 2 December 2008 (UTC)

= Standard information =
<small>(These are all semantic annotations that other pages such as [[Releases]] can query.)</small>

Primary objectives:
* was to have been a time-based release in 2009 per the process at: [[Release Process Home]].
* Deployability

Lead customers: Peru, Ethiopia, Uruguay, Haiti, Mongolia, Nepal and Rwanda
[[Category:Releases]]

Latest revision as of 15:56, 10 February 2011

For information on current and future OLPC software releases, see Releases

9.1.0 was cancelled. However, many of the planned features found their way into newer OLPC OS releases.

Stop hand.png WARNING:
The content of this section is considered
DEPRECATED and OBSOLETE
It is preserved for historical or documenting reasons.


This page defined the requirements, schedule and overall planning for a release 9.1.0.

Feature requests tracked features, requirements, and requests, and plans by customer; Feature roadmap tracked all software features by technical strategy.

See also notes from XOcamp 2 technical conference.

Overview

This release is the first major new feature release after 8.2.0 Its is the first of two major feature releases we want to deliver in 2009. The target date for this release is March 7, 2009 (Note: date and feature set not final and subject to change).

This release must run on all existing XO hardware.

Technical strategy

This section outlines the main areas of technology that we will focus on improving. All of the specific features should address one of these primary concerns. The choice of these comes from listening to users and deployment leads and hearing what their concerns are.

The strategic priorities are to make the XO work the way users expect and help get the XO deployed more quickly in more countries.

Easier to deploy and maintain

Easier to deploy focuses on facilitating the imaging of XOs, their activation, the installation and extension of custom leases and anything else needed to get the XOs from the factory in to the schools. Some examples include:

  1. Creating customization images (to include language packs and rpms)
  2. Installing images in the warehouse
  3. Activation and Leases

Easier to maintain focuses on upgrading, keeping the XOs working, monitoring them and allowing recovery of data from errors. Some examples include:

  1. Upgrade in the schools
  2. Updating activities
  3. Reducing power consumption

Greater reliability and performance

  • No loss of data. Fewer crashes and fewer open bugs than 8.2 and previous releases. See also: http://wiki.laptop.org/go/User:Gregorio/8.2.0_release_criteria
  • At the time of the release, works the way the manual says it works. That is, all of the things explained and listed in these manuals must work as described.

http://www.laptop.org/manual/

  • Better performance includes faster GUI interactions. Includes launching activities, switching from one activity to another, using the journal and using the frame. GUI, activities, back ups.

Primary release drivers

Date: March 7, 009

Customers: Rwanda, Peru, Ethiopia, Uruguay, Haiti, OLPC Birmingham, Mongolia, Ghana, Dubai, Lebanon

Features

Top Priority

The following are critical must-deliver features for this release. The categories are listed in priority order.

See all top priority features with details on one page here

Feature categorized in to the four main areas are list below:

1 - Rebasing on F10 and allowing "regular" Fedora window managers and applications to run.
Rebase on Fedora 10
Run_Fedora_applications_on_XO

2 - Activation/lease/signing/image customization. A subset of the features in Category:Security, activation and deployability
Activation_lease_security
Image_customization
Image_signing_key_delegation
Faster_imaging
Activation_via_wireless

3 - Power management. Some key features in Category:Power management
Improved_battery_life
No_power_regressions
Shutdown_menu

4 - Localization/translation.
Feature_roadmap/SCIM
Feature roadmap/Better Arabic Support
Feature roadmap/RTL support

Second Priority

These are very important features which benefit priority deployments. Any available engineer is encouraged to help with these, provided it does not take time away from working on the top priority features.

  1. Performance http://wiki.laptop.org/go/Feature_roadmap/General_UI_sluggishness
  2. Synchronous collaboration (reliability) http://wiki.laptop.org/go/Feature_roadmap/Synchronous_collaboration
  3. Asynchronous collaboration http://wiki.laptop.org/go/Feature_roadmap/Asynchronous_collaboration
  4. Flash

Activities

Sign in to the wiki and leave your suggestion for any activities you think we should install by default here.

Each activity will need a maintainer, latest version, and a test case to be considered for the release.

The maintainer is the Property:Contact person on the activity's wiki page (click [Edit with form] and modify "Maintainer's user page" to update). The .xo URL and version for 9.1.0 should be in the activity's Activities/My activity_(latest) fragment, e.g. Activities/Chat_(latest). (If this latest version is incompatible with 8.2.0, make sure that Activities/G1G1/8.2 does not reference it.)

Default Activities for 9.1.0
Name "(latest)" fragment Documentation URL to Test Case License status Status Comments
Chat Activities/Chat (latest) Chat GPLv2+ Accepted pending final tests.

Please help add all potential activities to this table. Add as much info as you have and leave the rest blank.

Nominations

(sign your nominations with -- ~~~~)

  • I nominate Develop. Version and test case upcoming. Homunq 15:04, 10 December 2008 (UTC)

Lists of possible candidate activities

{{#ask: Activity group::Activities/G1G1 | format = list}}
  • Activity queries has a sortable list of every wiki page in Category:Activities, and other counts and queries of activities.
  • As of December 3rd 2008, the following activities have test pages but aren't in the Activities/G1G1 list above.
Clock, Colors! (was Color?) Comic (not sure what this is), GCompris-Chess, GCompris-Sudoku, License, x2o
(The full list of activities with test pages is
Analyze, Browse, Calculate, Clock, Color, Comic, Distance (now Acoustic Tape Measure), Etoys, Gcompris-Chess, Gcompris-Sudoku, Help, Implode, Log, Maze, Measure, Memorize, Moon, Paint, Pippy, Read, Record, TurtleArt, x2o )
Comic Maker, Firefox, Games/Productive, HablarConSara, HelloMesh, Image Viewer, Lambda, Pacman, Physics, PlayGo, Rollcats, Turtle Art/lang-es, XO-GCC, Xo-get/Xo-get-gtk, XoIRC

Schedule

  • December 5 - Agree and document on Trac usage. Tag critical features for 9.1.0 on roadmap page and linked on 9.1.0 page.
  • December 12 - Trac scrub underway bugs targeted for inclusion in 9.1.0 flagged. First pass at requirements definition done for all main features.
  • December 19 - Scrub of all past Trac bugs completed. Last round of comments on requirements. First pass at specification write ups. Rough scoping recorded and engineers assigned.
  • December 24 - Branch strategy defined and check in branch chosen (Joyride?). Weekly bug triage begun.
  • January 7 - Presentations for XO Camp shared. All specifications posted and reviews scheduled. Code reviews scheduled as needed. Designs of major features shared with key customers for confirmation and comment.
  • January 12 to 15 - XO Camp held. http://wiki.laptop.org/go/XOcamp_2.
  • January 16 - Sugar 0.83 string/API/feature freeze. See: http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap
  • January 23 - Code for all major features in branch. Alpha test begun. Daily bug triage begun. Something similar to Steam milestone announced.
  • January 30 - Beta test begun. Must fix bugs listed in Trac. Release notes started.
  • February 9 - First Release Candidate built. Regression test defined. List of target activities to include in default image chosen. Something similar Water milestone announced.
  • February 16 - Second release candidate chosen. Default activities tested. Something similar to Ice announced. Penultimate regression test set. Release notes new feature section, final edit. Open bugs section started.
  • February 28 - Final release candidate chosen. Image sent to Quanta for factory verification. Final regression test done. Upgrade tests done for release notes.
  • March 7 - Quanta ships first XO with new image. Final release notes written and reviewed. On time release!
  • March 8 - Release announcement sent out.


Possible QA milestones:
- Start creating test cases for each feature.
- Finish creating test cases.
- Execute all test cases once.

First stab at schedule done by Gregorio 18:50, 2 December 2008 (UTC)

Standard information

(These are all semantic annotations that other pages such as Releases can query.)

Primary objectives:

  • was to have been a time-based release in 2009 per the process at: Release Process Home.
  • Deployability

Lead customers: Peru, Ethiopia, Uruguay, Haiti, Mongolia, Nepal and Rwanda