I’ve posted a few bugs here, and I’m so happy that they get fixed sooner or later…One took only a couple of builds, others multiple…
But…
Dear devs
Please understand your (L)users frustration, when we don’t get any feedback at all when posting…
I humbly suggest, that when a dev is reading a thread, and ack. a bug, and log it into your bug system, that a reply is posted that bug is ack, and logged.
(Even though if it never will be fixed)
/Tommy
P.S.
Is your Bug-Reporting system open to the public as R/O?
If so, then why not…would help in the amount of posts, IMHO
Hey Tommy, it would seem wrong (or fitting?) for your post to go unanswered, so let me give you some off-the-cuff thoughts, entirely my own, not any sort of official statement.
I think you’re right. I don’t think we’ve figured out how best to handle the posts in here. Sometimes it’s because we knew about a bug already and the person who fixed it didn’t even read about it here. Other times there’s simply a lack of feedback when feedback would have been appropriate. We can definitely do better (and will try to).
As for issue tracking, we’ve played with a few things in the past and never been satisfied. We use GitHub internally, which most of us love, but it’s impossible to give open access to the issues portion of a GitHub repo without giving access to the repo in general. It’s something we talk about periodically, we may (or may not) do something differently.
And on a final note, it would be a tremendous failure on our part if you all didn’t realize how much we appreciate the bug reports and feature suggestions.
Ack, and understood
So cool, as long as it doesn't take too much dev time away ;)
http://www.bugzilla.org/
We know, since we are all PlexPass members here, and we also do this not to nag, but to help :rolleyes:
/Tommy
Early 2021 clean-up: not a feature suggestion; referring to old environment