summaryrefslogtreecommitdiffstats
path: root/docs/html/scm.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/html/scm.html')
-rw-r--r--docs/html/scm.html32
1 files changed, 28 insertions, 4 deletions
diff --git a/docs/html/scm.html b/docs/html/scm.html
index 05189a6ac..87dd195f1 100644
--- a/docs/html/scm.html
+++ b/docs/html/scm.html
@@ -4,7 +4,7 @@
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
@@ -74,14 +74,38 @@ NAME="SCM"
>5.3. Perforce SCM</A
></H1
><P
-> Richard Brooksby and his team have an integration tool
- in public beta. You can find it at
+> Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
+ You can find the main project page at
<A
-HREF="http://www.ravenbrook.com/project/p4dt"
+HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
> http://www.ravenbrook.com/project/p4dti</A
+>. "p4dti" is now an officially
+ supported product from Perforce, and you can find the "Perforce Public Depot"
+ p4dti page at <A
+HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
+TARGET="_top"
+> http://public.perforce.com/public/perforce/p4dti/index.html</A
>.
</P
+><P
+> 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.
+ </P
+><P
+> 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.
+ </P
></DIV
><DIV
CLASS="NAVFOOTER"