[www-issues] [Issue 65006] The issue management for v otes is faulty
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=65006 --- Additional comments from [EMAIL PROTECTED] Sat Jun 14 06:16:05 + 2008 --- Well, let us assume a scenario: Someone stops me at office and tells me, Your tie is askew and your fly is open. Is it logical for me to say- Unfortunately you clubbed two unrelated issues!! The only way I will close my fly is you will have to tell me again. I know what's wrong, but policy is policy! You see, there is a risk that the guy will not bother again. He would not be so passionate and caring about my closing the fly. Worse, he will simply go around and tell others what a lout I am. So a policy-maker in OOo community has to wake up to this problem and explain to the front-ending QA guys NOT to bounce valid inputs in the name of policy. Just thank the public for bothering at all, and take care of the ISSUE at hand! - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[www-issues] [Issue 65006] The issue management vor v otes is faulty
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=65006 User raindrops changed the following: What|Old value |New value Status|RESOLVED |VERIFIED Status|VERIFIED |CLOSED Status|CLOSED|UNCONFIRMED Resolution|DUPLICATE | --- Additional comments from [EMAIL PROTECTED] Sat May 17 20:15:30 + 2008 --- The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html --- Additional comments from [EMAIL PROTECTED] Sat May 17 22:18:17 + 2008 --- As per previous posting: Verified - Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew --- Additional comments from [EMAIL PROTECTED] Sun May 18 07:43:51 + 2008 --- Andrew, I doubt whether you ever read through this issue. Probably this is a software-generated post attached to ALL old issues. The sweeping-under-carpet has reached a new low. I am absolutely disgusted with how Bugzilla is misused in dealing with the problems. It has sunk so low that now it is nothing more than forum posting. The issuezilla is meant to detect problems and track them to closure. While the users do the first part, the Sun/OOo staff should do the rest. So why ask the originator to raise another issue? Just clone the topic into a new issue and start off discussion on it! The Issuezilla management policy (DOES IT EXIST??) needs to be changed. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[www-issues] [Issue 65006] The issue management for v otes is faulty
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=65006 User ace_dent changed the following: What|Old value |New value CC|'rainerbielefeld' |'ace_dent,rainerbielefeld' Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE Summary|The issue management vor v|The issue management for v |otes is faulty|otes is faulty --- Additional comments from [EMAIL PROTECTED] Sun May 18 21:16:34 + 2008 --- Dear 'raindrops', Thank you for taking the time to reply. I will try to answer some of your important concerns as briefly as possible. I also want to assure you that it was not my intention to cause you any distress! (1) Andrew, I doubt whether you ever read through this issue. Probably this is a software-generated post attached to ALL old issues. - Correct (partly). The first stage - stirring up User feedback- was automated based on reasonable criteria. In this case, you had over 1 year to argue against the 'resolved' status and change it to 're-opened'. The second stage (as you can see) will require QA time to go through every response and individual issue. The reason step 1 was automated, is that there are thousands (~5k issues) which are old and gathering dust. It is much more efficient if the original reporter takes responsibility for their Issue and closes it if possible, to minimize this effort. It is about distributing rather than centralizing the task load. (2) The sweeping-under-carpet has reached a new low. - This is the exact opposite. The point of my actions is to bin old and irrevelant Issues and highlight long outstanding ones. Remember, even when an Issue has been closed it will always be available, so your comment just doesn't stand. (3) While the users do the first part, the Sun/OOo staff should do the rest. So why ask the originator to raise another issue? Just clone the topic into a new issue and start off discussion on it! - And here is the key point(s)... Sun (company) does not equate to OOo (community). OOo doesn't have staff (as such), just keen volunteers such as myself - and yourself! You have just as much responsibility as a custodian for the bug report you raised, as any other member of the OOo community. If you bothered to raise an Issue, it is reasonable to assume you may be the only person in the world who cares about it. I also want you to note that I have acted as an individual, just keen to try and improve the current IssueTracker situation. (4) The Issuezilla management policy (DOES IT EXIST??) needs to be changed. - There are fairly clear guidelines and policies. This brings us back to your original Issue. Reviewing rainerbielefeld's QA (spot-on as usual), this Issue is clearly a duplicate and breaks the principle policy of IssueTracker: One Problem One Issue. This is will be Closed. Please fell free to email me if you have any further questions, to avoid treating IssueTracker like a forum... Regards Andrew *** This issue has been marked as a duplicate of 22519 *** - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[www-issues] [Issue 65006] The issue management for v otes is faulty
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=65006 User ace_dent changed the following: What|Old value |New value Status|RESOLVED |CLOSED --- Additional comments from [EMAIL PROTECTED] Sun May 18 21:17:30 + 2008 --- Closed. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[www-issues] [Issue 65006] The issue management vor v otes is faulty
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=65006 User rainerbielefeld changed the following: What|Old value |New value Status|UNCONFIRMED |RESOLVED Issue type|DEFECT|ENHANCEMENT Resolution| |DUPLICATE Summary|The issue management is fa|The issue management vor v |ulty (votes, disposition, |otes is faulty |etc) | --- Additional comments from [EMAIL PROTECTED] Wed Dec 20 21:56:37 -0800 2006 --- We can not handle different problems within one issue. The first enhancement request is a DUP of an other issue, so I will close this issue again after I limited the subject to the votes problem. For the resting listed problems please see my following comments. @raindrops New issue for every problem! Please divide your requests (as you offered in your report) into separate issues, so that decisions concerning each of your requests can be found separately. I do not see good prospects that your points 2 and 3 might be considered in near future. 1. Faulty tallying of votes --- duplicate of issue 22519. 2. Loss of age-weightage I don't believe that seniority has much importance for the developers when they decide what issue should be fixed for next. If you believe that consideration of this could improve the bug fixing process, please state that plausible in a new issue. 3. Enhancement vs defect: - I do not see that difference to common use of those terms. If you believe that a new definition could improve the bug fixing process, please state that plausible in a new issue. *** This issue has been marked as a duplicate of 22519 *** - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
