[Qt-interest] Clarification on "out of scope" closed bug

[Stephen Kelly]

Andre Somers wrote:

> Op Wo, 19 januari, 2011 3:18 pm, schreef Thiago Macieira:
>> On Wednesday, 19 de January de 2011 14:10:59 Andre Somers wrote:
>>> Being honest after the fact is not much use. What I mean is: I think you
>>> (not you personally, but Qt in general) should add warnings in the
>>> documentation if classes are considdered end-of life, "mistakes" or for
>>> some other reason won't receive bugfixes anymore or are for other
>>> reasons
>>> better to stay away from in new code. Better yet: that should be
>>> announced
>>> ahead of time, before such support actually stops. Qt decided to
>>> release the code (and I remember showed it off even, I can still see the
>>> cool demo's where a Grahics view item rotated to show it's backside to
>>> reveal a widget-based form to edit something). That, IMHO, also means
>>> supporting it.
>>
>> We're doing that.
>>
>> But you'll understand that such a communication needs to be done with
>> care.
>> People won't like some of the things that are in the list.
> 
> I do understand, but personally, I would *much* rather find it out by
> reading the docs or some other .plans document somewhere, than by comments
> on closed but unresolved bugreports. Even if the news is bad, I'd rather
> have it sooner than later so I might be able to do some damage control.

I agree. I consider that things like "dropping support and maintenance for 
APIs being announced ahead of time, before such support actually stops", is 
part of open governance.

> 
> Perhaps the openness surrounding the roadmap, as discussed on the DevDays
> in your own Open Governance session if memory serves me well, could still
> be improved here and there...
> 
> André