122431 - topembed expansion to include '-' and '+'

Status: RESOLVED FIXED

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

Description

[Judson Valeski]

I'd like to push topembed into the approval/denial/nomination realm, beyond it's
current "tagging" value only.

Basically we want it to look like the "nsbeta1" keyword. If you replace
"netscape" with 'embedding" in the keyword list/description doc, for the nsbeta1
descriptions, and add topembed- and topembed+, we'll be good to go.

so, in brief.

new keyword - topembed+
new keyword - topembed-
descriptions reflect those for nsbeta* with "Netscape" replaced w/ "embedding"

Comment 1

[timeless]

does embedding really 'release' or do you just mean inclusion in the current 
embedding branch? [or do you mean something else?]

Comment 2

[Asa Dotzler [:asa]]

Shows how closely I've been paying attention. I thought topembed was the "plus"
 for bugs flagged with the "embed" keyword. I'm pretty  sure I  added it with
that in mind. Well, I've  added  the  plus and minus. Should  we  remove  "embed"?

Comment 3

[Asa Dotzler [:asa]]

fixed

Comment 4

[Judson Valeski]

still thinking about removing embed. asa, your previous understanding was
correct. this is an attempt to rally around the +/- standard that seems to be
locking into everyone's minds.

timeless, valid questions. I guess it "releases" when a set of embedding
customers rally around a particular branch, then want to call tha branch "done."
I would also say that it can release when we hit a true release type milestone
w/ embedding APIs, performance metrics, footprint metrics, etc. An embedding
"package" can be considered a 'release" in that sense.

Comment 5

[timeless]

if we remove embed, could we rename topembed* to embed*?  i don't see the reason to force everyone to type 3 extra characters :)

Comment 6

[lchiang]

We had considered just "embed", but "topembed" was so ingrained in everyone's
mind that we decided to use "topembed"