Hello Marek, Marek Mikus wrote (in <mid:[EMAIL PROTECTED]>):
>> Bugtraq is one big big chaos, with hundreds unreproduceable, already >> fixed, never seen again bugreports. I just can't believe somebody has >> any orientation in it. > and You have orientation in TBBETA when approximately 150 messages are > received daily? no. > Do You really expect, developers will check that Peter's mail Yes, I did! Peter spends much time on it, but (I guess) not, if nobody cares! > and will watch all mids with all replies to know, how it is > reproducable and how many people confirmed it with which OS etc? Seems that you didn't read the list at all! The discribtion how to reproduced is below the mid. And BTW: It is always a very good and short descibtion. /If/ you don't understand discribtion you /can/ read the original, but if you did understand the discribtion why should you read the original message and its replies? >>> And all developers with official support is working with it. >> Oh, I really hope this is not true. All developers work with it - and it >> has 329 new reports? Correct me when I'm wrong, but new means "never >> seen/tested by developer" > as I told, TBBETA is for discussing and I expect, if will be bug > revealed and confirmed by many users, it will be added into BT with > complete description how to reproduce it. <irony>Of course.</irony> But sometimes it really goes this way, and there the bugreport stays unwached until the end of BugTracker. >>> Max wanted it, because Ritlabs can read all hundred messages sent >>> daily to TBBETA, but will not have time to solve them then. >> Well, my answer might go more to Ritlabs/Max then to you: >> Many bug reports on TBBeta are already in Peters list. So if Ritlabs >> would read this mail, lot of bugs could be fixed and much messages could be >> saved and that with reading only ONE mail (not 30 bug reports in BT + >> changing the status). > Peter's list have not many of them what do you talk about here? > and had links to BT too. no, it had only /one/ link to BT (BTW: this was /the/ (only) report that was from bugtracker and now I'm sad I told him to add the bug to the list). >> Furthermore if Ritlabs would answer to bugreports on TBBeta, much >> messages and time could be safed - as there would be no need for others >> to try to confirm a already fixed bug. > so You expect, they will read all messages? I expected that they will read /one/ message each release. >> And in this difficult situation, all bugs are duplicated into BT, making >> the chaos of BT greater without any advantage. > You can help to have BT better, Sorry, but this is the task of Ritlabs. I don't get money to check about the 1000 open BugReports. And furthermore I don't see any effort from Ritlabs to keep the bugtracker uptodate or even care about it. > confirm new I won't confirm any bug report that was copied from BugList to bugtracker. If you like to do senseless work, do it - I won't. > or ask users about more details. and get no response at all. > but list in mail includes bugs for whole program and is harded to find > duplicates. In bugtracker there is often wrong category or even not a bugreport but a wish report. And this (and other things) leads to the fact, that nobody (including Ritlabs) does care about BT (the 300 new reports proves this fact). -- Regards, Boris Anders, http://www.batboard.de ________________________________________________________ Current beta is 3.0.9.17 Return | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
