summaryrefslogtreecommitdiffstats
path: root/docs/html/scm.html
diff options
context:
space:
mode:
authorbarnboy%trilobyte.net <>2001-08-22 12:44:14 +0200
committerbarnboy%trilobyte.net <>2001-08-22 12:44:14 +0200
commitbf8ac7551058df22dd5eb712631d9e383fc587a5 (patch)
tree8cf0b9bb7d0755c75266bd30cf7059d556a23703 /docs/html/scm.html
parentf210bb460c786a31bc7677f0e547a67880997558 (diff)
downloadbugzilla-bf8ac7551058df22dd5eb712631d9e383fc587a5.tar.gz
bugzilla-bf8ac7551058df22dd5eb712631d9e383fc587a5.tar.xz
Big checkin of docs to resolve every
known outstanding doc bug! Yay release. Still many things to fix. Aren't there always?
Diffstat (limited to 'docs/html/scm.html')
-rw-r--r--docs/html/scm.html42
1 files changed, 17 insertions, 25 deletions
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"><LINK
REL="NEXT"
-TITLE="Tinderbox"
+TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"></HEAD
><BODY
CLASS="SECTION"
@@ -74,36 +74,28 @@ NAME="SCM"
>5.3. Perforce SCM</A
></H1
><P
-> You can find the project page for Bugzilla and Teamtrack Perforce integration at:
- <A
+> You can find the project page for Bugzilla and Teamtrack
+ Perforce integration (p4dti) at: <A
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
+> http://www.ravenbrook.com/project/p4dti</A
+> . <SPAN
+CLASS="QUOTE"
+>"p4dti"</SPAN
+> 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
+> 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.
+> 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.
</P
></DIV
><DIV
@@ -159,7 +151,7 @@ HREF="integration.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Tinderbox</TD
+>Tinderbox/Tinderbox2</TD
></TR
></TABLE
></DIV