Date: Tue, 20 Mar 2001 18:02:36 GMT
Message-Id: <200103201802.SAA00883@gannet.ravenbrook.com>
From: Nick Levine <ndl@ravenbrook.com>
To: p4dti-staff@ravenbrook.com
Subject: comments on p4dti u/g
CC: ndl@ravenbrook.com

I was trying to reproduce an earlier problem where submitting a
changelist (16) linked to a job (bug11) had not moved the status of
that job. I failed to reproduce that problem but did encounter some
hassles along the way - see (4) & (5) below.

As to why I couldn't reproduce the earlier problem - I think it'll
turn out to be to do with the aggravation I had with getting my
JobView established. 

An overall comment is that for someone hazy about p4 and very hazy
about bugzilla, some words in the u/g about what was standard p4 and
what was a p4dti extension would be Most Helpful. Eg which are the new
commands, or new flags to existing commands? Is JobView specific to
p4dti or what? 

A second comment is that I spent much time flicking through the u/g
getting past the GUI stuff to locate the command-line info buried in
the gaps between the screen-dumps. Would it be better to group the
command-line stuff in one place and the GUI bits in another?

- n

I tried the following:

1) used bugzilla to create a new job: bug12, assigned to self, status=new

2) used "p4 job bug12" to change the status to "assigned" - this
   worked fine and the new status was visible in bugzilla

3) created a changelist "p4 change" (gave me change 17)

4) "p4 edit -c 17 rosefish" and played with the file

At this point I noticed that although bugzilla showed a link to change
17 from bug 12, the view of bug 12 did not include any mention of the
file I was editing (and this was >15 minutes ago now so it's hardly a
replication problem). 

Btw, if making a change in p4 is going to take time to replicate into
bugzilla, would it be better for p4 to hang until bugzilla is ready?

5) Now I went to section 8.2 of the u/g. The change is not on my
   default changelist, so I went to the second unmbered block of
   instructions which sent me back to section 6.3

6) Attempting to section 6.3 for a pre-exisiting change,  I typed "p4
   change 17". I stuggled withthe wording of instruction 4 - what
   keyword might that mean? Under jobs I changed

	bug12	# this is another job  

   to

	bug12 fixed	# this is another job  

   and invoked server-edit. I got

	Waiting for Emacs...Done
	Error in change specification.
	Error detected at line 29.
	Wrong number of words for field 'Jobs'.
	Hit return to continue...

   and so guessed that instead of fixed, status=fixed would be more
   hopeful. Not so, so in exasperation I removed the fixed bit
   altogether and ploughed on.

   Not going well here. I think the instruction to go back to 6.3
   needs qualifying. An example might help.

7) "p4 submit -c 17"

   At least the view of bug12 now included a link to the file I had
   edited

   And hey, bug 12 is now "resolved fixed"