The following changes since commit 8a9363c166dbe07bbb9f719a97e90d271f2789e5:
LINARO: Linaro-18.104.22.1687.12 (2010-10-11 12:45:09 -0600)
are available in the git repository at:
John Rigby (1):
meta-source/debian/changelog | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
The day-by-day schedule for Linaro@UDS is now available for viewing:
To get the most out of your Linaro@UDS experience you are strongly
encouraged to look at the schedule before this event and register your
interest in specific sessions, as described here:
Subscribing to sessions is helpful because you can then use the "Hide talks
that aren't for me" button to get a view of where you want to be when.
Linaro assignees will have already been subscribed to some sessions by their
technical leads where their participation is required, but all attendees
should feel welcome to participate in any sessions!
* Scheduling conflicts *
If there is a session that it's important that you participate in directly
that is scheduled before your arrival or after your departure, or if two
sessions are scheduled at the same time and you need to be present for both
of them, indicate this by marking yourself as "participation essential" for
each of these sessions and make sure that your arrival and departure times
are correctly recorded in your Linaro@UDS registration:
Please don't use this lightly. We have a whole week packed full of
interesting topics, and it's impossible for any of us to attend all the
sessions that we want to; that's why we have session minutes and wiki specs
afterwards, to help people catch up with discussions they couldn't be
present for. You should only mark yourself "participation essential" where
it would be important for us to reschedule a session around your
And please get any such requests into the system before the end of day on
Friday. We are unlikely to be able to accomodate schedule change requests
once the conference has started.
See you all next week in Florida!
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
The weekly report for the Linaro Infrastructure team may be found at:-
Status report: https://wiki.linaro.org/Platform/Infrastructure/Status/2010-10-21
The Infrastructure related blueprints, of which currently there are 4 active ones, are showing that there are 11 work items in progress (14 last week), and 12 work items to undertake (12 last week).
arm-m-validation-dashboard; 2 work items completed since last week; 2 in progress; 8 to do
arm-m-image-building-console; 1 work items completed since last week; 7 in progress; 3 to do
arm-m-automated-testing-framework; no change in status from last week; 1 in progress; 0 to do
arm-m-testsuites-and-profilers; no change in status from last week; 1 in progress; 1 to do
In arm-m-image-building-console, 6 items are awaiting review before they can be completed.
Preparations for UDS are occupying more of the team's time, with more tasks related to UDS being undertaken and completed that are not in blueprints.
Specifics accomplished this week include:-
* Three bugs fixed in abrek (Automated Test Framework) - two related to gtkperf, and one related to an IOException generated when quitting while piping the output.
* Two branches were merged back to the launch-control trunk
* OpenID (secure authentication) reviewed and landed for arm-m-validation-dashboard
Please let me know if you have any comments or questions.
We are nearly there ! Today marks the fourth installment of the weekly
testing saga, the last before Linaro@UDS happens. The -proposed queue
will be frozen on the 27th October to flush out any outstanding changes
before the release candidate image is produced on November 1st. As
always, If you have supported hardware and are willing to test the
images, please make your way to:
for an explanation on how to test and submit your results to the QA
Happy Testing !
Linaro Release Manager