[meego-releases] Response times and ratios to blocker bug requests

[Andre Klapper]

On Tue, 2011-08-30 at 09:00 -0600, Clark, Joel wrote:
> > On Tuesday, August 30, 2011 7:50 AM Andre Klapper wrote:
> > Thanks for the discussion everybody, but with regard to bugs like bug
> > 18619 there's still no change visible.
> > Nobody is reviewing it and it's stuck, so I ask Release Engineering to
> > discuss here to please find a way to get such request actually reviewed.
> > We need progress.

> The Release Engineering team does not fix bugs.

I know. As you can see in the bug report the patch has been already
submitted ages ago to the 1.3 branch so nobody asked RE to do so.

> They work to ensure the integration 
> and build process is reliable.  If someone really does care about this bug
> They should submit a patch.  Then the Release Engineering team and do its thing.

So if obviously something more is needed, what has been blocking you
from adding these short two lines to the bug report directly and
earlier, so that reporters / developers can actually fulfil the needs
instead of waiting and then turning away from MeeGo?

Just do it please.

The "MeeGo_Update_Release_Blocker" flag has been requested three months
ago, probably with an intention.

Nothing has happened for the last three months as RE has been doing
nothing.

For the records:
Luis had provided a package
http://download.meego.com/live/home:/araujo:/branches:/devel:/qt-mtf:/MeeGo:/1.2/MeeGo_1.2_testing/i586/meegotouch-inputmethodbridges-0.2.2-5.1.i586.rpm
and the source RPM contains the patch
http://download.meego.com/live/home:/araujo:/branches:/devel:/qt-mtf:/MeeGo:/1.2/MeeGo_1.2_testing/src/meegotouch-inputmethodbridges-0.2.2-5.1.src.rpm

And now there is also an extracted patch attached to the report.

Looking forward to seeing some progress, or is anything else still
blocking getting this in?

andre
-- 
Andre Klapper (maemo.org bugmaster | MeeGo QA)
http://blogs.gnome.org/aklapper/ | http://www.openismus.com