On Thu, Mar 15, 2018 at 4:45 PM, Steffen <[email protected]> wrote: > Thinking. > > Because an issue can be a configuration fault and not a bug. I think > best is post it to the user list first or dev can reply in the AL > forum. Bugzilla is not so suited for discussions.
Yes, technical discussions and (possible) configuration issues are not nice/appropriate for bz. Qualified bugs are, and we can always (usually do) continue related technical discussions on dev@, if needed. There remain the description of the issue, final patches and where they are committed/backported to in bz, which is nice for those who didn't upgrade (for instance). So once qualified it's always worth creating a bz for the record. > Experience learns that AL users not always willing to be directed to > bugzilla or to lists. > > Yep, hard for a non coder to understand what to do to report issues > from my own test frame work, reported to me by mail, reported in the > forum. It's hard to get a fix without reporting appropriately, the less time spent by the committer, the faster the issue gets resolved. > > For years I and others report issues on the dev list, but suddenly it > seems not be the way anymore. > > What is changed lately ? Well, it sometimes works on the one or the other, the preferred way is (and has always been AFAICT) to fill a bz and ping on dev@ if it lacks attention...
