This depends on whether the bug is marked resolved or not.
I had sent email out on this to mgrs. I should have sent to all.
In helping answer some developers who wanted to find an easy way to let
QA know that a fix is on the trunk and they wanted extra testing on it
before the fix went into the 092 branch. We came up with just using
the keyword that was already there "vtrunk" (verify on trunk) and we ran
this by Asa who agreed that it would be fine for this short period of
time. This way, QA would be able to do a query.
It does have opposite meanings (as you described) depending on whether
the bug is marked Resolved or not. I routinely go through the bugs to
make sure that the resolved PDT+ bugs with vtrunk or vbranch are
properly marked.
Sorry for the confusion. Next time, I'll work on a better plan when we
have the need to track both branch and trunk changes.
Lisa
Dan Veditz wrote:
>Just today I've seen two opposite meanings of "vtrunk" being used in
>bugzilla. How is it really supposed to be used? Some folks are using
>"vtrunk" to mean it's been checked into the branch and needs future checking
>on the trunk (as described on the keyword page), and others are using it to
>mean it's been checked in on the trunk but not the branch.
>
>So which is it? Engineering saying "ready to be verified on the trunk only
>right now", or QA saying "not done on the trunk, check later"? (ditto for
>vbranch, reversing the sense).
>
>-Dan Veditz
>
--
Lisa Chiang
Netscape, Client QA
[EMAIL PROTECTED]
650.937.4420
sn: LisaChiang
