Patch Criteria: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{OLPC}} |
{{OLPC}} |
||
===Criteria for |
===Criteria for Creating a Patch Release=== |
||
Patch releases are to be used only for critical bug fixes. Here is a list of typical critical problems: |
Patch releases are to be used only for critical bug fixes. Here is a list of typical critical problems: |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
* Updates to support new versions of hardware (e.g. keyboards, revisions to major components) that cannot wait for the next major software release |
|||
| ⚫ | |||
Latest revision as of 16:52, 2 January 2008
This page is monitored by the OLPC team.
Criteria for Creating a Patch Release
Patch releases are to be used only for critical bug fixes. Here is a list of typical critical problems:
- Security issue that threatens anti-theft or child safety; or a known exploit that threatens a large number of laptops
- Datastore, Journal, or file-system problems resulting in loss of data
- Bug resulting in laptop crashes more frequently than 1/day with typical use
- Bug resulting in serious disruptions to other services (non-XO)
- A core feature or functionality that is not working or fails (e.g., Browse, Write, Read, Chat, power management, telepathy)
- Updates to support new versions of hardware (e.g. keyboards, revisions to major components) that cannot wait for the next major software release