linaro-project-management team mailing list archive

[Joey Stanford <joey@xxxxxxxxxx>]

Good topic Mounir.

For the release meetings themselves I think the status bit should be
changed to a blueprint review.

For regular status reports, I read them. All of them.  Including ones
that the TL's send.  We optimized them significantly at UDS so they
aren't too cumbersome.  I do not read the meeting log though.

J

On Thu, Jul 7, 2011 at 3:09 PM, Mounir Bsaibes
<mounir.bsaibes@xxxxxxxxxx> wrote:
> Hi Joey,
> You were present today during the release meeting when the issue about
> status report was raised.
> The concern from the release management is that the weekly status report is
> not being looked at and may be a waisted overhead.
> Instead, they prefer to replace the status review slot with a review of the
> blueprints targeted for the milestone, checking whether these blueprints
> have all what is needed for the release.
>
> I think we should circle back and see how useful the weekly reports are, who
> consumes them and how up to dates are kept.
>
> It maybe that the release management / release management meetings are not
> the only audience and we should keep them regardless of what the RM thinks.
>
> In any case, it is a good idea to check back on this activity, whether to
> continue with it or not.
> If we can't resolve it through emails,  it maybe a good topic for the August
> Connect meeting.
>
> If we decide to keep doing it, we need to re-educate the TL's / PM's on how
> it should be done, where on the wiki it should reside, etc.....
>
> Thanks & Regards,
> Mounir
>
>
>
> --
> Mounir Bsaibes
> Project Manager
>
> Follow Linaro.org:
> facebook.com/pages/Linaro/155974581091106
> http://twitter.com/#!/linaroorg
> http://www.linaro.org/linaro-blog
>