← Back to team overview

linaro-infrastructure-stakeholders team mailing list archive

Re: Infrastructure Stakeholders Meeting 2011-08-11

 

Hi stephen,

we had patch tracking for quite a while being actively being worked
on. I very much would like to see agreement that we put further
features to patch tracking in the queue to give other projects a
chance of being worked on.

Did the member meeting explicitly express priority and expected
timeline for those features to become available?

On Thu, Aug 11, 2011 at 3:28 PM, Stephen Doel <stephen.doel@xxxxxxxxxx> wrote:
> Hi James,
>
> At the Linaro Members Meeting on Monday there were a couple of requests for
> patches.linaro.org (which has been well received):
>  1. Can we include a monthly stacked column showing patches per team
>  2. Can we link the patches to particular TSC requirements, or topic areas.
> We thought this might be hard, but we may be able to provide a better
> monthly update which we could also include in the Monthly Members Report
>
> Also, can we get an update on the changes planned to summit.linaro.org?
>
> Thx
>
> Stephen
>
> -----Original Message-----
> From:
> linaro-infrastructure-stakeholders-bounces+stephen.doel=linaro.org@xxxxxxxxx
> nchpad.net
> [mailto:linaro-infrastructure-stakeholders-bounces+stephen.doel=linaro.org@l
> ists.launchpad.net] On Behalf Of Alexander Sack
> Sent: 11 August 2011 14:01
> To: James Westby
> Cc: linaro-infrastructure-stakeholders@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Linaro-infrastructure-stakeholders] Infrastructure
> Stakeholders Meeting 2011-08-11
>
> thanks. looks very good. I agree with your proposed next projects.
>
> One thing I would like to see captured somewhere in current or
> really-soon projects is adding features to offspring
>
>  * to submit build success/failure to lava dashboard (should be
> trivial; maybe rather a bug?)
>  * to push output artifacts to LAVA for instant validation, like we do
> with android now (should be low effort).
>
> also looking forward to see toolchain build spec getting split up so
> we can make progress on this next big topic!
>
> On Thu, Aug 11, 2011 at 2:35 PM, James Westby <james.westby@xxxxxxxxxx>
> wrote:
>> Hi,
>>
>> Actions from last meeting:
>>
>>  * james_w to work with mounir and michaelh to split up the
>>    ToolchainBuilds spec to be more manageable: still TODO
>>
>> Report on current projects:
>>
>>  * Patch Tracking - This is up and running and working well. It is all
>>    but done, and will be complete a couple of days after Guilherme
>>    returns from vacation.
>>  * TestDrive - This is available since the last monthly release. At the
>>    Connect improvements to the GUI were designed, and will be worked on
>>    this week.
>>  * HardwarePacksv2 - After a delay due to vacation, this made progress
>>    at the Connect. It will hopefully be complete this month.
>>  * CI with LAVA - This made progress at the Connect with kernel builds
>>    now being submitted to LAVA. The number of kernels built needs to be
>>    increased, as well as some improvements to what is there.
>>  * Configure Gerrit - The switch to Gerrit for the Android team
>>    happened yesterday. There is still more to do in order to use Gerrit
>>    fully for its intended purpose, and that will happen this month.
>>
>>  * Next projects
>>    - Private Hardware Pack Builds - we now have a spec for this and
>>      work will start once TestDrive GUI has been changed, so next week
>>      or the week after. We estimate 6 weeks for this once it has started.
>>    - Improvements to status.linaro.org - This is going to be used to
>>      bring status.linaro.org inline with the new roadmap process, as
>>      discussed at the Connect. This will start once the HardwarePacksv2
>>      work is done.
>>
>>  * IS Queue
>>    - https://portal.admin.canonical.com/q/linaro
>>    - Meeting bot - almost complete
>>    - IRC names metrics - not scheduled
>>    - pad.linaro.org - not scheduled
>>    - pruning of builds on maprang (ubuntu-build.linaro.org) - waiting
>>      on code changes from us
>>    - Canonical conference line: Chinese numbers don't work - awating
>>      further info
>>
>> Proposed changes to the queues
>>
>>  * There is no slot free on the next projects queue, so we don't have
>>    to decide something to add there at this time.
>>  * I don't think there is anything more urgent that the current
>>    projects and next projects that would warrant changing them.
>>  * The IS Queue is small, and nothing in there is very high priority
>>    that I know of, so I don't think we need to reprioritise there.
>>
>> Possible upcoming projects
>>
>>  * Discussion of any projects that people want to propose in the near
>>    future.
>>
>> Thanks,
>>
>> James
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
>> Post to     : linaro-infrastructure-stakeholders@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
>
>  - Alexander
>
> _______________________________________________
> Mailing list: https://launchpad.net/~linaro-infrastructure-stakeholders
> Post to     : linaro-infrastructure-stakeholders@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~linaro-infrastructure-stakeholders
> More help   : https://help.launchpad.net/ListHelp
>
>
>



-- 

 - Alexander


Follow ups

References