Hello Marek, Marek Mikus wrote (in <mid:[EMAIL PROTECTED]>):
>> <irony>Great, now we have all these bug 2 twice. That makes all much >> easier and saves much work.</irony> > Bugtraq is main place for bugreports, I don't understand Your irony. 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. >> Sorry, but I really can't understand why you copy all bugs from the >> great list of Peter into Bugtracker. > TBBETA is a place for discussing bugs, Bugtraq is a place for telling > developers about them and where are bugs easily maintained and under > control. > 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" > I have described it saw <mid:[EMAIL PROTECTED]> too late, I'm sorry. > and if You really need an answer, Of course, why do you think I replied? > 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). 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. But the situation now is: Bug reported on TBBeta Bug will confirmed and deconfirmed on TBBeta. Bug was fixed by Ritlabs - but nobody knows: Bug will confirmed and deconfirmed on TBBeta. Explainations of Bug in TBBeta and several message reporting the bug again Add Bug into Bugtracker with mails on TBBeta to confirm. Several mails from bugtracker who reports that somebody confirmed the bug. and so on until Ritlabs releases new version (and of course, the BugReport in the BT will stay open or verify wait for several months/years making the chaos in BT a bit bigger). I had hoped, situation will change with the great BugList of Peter - but I might be wrong. Many testers in list didn't read this single mail but just report there problem (again) on TBBeta. From these users who read the list, only few answered - so the list doesn't seem to be accepted yet. And in this difficult situation, all bugs are duplicated into BT, making the chaos of BT greater without any advantage. Peter, what do you think? Will you continue the list, or just give up, seeing the situation is lost? (PM?) >> (BTW: That's the reason why I didn't published my BugList for NFS!) > who told You to not add them into Bugtraq? My brain. Can't see any sence of this. > And which NFS related bugs were included in list of Peter? Not one, because I didn't (and won't) publish my BugList for NFS. > Some of bugs were already reported Yes, I think it was exactly ONE. > and some of them were missing and I have added them. about 30 I think. (21 today, and 9 earlier). -- 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/
