Good [morning|afternoon|day|evening|night] Oleg, OT> I am afraid that I dislike the things are going on, in particular OT> that I (may be someone agrees with me too - just write here) am OT> getting new features in a product that have a lot of bugs on OT> bugzilla list.
Issues enlisted on the Bugtraq are not all bugs. Many of them are design/handling of non-standard situations issues or feature requests. Many are fixed already, it just needs some time to go through the list and make changes - this requires some moral power :-) As about adding new features - a program cannot be developed only by bugfixing. For many people most of bugs do not exist either because they do not come into situation to meet a problem or because they do not think it is a bug. Those people (and they are actually majority of users) would be extremely aggravated if they do not see any new features added in a new version saying "Well, I do not care for these bugs, they are not bugs to me, but where are improvements?!" Besides, even bugfixes may lead to implementing new features and generating new issues. So, this is the same old story of struggling with Beta testers :-) OT> I would like to see old bugs fixed first. A lot of them are OT> unfixed OT> (nickname autocomplete, missing feature. OT> first name handle in templates, AI is needed here to handle everything properly :-) Basically, the choice of names is provided, now we should get things sorted out. OK, this is a bug, but the way it's going to be fixed is implementing of a new feature :-)) OT> better SSL support, We are heading to it. But - who can say it is not working? Yes, there are some usability problems, but where are bugs? OT> stable work of KAV anti-virus plug-in, ... It depends on the KAV plug-in itself. Because it is produced by Kaspersky, we cannot do anything here. On all machines I use and used it was always working correctly. I have no idea why, but it even did not require any messages sent to Kaspersky Labs. :-) OT> just few to mention). You mentioned just one to be fixed. :-) And not many people can mention more, as a matter of fact. OT> Do you, guys at RITLabs, feel you can: OT> a) develop new version OT> b) introduce new features in old version OT> c) fix bugs in old version OT> *all* at the same time? We ARE doing this :-) OT> May be you could consider to drop v.1.XX and deliver new v.2.XX in OT> reasonable time, get some money and fix the old version. "Get some money" is a very interesting thing. You cannot just "get some money" out of nowhere you should get it from a) something you can sell (which is version 1.xx for now) b) borrow from somebody (which means additional dependency) c) stealing, but is not a choice anyway :-) Do we have more choices? OT> Or ask for donation (I am ready to pay something reasonable to get OT> all bugs fixed in v.1XX as I am very happy with it). Well, thank you, but we are trying to do some business instead of being a charity organisation. OT> Also you may release source code of TB! v.1.XX to public domain so OT> others could take care of old version. This is not a choice, sorry. -- Read you later Stefan mailto:[EMAIL PROTECTED] ...Next time you wave, use all your fingers. ________________________________________________________ Current beta is 1.63b4 | "Using TBBETA" information: http://www.silverstones.com/thebat/TBUDLInfo.html
