9.1.0 requirements: Difference between revisions
m (→Standard information: typo) |
DanielDrake (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
<b><font color=red><big>For information on current and future OLPC software releases, see [[Releases]]</big></font></b> |
|||
⚫ | |||
{{obsolete|link=[[Future releases]]}} |
|||
[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]]. |
|||
{{Deprecated}} |
|||
⚫ | |||
This page defined the requirements, schedule and overall planning for a release 9.1.0. |
This page defined the requirements, schedule and overall planning for a release 9.1.0. |
||
Line 165: | Line 167: | ||
= Standard information = |
= Standard information = |
||
<small>(These are all semantic annotations that other pages such as [[Releases]] can query.)</small> |
<small>(These are all semantic annotations that other pages such as [[Releases]] can query.)</small> |
||
[[Category:Releases]] |
|||
<!-- above lines maybe should be a template --> |
|||
Status: [[status::inactive]]. See [[Future releases]] and [[F11 for 1.5]] |
|||
Primary maintainer: not chosen yet |
|||
ECO: not yet |
|||
Primary objectives: |
Primary objectives: |
||
* was to have been a time-based release in 2009 per the process at: [[Release Process Home]]. |
* was to have been a time-based release in 2009 per the process at: [[Release Process Home]]. |
||
* Deployability |
* Deployability |
||
Lead |
Lead customers: Peru, Ethiopia, Uruguay, Haiti, Mongolia, Nepal and Rwanda |
||
Build number and URL: [[Build number::999]] |
|||
Schedule: N/A |
|||
[[Category:Releases]] |
[[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.
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. OverviewThis 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 strategyThis 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 maintainEasier 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:
Easier to maintain focuses on upgrading, keeping the XOs working, monitoring them and allowing recovery of data from errors.
Some examples include:
Greater reliability and performance
Primary release driversDate: March 7, 009 Customers: Rwanda, Peru, Ethiopia, Uruguay, Haiti, OLPC Birmingham, Mongolia, Ghana, Dubai, Lebanon FeaturesTop PriorityThe 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. 2 - Activation/lease/signing/image customization. A subset of the features in Category:Security, activation and deployability 3 - Power management. Some key features in Category:Power management 4 - Localization/translation. Second PriorityThese 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.
ActivitiesSign 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.)
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 -- ~~~~)
Lists of possible candidate activities
Schedule
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:
Lead customers: Peru, Ethiopia, Uruguay, Haiti, Mongolia, Nepal and Rwanda |