From bf8ac7551058df22dd5eb712631d9e383fc587a5 Mon Sep 17 00:00:00 2001 From: "barnboy%trilobyte.net" <> Date: Wed, 22 Aug 2001 10:44:14 +0000 Subject: Big checkin of docs to resolve every known outstanding doc bug! Yay release. Still many things to fix. Aren't there always? --- docs/html/scm.html | 42 +++++++++++++++++------------------------- 1 file changed, 17 insertions(+), 25 deletions(-) (limited to 'docs/html/scm.html') diff --git a/docs/html/scm.html b/docs/html/scm.html index 3aa515b35..c96598b81 100644 --- a/docs/html/scm.html +++ b/docs/html/scm.html @@ -16,7 +16,7 @@ REL="PREVIOUS" TITLE="CVS" HREF="cvs.html">5.3. Perforce SCM

You can find the project page for Bugzilla and Teamtrack Perforce integration at: - You can find the project page for Bugzilla and Teamtrack + Perforce integration (p4dti) at: http://www.ravenbrook.com/project/p4dti. "p4dti" is now an officially - supported product from Perforce, and you can find the "Perforce Public Depot" - p4dti page at http://www.ravenbrook.com/project/p4dti . "p4dti" is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at http://public.perforce.com/public/perforce/p4dti/index.html http://public.perforce.com/public/perforce/p4dti/index.html.

Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However, - p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate - patches for 2.12 will be out shortly. Check the project page regularly for updates, or - take the given patches and patch it manually. p4dti is designed to support multiple defect - trackers, and maintains its own documentation for it. Please consult the pages linked - above for further information. -

Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or - to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you - have synchronization problems, the easiest way to avoid them is to only put the bug - information, comments, etc. into Bugzilla, and not into the Perforce change records. - They will link anyway; merely reference the bug ID fixed in your change description, - and put a comment into Bugzilla - giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology - question. +> Integration of Perforce with Bugzilla, once patches are applied, + is seamless. Perforce replication information will appear below + the comments of each bug. Be certain you have a matching set of + patches for the Bugzilla version you are installing. p4dti is + designed to support multiple defect trackers, and maintains its + own documentation for it. Please consult the pages linked above + for further information.

TinderboxTinderbox/Tinderbox2