I'm certainly willing to test any Sip and PyQt versions released for OS X (and I think I've tried to compile every version I've seen since joining this list). Unfortunately, the only feedback I can give right know is whether it works or not and provide a listing of make/make install errors.
Is this helpful at all? If not, or if there is something else that would help, please let me know. Along those lines, Phil, what are your expectations from us? Perhaps we could be better testers if we knew what exactly would help you in the development process. Even something as simple as a certain format for change request/bug submission reports might help. I appreciate the effort that you and the team put in! Thanks! -Barron -----Original Message----- From: Phil Thompson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 08, 2002 6:53 PM To: PyKDE Mailing List Subject: [PyKDE] I Wish To Register A Complaint I'm not happy with the problems that have been found with v3.2. Admittedly there were some large changes under the covers (for threading for example) which wouldn't have attracted attention unless they broke, but I view v3.2.n (where n > 0) as a failure of the testing process. So, why don't users want to test pre-releases and release candidates? I'd like some feedback on this problem - what would motivate you as a user to test a beta version with your application? I don't want to adopt the Microsoft approach and release beta versions pretending they are working perfectly. Over the next few weeks I intend to switch off CVS access and provide daily snapshot source packages instead. Maybe if my initial reaction to bug reports was then "have you tried the latest snapshot"? Phil _______________________________________________ PyKDE mailing list [EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde _______________________________________________ PyKDE mailing list [EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
