Received: from [172.16.1.164] (root@raven.ravenbrook.com [193.82.131.18]) by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id XAA25620 for ; Thu, 1 Feb 2001 23:33:23 GMT Mime-Version: 1.0 X-Sender: gdr@pop3 Message-Id: Date: Thu, 1 Feb 2001 15:32:44 -0800 To: p4dti-staff@ravenbrook.com From: Gareth Rees Subject: Test report for release 0.5.1, 2001-01-31 Content-Type: text/plain; charset="us-ascii" ; format="flowed" These are comments from Lawrence You . 1. All the justification and advice in the Administrator's Guide gets in the way of the administrator who just wants to install it quickly. Lawrence would prefer a separate "read this first" installation guide. 2. A site map for the P4DTI project on would be useful. A visitor's question is usually "how do I get and install it?". I showed him the "Quick Q&A" section and he agreed that was an improvement. 3. We tried to build MySQLdb-0.2.2 on FreeBSD 4.2. It build the _mysqlclient.so library, but when we tried to "import _mysql" from Python the library failed to load, complaining about the missing symbol "PyType_Type". Python 1.5.2 has been built previously by someone else on that machine. It's possible that there was a mismatch between the build instructions: perhaps Python had been built with static libraries but MySQLdb-0.2.2 was expected shared libraries? We had no success in tracking this down. However, we had no problem building MySQLdb-0.2.2 on Linux (Slackware). 4. There's a security hole in the integration. Because users are matched between the defect tracker and Perforce by e-mail address, you can fool the replicator by running "p4 user" and editing your e-mail address. Perforce provides no control over what e-mail address a user specifies for themself.