All,

Although it might not be the most speedy method of development, I would like to suggest having Koolu as the main repository. I have talked with Michael Trimarchi and am in the process of devising a streamlined way to submit patches so that they can be integrated into the tree. I will post the process to this list a little bit later today.

To date, the Koolu releases have been slower to come out that some of the other individuals in the community. This was in part due to getting some of the infrastructure set up to facilitate this project, however, now that the infrastructure is in place, I expect that there will be more frequent releases. With that being said, it's important that each release gets tested to determine what works and what doesn't. In my opinion, daily builds on some of the Openmoko derived distributions fragments the QA process and testing.

I would encourage everyone to look at the test list at http://freerunner.android.koolu.com/test-plans-and-results . It gives an idea of the type of rigorous testing that I would like to see of Android on Freerunner. There will be more tests added to the list (and I would recommend people submit them to this list) moving forward. It's a start, but by no means exhaustive.

Also, I would ask that people submit bugs against the different releases in the trac at trac.koolu.com. That way we will have a central place to catalog all the open issues with Android on Freerunner, and start to close them out. I will be working on that as well today to ensure that the different subsystems and releases are available to file tickets against.

Lastly, thanks to everyone in the community that has shown interest in this project, and especially those that have contributed to help move it forward.

Best Regards,
Brian Code

_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org

Reply via email to