Dx-3 development notes

Repos: sugar-mainline-git http://git.sugarlabs.org/sugar/mainline git checkout -b <branch-name> v0.94.1 git am <all patches in dx3-oob-git rpms/sugar directory> sugar-toolkit, sugar-artwork dx3-oob-git http://git.sugarlabs.org/dextrose/mainline [bleeding edge branch] look in the rpms/sugar-* directories for the patches. rpm [ARM] http://download.sugarlabs.org/dextrose/testing/dx3/rpms/armv5tel/ [Dx3-x86-dev-repo] http://download.sugarlabs.org/dextrose/testing/dx3/rpms-next/i386/os/ stats server: A test server would be setup on a .sugarlabs.org domain stats: upstream repo (debian 6.0, ubuntu, fedora-14): http://download.sugarlabs.org/packages/Server:/Factory/ Stats system implementation notes: http://wiki.sugarlabs.org/go/Sugar_Server_Kit/Guide/Usage_Statistics builds: http://download.sugarlabs.org/dextrose/testing/dx3/xo1/ http://download.sugarlabs.org/dextrose/testing/dx3/xo1.5/ http://download.sugarlabs.org/dextrose/testing/dx3/xo1.75/ workflow: http://people.sugarlabs.org/anish/testing_workflow.png

• So for intl builds: I roll the rpms and resulting builds.
• For AU builds: I roll the rpms (which are the same as above, in the same repo), and Jerry rolls the builds with some AU specific customizations.
• For UY builds: Same, I roll the rpms (same repo), and Daniel or someone else in their team rolls the builds with Uy customizations.
• Submitting patches: Everyone has commit access to the OOB git repo, only restriction is that the patches should be tested before being committed.