[Development] [QtMultimedia] Still is supported, active?

[Denis Shienkov]

@ Thiago,

>The one you linked to is P2 - Important. It's neither critical nor
showstopper.

It isn't I did the decision about assigning the P2 status. I personally
would establish P0/P1 if it would make sense (but, it is just "empty work"
which won't change anything).
Since many bugs with P1 statuses still are not considered.

> It's not critical, according to whoever triaged it.

If the AVI video playback shows with 0.5-1 FPS then it is not critical for
you? Then it is strange for me... o_O

> Where's your proof?

My proof - it is a BUG tracker and current QtMM status.

@ Kai,

> I think Denis should end this e-mail thread by apologizing, and start a
new one
in a reasonable way.

I do not consider myself as the guilty person and I have nothing to
apologize.

BR,
Denis




2016-07-21 10:41 GMT+03:00 Kai Koehne <Kai.Koehne at qt.io>:

> > -----Original Message-----
> > From: Development [mailto:development-bounces+kai.koehne=qt.io at qt-
> > [...]
> > So while I agree that angriness is not helpful for mail list ...
> messages like this
> > are probably the seed to rethink strategy of working with bugs.
>
> Somewhat a side remark, but the unfortunate consequence of this thinking is
> that the objectively best way to get a lot of Qt developers interested in
> your
> problem is to write e-mails that breach of etiquette (to put it mildly).
>
> If Denis would have written a reasonable e-mail asking about the status of
> Qt
> Multimedia (without insults, attacks, and wishing anyone to hell), we most
> probably won't have this discussion.
>
>
>
> I think Denis should end this e-mail thread by apologizing, and start a
> new one
> in a reasonable way.
>
> Just my 2 cents,
>
> Kai
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160721/6e9f350c/attachment.html>