Philip TAYLOR wrote:
OK, I have no idea of what "M.D.A.Seamonkey" is a contraction,
I referred to the mozilla.dev.apps.seamonkey newsgroup which is used for
SeaMonkey development coordination. As Chris already wrote, there's also
a mailing list access option for that.
Hmm, I don't feel this is serious enough. It doesn't seem anything
stops working through this. Actually I'm trying to /reduce/ the
amount of things we list under Known Issues. Sure, the easiest way
would be to fix this issue, but until that happens, what's the impact
of this issue on users other than being an annoying?
what exactly did you mean by "reduce". Do you mean "fix the issues,
so they can be removed from the list", or "filter the recorded
issues in terms of their impact as perceived by the developers" ?
Rather the latter. Fixing the listed issues is often out of my hands (as
I tend to prioritize things that are both listed there and possible for
me to fix), so I can only try to keep them in view and nag those who are
actually able to fix them (like in the case of the busy cursor issue,
which seems to be caused by a back-end change).
If you look at the current list, I tend to remove the DOM Inspector,
Lightning, GMail and Synaptic touchpad issues sooner than later because
there's not much we (SM devs) can do about it and I don't really feel
they are too important.
Personally I'd also remove things that have been around for so long now
that they are a FAQ case by now and unlikely to be resolved any time
soon (like the MailNews account wizard news-type issue and the locked
profile crash issue), but I guess some users will find it there better
than on the FAQ page (alone).
The actual reason why I want to reduce the list is because I think that
the longer the list, the lower the probability that people will actually
read it completely. And if people skip reading it, they'll flood the
support channels with redundant questions, which is bad for everyone
(the requestors have to wait longer to get an answer, and supporters
have less time to address problems that better deserved their attention
- not to name helpful developers who have less time to actually fix some
issues).
I hope very much that you meant the former, because the latter looks
ominously like papering over the cracks in a manner that one /might/
associate with proprietary software but which seems very much at
odds with the open-source philosophy on which Seamonkey is predicated.
We're not papering over anything. In an open project, that's not going
to work anyway. You know, the Known Issues list is just a (technically
redundant) mirror of high-profile issues, maintained in order to spare
end users the hassle of searching Bugzilla (e.g. for the "relnote"
keyword, which is the basis of what gets listed). Bugzilla, as you know,
is not filtered/censored (ignoring security-related issues).
The actual issue tracker is Bugzilla, and there are *tons* of issues
that can only be found through Bugzilla (or maybe Google). The Known
Issues list is by no means complete (never was, never will be). Either
way, some group of people will always have to make the call which things
deserve to get listed and which not. Current practice is that anyone can
nominate (through setting the "relnote" keyword, accompanied by some
reasoning comment, or only the latter), then I as website module owner
(or some other Council member) decides whether it sticks, and in the end
every bug that has "relnote" set shall be added to Known Issues. Plus
any extra ones I deem worthy (using common sense).
HTH
Jens
--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
