← Back to team overview

linaro-project-management team mailing list archive

Re: Call for contribution - Linaro 12.10 development cycle highlights

 

On 26 November 2012 16:56, Jakub Pavelek <jakub.pavelek@xxxxxxxxxx> wrote:
>
> On 26 November 2012 13:06, Alexander Sack <alexander.sack@xxxxxxxxxx> wrote:
>>
>> On Mon, Nov 26, 2012 at 11:47 AM, Jakub Pavelek
>> <jakub.pavelek@xxxxxxxxxx> wrote:
>> >
>> > On 26 November 2012 10:35, Fathi Boudra <fathi.boudra@xxxxxxxxxx> wrote:
>> >>
>> >> On 26 November 2012 11:29, Alexander Sack <alexander.sack@xxxxxxxxxx>
>> >> wrote:
>> >> > On Tue, Oct 23, 2012 at 10:20 PM, Deepak Saxena <dsaxena@xxxxxxxxxx>
>> >> > wrote:
>> >> >> On 22 October 2012 04:30, Alexander Sack <alexander.sack@xxxxxxxxxx>
>> >> >> wrote:
>> >> >>> On Mon, Oct 22, 2012 at 12:23 PM, Fathi Boudra
>> >> >>> <fathi.boudra@xxxxxxxxxx> wrote:
>> >> >>>> Hi TLs/PMs,
>> >> >>>>
>> >> >>>> The initial wiki page for the cycle highlights is online:
>> >> >>>> https://wiki.linaro.org/Cycles/1210/Release/Highlights
>> >> >>>>
>> >> >>>> The initial page is auto-generated, based on the headline of the
>> >> >>>> implemented blueprints targeted for this development cycle.
>> >> >>>> The wiki page is mostly empty as *4* blueprints on *72* have been
>> >> >>>> implemented.
>> >> >>>>
>> >> >>>> Please, update the blueprints status and/or fill your respective
>> >> >>>> section ASAP.
>> >> >>>> Thanks in advance for your help.
>> >> >>>
>> >> >>> Amitk had the idea to get all the work items completed on all
>> >> >>> blueprints included in the initial higlights page and then have him
>> >> >>> hand edit based off that...
>> >> >>>
>> >> >>> Can we try that next month?
>> >> >>>
>> >> >>> From what I understand Amitk would have to move DONE work items to
>> >> >>> a
>> >> >>> Work Items (milestone): section in order to make it possible for us
>> >> >>> to
>> >> >>> extract that info automatically for him, right? Amit, does that
>> >> >>> sound
>> >> >>> reasonable to try out next month for PM blueprints?
>> >> >>
>> >> >> +1, would love to see this happen for KWG BPs too.
>> >> >
>> >> > Fathi: are we getting this info for kernel and power preseeded on
>> >> > highlight for manual editing this month?
>> >>
>> >> I was writing the call for contribution mail right now.
>> >> Highlights wiki page is already up-to-date.
>> >
>> >
>> > It seems to be really picky, took only two work items :(
>>
>> I guess if you go to your engineers and fix the WI section to better
>> reflect what was done for this month, Fathi would be willing to rerun
>> his script and update the highlights section to give you a better
>> start to edit :)
>
>
> The WI sections for KWG blueprints seem to be reflecting what was done just
> fine, yet almost none were picked by the scripting, like few examples:
> https://blueprints.launchpad.net/linux-linaro/+spec/android-lowmem-upstreaming
> https://blueprints.launchpad.net/linux-linaro/+spec/android-keyreset-upstreaming
> should have been picked.
>
> I think the issue is the formulation of "targeted to this cycle" - in KWG we
> target typically upstream kernel releases, meaning our series are
> upstreamlinux and our milestones are 3.7, 3.7 and 3.9. Looking at the items
> picked for this month's highlights, only blueprints that are not
> up-streaming work (like the one analyzing kernel size and writing a report)
> got picked up.

The issue here is your new milestone naming scheme. You introduced a
new serie/milestones breaking all tracking tools (including
status.l.o).
Last time you mentioned that changes, I recommended to discuss it with
a larger attendance and send a mail to announce your intent to change
the rules. It didn't happened, so I guess other things are broken.

> Do we have similar situation in the Android team with nothing being
> collected despite plenty of blueprints in 12.11?

No, it's because we do that only for KWG/PMWG. On Android, regular
rule applies: blueprint targeted to be delivered this cycle and
implemented.


Follow ups

References