Author: sajolida Date: To: The Tails public development discussion list Subject: Re: [Tails-dev] New support page /support/known_issues/graphics
intrigeri: > sajolida:
>> intrigeri:
>>> sajolida:
>>>> - Does it make sense to link to Redmine tickets? For example, #11095 for
>>>> Radeon HD was closed because we had nothing else to do but the problem
>>>> still exist.
>>>
>>>> Is it worth making this information visible to users?
>>>
>>> Only if the ticket is still open i.e. we think we can do something
>>> about it: then the user can "Watch" the ticket and learn about new
>>> experimental ISOs they can test etc.
>
>> If we want to only link to open tickets and not closed ones then this
>> information will likely get quickly outdated. I'm afraid that linking to
>> closed tickets (by lack of maintenance) might lead to serious confusion
>> as it could either mean that the problem is solved or that the problem
>> cannot be solved...
>
> I'm not sure: in many cases, we simultaneously decide to drop the ball
> on fixing the hardware support issue ourselves and to document the
> known issue (and workaround if there's a known one), and then we know
> that the ticket will be closed once the known issue is documented ⇒
> the known issue should avoid linking to the ticket.
>
> So the only situation when this info will get outdated is when we
> decide to document a known issue strictly before we drop the ball on
> tracking/fixing the actual problem ourselves, and thus track the doc
> writing and the hardware support issue on different tickets. I think
> we're doing this less and less and with my FT hat on, I plan to keep
> doing it less and less: researching graphics hardware support issues
> is a huge time sucker and most of the time we don't get anything out
> of it other than what the initial hour of research (that leads to
> documenting a workaround or the lack thereof) already gives us.
I think I got it. I checked all the tickets referenced in the page. Only
two were still open (#12482 and #15116) and it's when we need more info
and more tests. So I linked to them in the workaround sections (9ac18b19c9).
