157190 - request for new keywords for OEM release

Status: VERIFIED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Jim Dunn]

I would like the following 4 keywords to be added to the current
list of keywords so that we can "manage" the upcoming (and future)
oem releases.  I tried to make them "standard" with existing keywords
(but if you need to tweek the names, that is fine).

oem - request a bug to be added to the OEM Branch
oem+ - request granted, bug is approved for OEM Branch
fixed_oem - fix for bug has been checked into OEM Branch
verified_oem - fix for bug has been verified in an OEM Branch build.

Comment 1

[Jim Dunn]

*** Bug 158231 has been marked as a duplicate of this bug. ***

Comment 2

[Jim Dunn]

asa any update?
we are ready to begin checking into the oem branch and
these keywords will definitely help!

Comment 3

[timeless]

can't we recycle the fixedSunBranch keywords?

I really don't like the idea of a generic OEM to be used by a single OEM, Sun
and IBM are both OEMs but i doubt IBM will be using this one.

ignoring that, please follow the naming convention which is

    fixedSunBranch
    verifiedSunBranch
(note the lack of underscores)

Comment 4

[Jim Dunn]

but ALL (my) OEM's are using this
IBM, HP, Compaq & Sun...
I guess I can reuse the Sun ones, but the fact that
IBM/HP/Compaq are also using it, makes me queasy.

Comment 5

[timeless]

oh, well that's a different story

how does this sound:
branchOEM-	OEM deities do not feel that this bug must be fixed on the OEM
		branch
branchOEM	Add this keyword to propose that a bug must be fixed on the OEM
		branch. This branch will be used by Compaq, HP, IBM, & Sun....
branchOEM+	OEM deities agree that this bug must be fixed on the OEM branch
fixedOEM	Use this keyword when you check in a fix to the oem branch (to
		be named later). QA will verify bugs with this keyword by
		replacing it with 'verifiedOEM' keyword.
verifiedOEM	Use this keyword to indicate that a fix has been verified on the
		oem branch (to be named later). 

I don't suppose you have a name for your branch?

Comment 6

[Jim Dunn]

those work for me...

I "think" the branch name is NETSCAPE_7_0_OEM_BRANCH, is sort of
"messed" up while creating it, am working on fixing it now but won't
know for a bit (leaf is helping)

I also have http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey-OEM
to track this.

Comment 7

[Asa Dotzler [:asa]]

For low volume uses like this I still think that using metabugs (like
[e-mail] uses for tracking its milestone requirements) is better than
keywords. Bug I've pretty much completely given up on the idea of keywords as
being useful to wider audiences and so I'm letting it decay into the same mostly
usless mess that are status whiteboard flags.

Fixed.

Comment 8

[timeless]

vrfy fixed
all status whiteboard items were migrated.