Re: [Bugzilla] Add note to not paste logs and back traces.
On Sat, 11 Mar 2006 08:14:03 -0700, you wrote:
Change Log: Add note to attach and not paste logs and back traces.
Files changed: template/en/default/bug/edit.html.tmpl template/en/default/bug/create/create.html.tmpl
Not pasting back traces will make following the bug list by email rather useless. IMO what people are currently posting in bugzilla do not require such recommendations. Rein.
Rein Klazes wrote:
On Sat, 11 Mar 2006 08:14:03 -0700, you wrote:
Change Log: Add note to attach and not paste logs and back traces.
Files changed: template/en/default/bug/edit.html.tmpl template/en/default/bug/create/create.html.tmpl
Not pasting back traces will make following the bug list by email rather useless.
There is always a link in the email to the attachment.
IMO what people are currently posting in bugzilla do not require such recommendations.
Well if that was the case there would not be so many comments telling people not to paste[1]. I can only see the situation getting worse as more people report bugs. [1] http://bugs.winehq.org/buglist.cgi?query_format=&short_desc_type=allwordssub... http://bugs.winehq.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=don't+paste
Saturday, March 11, 2006, 11:19:57 AM, Rein Klazes wrote:
On Sat, 11 Mar 2006 08:14:03 -0700, you wrote:
Change Log: Add note to attach and not paste logs and back traces.
Files changed: template/en/default/bug/edit.html.tmpl template/en/default/bug/create/create.html.tmpl
Not pasting back traces will make following the bug list by email rather Well it might be true, but to a point. Most of the debug traces are too wide and e-mail wraps them (so does maillist archive). That _does_ make it nearly impossible to see anything.
useless. IMO what people are currently posting in bugzilla do not require such recommendations.
What? You mean having all the pastes in this bug: http://bugs.winehq.org/show_bug.cgi?id=4131 adds to it's readability? This is just one bug that I could think of. Also note that the biggest paste by author has nothing to do with the bug itself. Vitaliy
On 3/11/06, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
What? You mean having all the pastes in this bug: http://bugs.winehq.org/show_bug.cgi?id=4131 adds to it's readability? This is just one bug that I could think of. Also note that the biggest paste by author has nothing to do with the bug itself.
Vitaliy
Yeah, that's bad, but so is this AppDB page: http://appdb.winehq.org/appview.php?versionId=1177 People seem to think that the AppDB comment sections are a good place to post logs. It made the page really long. So I put this as the first thing in the howto: "Reporting Problems If you encounter a problem, send your report to Wine-Users Mailing List or WineHQ Bugzilla. These places are much faster for getting help, and bugzilla is better for posting logs." And it mostly seemed to work. And there are alot more new bug links now. But then they added the "testing" section and people use that too to report their problems and for pasting logs. I wish they would be brief in those and link to bug #'s instead. And true it is the same that the logs aren't good in the bugzilla comments either. They should upload them seperate. I guess there are a lot of new people that haven't dealt with this system. The new note should help. One of these days I'd really like to clean up the old comments on the AppDB page, but I don't want to scare anyone with mass deletions. It takes a long time to load on dialup.
On 3/12/06, Jesse Allen <the3dfxdude(a)gmail.com> wrote:
On 3/11/06, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
What? You mean having all the pastes in this bug: http://bugs.winehq.org/show_bug.cgi?id=4131 adds to it's readability? This is just one bug that I could think of. Also note that the biggest paste by author has nothing to do with the bug itself.
Vitaliy
Yeah, that's bad, but so is this AppDB page: http://appdb.winehq.org/appview.php?versionId=1177
People seem to think that the AppDB comment sections are a good place to post logs. It made the page really long. So I put this as the first thing in the howto:
"Reporting Problems
If you encounter a problem, send your report to Wine-Users Mailing List or WineHQ Bugzilla. These places are much faster for getting help, and bugzilla is better for posting logs."
And it mostly seemed to work. And there are alot more new bug links now. But then they added the "testing" section and people use that too to report their problems and for pasting logs. I wish they would be brief in those and link to bug #'s instead.
And true it is the same that the logs aren't good in the bugzilla comments either. They should upload them seperate. I guess there are a lot of new people that haven't dealt with this system. The new note should help.
One of these days I'd really like to clean up the old comments on the AppDB page, but I don't want to scare anyone with mass deletions. It takes a long time to load on dialup.
I'm curious what the policy about cleaning up comments on the appdb is. If a user posts about a comment about some problem with the application, and the problem later is fixed, should the comment be removed? What about bug links? Should they be removed once the bug is fixed or closed? The maintainer's guidelines page says: "If a comment is useless or is not true anymore, you can safely delete it." Though, if you look at AppDB entries like the one above, this doesn't seem to happen. Perhaps the maintainer's guidelines could be a bit more specific? Also, the guidelines don't even mention bug links. -James
James Trotter wrote:
On 3/12/06, *Jesse Allen* <the3dfxdude(a)gmail.com <mailto:the3dfxdude(a)gmail.com>> wrote:
Yeah, that's bad, but so is this AppDB page: http://appdb.winehq.org/appview.php?versionId=1177
People seem to think that the AppDB comment sections are a good place to post logs. It made the page really long. So I put this as the first thing in the howto:
"Reporting Problems
If you encounter a problem, send your report to Wine-Users Mailing List or WineHQ Bugzilla. These places are much faster for getting help, and bugzilla is better for posting logs."
And it mostly seemed to work. And there are alot more new bug links now. But then they added the "testing" section and people use that too to report their problems and for pasting logs. I wish they would be brief in those and link to bug #'s instead.
And true it is the same that the logs aren't good in the bugzilla comments either. They should upload them seperate. I guess there are a lot of new people that haven't dealt with this system. The new note should help.
One of these days I'd really like to clean up the old comments on the AppDB page, but I don't want to scare anyone with mass deletions. It takes a long time to load on dialup.
I'm curious what the policy about cleaning up comments on the appdb is. If a user posts about a comment about some problem with the application, and the problem later is fixed, should the comment be removed?
Yes these can be deleted
What about bug links? Should they be removed once the bug is fixed or closed?
No at least for now. There probably should be an option to hide resolved and closed bugs though.
The maintainer's guidelines page says: "If a comment is useless or is not true anymore, you can safely delete it." Though, if you look at AppDB entries like the one above, this doesn't seem to happen. Perhaps the maintainer's guidelines could be a bit more specific?
That seems pretty straight for ward to me. Could you clarify what you mean.
Also, the guidelines don't even mention bug links.
Well the guideline is not to delete bug links unless they never did apply to the application version. (If the bug link was submitted in error then delete it) -- Tony Lambregts
On Sat, 11 Mar 2006 12:30:39 -0700, you wrote:
Not pasting back traces will make following the bug list by email rather
Well it might be true, but to a point. Most of the debug traces are too wide and e-mail wraps them (so does maillist archive). That _does_ make it nearly impossible to see anything.
I said "backtraces". You talk about debug traces, the backtraces are good to follow. I agree that logs are mostly too large to post, but then most people already attach those.
useless. IMO what people are currently posting in bugzilla do not require such recommendations.
What? You mean having all the pastes in this bug: http://bugs.winehq.org/show_bug.cgi?id=4131 adds to it's readability?
Honestly I do not see your problem here. To me it is readable both on the web and by email. Perhaps the web form could be reversed so that new reactions are on top, if the scrolling is your problem. Rein.
participants (5)
-
James Trotter -
Jesse Allen -
Rein Klazes -
Tony Lambregts -
Vitaliy Margolen