NEXO: Difference between revisions
(merging) |
|||
| Line 1: | Line 1: | ||
'''NEXO''' is a collection of activities and other material designed for use on XOs in Nepal. (is it an entire XO image, from Fedora and Sugar to the full activity suite? If so, designed to boot from NAND, from an SD card, both?) |
|||
==For testers developers== |
|||
== |
== Development == |
||
| ⚫ | |||
Most NEXO development tasks can be grouped under 2 categories: |
|||
# Activity updates (or addition of new activities): this process is documented at [[NEXO activity updating]] |
|||
# Tweaks on top of underlying OLPC OS through pilgrim at /home/pilgrim: the internals are documented at [[NEXO build system]] |
|||
Before making any change, you should have fully tested it on an individual XO. At this point, you can make the change on the pilgrim box (192.168.5.233) as the pilgrim user. If your change involved changing anything under the pilgrim repository, please make sure to commit and push your changes. |
|||
Your change is now ready for inclusion in the next NEXO build, but there is one last step: Update [[NEXO release notes]] with your change. If you need to, create a new entry at the top of the page labelled simply "Unreleased development version" or similar (otherwise, append to the development entry that already exists). When released, the build master will assign an appropriate version number and release date and send the list of changes to the team. |
|||
After a new NEXS release has been deemed deployment-ready, update the [[NEXO]] page to state that this is the most recent stable release. |
|||
=== NEXS and NEXC development === |
|||
=== Notes for developers and testers === |
|||
| ⚫ | |||
Revision as of 08:36, 19 December 2009
NEXO is a collection of activities and other material designed for use on XOs in Nepal. (is it an entire XO image, from Fedora and Sugar to the full activity suite? If so, designed to boot from NAND, from an SD card, both?)
Development
Most NEXO development tasks can be grouped under 2 categories:
- Activity updates (or addition of new activities): this process is documented at NEXO activity updating
- Tweaks on top of underlying OLPC OS through pilgrim at /home/pilgrim: the internals are documented at NEXO build system
Before making any change, you should have fully tested it on an individual XO. At this point, you can make the change on the pilgrim box (192.168.5.233) as the pilgrim user. If your change involved changing anything under the pilgrim repository, please make sure to commit and push your changes.
Your change is now ready for inclusion in the next NEXO build, but there is one last step: Update NEXO release notes with your change. If you need to, create a new entry at the top of the page labelled simply "Unreleased development version" or similar (otherwise, append to the development entry that already exists). When released, the build master will assign an appropriate version number and release date and send the list of changes to the team.
After a new NEXS release has been deemed deployment-ready, update the NEXO page to state that this is the most recent stable release.
NEXS and NEXC development
Notes for developers and testers
- See also the NEXO Development Process