P4DTI issue job000390

TitleP4DTI doesn't support Bugzilla 2.14
Assigned userNick Barnes
DescriptionBugzilla 2.14 was released on 2001-08-29. The P4DTI doesn't support it.
AnalysisDownload 2.14, add it to the master sources, make the patch modifications, test against it. Consider dropping 2.10 (but that's another job).
The existing 2.12 patch applies cleanly to 2.14.
GDR 2001-09-14: However, there are schema changes and security enhancements which we need to support.
This is Perforce job 6527.
NB 2001-09-18: The most significant schema change is that columns in the bugs_activity table have changed their names. We read and write this table. We need code to determine the Bugzilla version (which can be done simply by inspecting the table names). The user should specify a version, against which we can test (and warn if it doesn't match the database). That will allow us to work with user-modified Bugzillas.
How foundinspection
EvidenceNews on front page at <http://www.mozilla.org/>.
Observed in1.1.1
Test procedure<http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>
Created byNick Barnes
Created on2001-09-03 12:14:37
Last modified byGareth Rees
Last modified on2010-10-07 12:06:26
History2001-09-03 NB Created.
2001-09-14 GDR Noted schema changes, Perforce job.
2001-09-18 NB Noted bugs_activity schema change.
2001-10-11 NB Added support note.

Advice for all releases.


Change Effect Date User Description
22570 closed 2001-09-19 14:05:54 Nick Barnes Correct operation with Bugzilla 2.14 (job000390): detect Bugzilla version from database tables, get the user to specify it, warn if different and behave accordingly.
22219 open 2001-09-03 12:18:22 Nick Barnes Support Bugzilla 2.14.
22218 open 2001-09-03 12:02:03 Nick Barnes Added Bugzilla 2.14.
22217 open 2001-09-03 11:59:16 Nick Barnes _this_ is where the bugzilla 2.14 sources go.
22214 open 2001-09-03 11:38:16 Nick Barnes Imported Bugzilla 2.14