- Period: (20110224-20110302)
Burndown information : http://status.linaro.org/linaro-infrastructure.html
Stakeholder process: https://wiki.linaro.org/Platform/Infrastructure/CurrentProjects
Key Points for wider discussion
firstname.lastname@example.org is not only receiving patches from a small proportion of Linaro assignees. Is everyone that submits patches upstream sending them here as well?
- Code registered as "svammel" on Launchpad.
- Progress is good to meeting the use case of the porter team. Initial tests with them were positive, and work has started on adding further features that they requested.
You can track progress at https://blueprints.launchpad.net/linaro/+spec/other-linaro-n-build-failure-bug-filing
- continues to produce builds in three configurations: panda, beagle, u8500href
- Is sporting a new interface that allows you to easily browse the available builds and download them
- work is progressing well to allow submitting new configurations to build easily through a web form
More patches submitted upstream to support our use cases: http://tinyurl.com/4wfkp4x
- Includes a UI for mass-moving patches from one project to another, which will allow Linaro assignees to easily correct errors in detecting the target of patches.
Process for getting this deployed as http://patch-tracking.linaro.org started
- Continuous Integration
- Testing of linaro-gcc cross-builds in the Continuous Integration environment done.
- Work started on deploying this as a service in ec2.
- status.linaro.org now colours the progress bars according to whether the progress is deemed good for the point we are at in the cycle. This provides an at-a-glance indication of which projects are at risk.
Linaro image builds now come with a report detailing the packages which changed since the previous build. e.g. http://snapshots.linaro.org/11.05-daily/linaro-nano/20110303/0/reports/linaro-natty-nano-tar-20110302-0.packages_linaro-natty-nano-tar-20110303-0.packages.bcct
- The status.linaro.org should be deemed complete for this round this week.
- linaro-image-tools will be getting a release soon (likely before the monthly release date to ease the process of getting it in to Ubuntu)
https://android-build.linaro.org/ will allow submitting new builds through a form on the website soon.
- Patch metrics for the next member report in two weeks.
Risks / Issues
- Mattias unable to work productively due to IT restrictions in ST-E (5 weeks, v. high): some progress. Has process now to request changes, but little response to his requests in more than 2 weeks. Mattias is working from home or over 3G in the meantime.
Deepti lacking a board to work with (many weeks, high): Deepti has received the Panda board, but doesn't have a USB->serial cable for it, so is still unable to use it for much. Working on tasks that don't require it, but unable to participate in image testing.
PatchTracking requires deploying Patchwork (3 weeks, high): Discussion with IS, and it is not expected to take them long to do once they get to it. They have indicated that they may be able to start at the end of next week, or in the week after.
- Gerrit instance needed for Android (3 weeks, high): Co-ordination with IS has started. Waiting to hear from them if we can get it this month, and what we need to do to help with that.
- Deepti believes she has not been granted travel to Linaro@UDS (1 weeks, high): She will attend remotely where possible.
- Mattias lacking a board to work with (5 weeks, medium): some progress, he has a board, but it spends most of the time being borrowed back by other people with ST-E. Mattias will work on a project that doesn't require a board in the meantime.
OurOwnOffspring lacking hardware (many weeks, medium): x86 for master is ready and waiting, XMs for slaves delivered to IS. Awaiting setup from IS.
- Want a Jenkins/Hudson instance for Continuous Integration purposes (many weeks, medium): Discussions with IS, and they will provide one, but timeframe is unclear at this point. Will host ourselves until IS can provide. Work on getting an ec2 instance for this has started, and we should have it running in ec2 by next week.
- Guilherme on national holidayys 7/8 March
- James on vacation 7th March
Guilherme at PyCon 10-15 March
- James away 21st March
- Deepti on vacation 11th March
internal/archive/Platform/LAVA/Infrastructure/Status/2011-03-03 (last modified 2013-08-23 12:19:34)