Closed
Bug 1040544
Opened 11 years ago
Closed 11 years ago
[Adding Component] Request of adding components
Categories
(bugzilla.mozilla.org :: Administration, task, P1)
Tracking
()
RESOLVED
FIXED
People
(Reporter: wachen, Assigned: dylan)
References
Details
Currently, we are using FirefoxOS::General or FirefoxOS::Performance for current MTBF(Mean Time Between Failure tests). However, we do need some categories to fit the best of current MTBF tests.
We need more categories for other new stability requests and MTBF automation framework/bugs
1) For MTBF crashes/hangs/bugs, We will ask to create a bugzilla component called “Firefox OS :: Stability”
2) For MTBF framework issues, We will ask to create a bugzilla component called “Testing :: MTBF"
If there are other procedures and information needed to be provided, please feel no hesitate to contact/ni? me.
Assignee | ||
Comment 1•11 years ago
|
||
The information needed for new components is described on this wiki: https://wiki.mozilla.org/BMO/Requesting_Changes#Components
Assignee: nobody → dylan
Status: NEW → ASSIGNED
Flags: needinfo?(wachen)
OS: Gonk (Firefox OS) → All
Hardware: ARM → All
Assignee | ||
Updated•11 years ago
|
Priority: -- → P1
Reporter | ||
Updated•11 years ago
|
Blocks: MTBF-2014Q3
Reporter | ||
Comment 2•11 years ago
|
||
1.
Firefox OS :: Stability
Along with rapid growing of Firefox OS, stability issues has become more and more important than ever before. This is for all stability tests on Firefox OS (B2G).
nobody@mozilla.org
nobody@mozilla.org
if a b2g-stability flag on bug can be added for now, it will be excellent.
nobody@mozilla.org
2.
Testing :: MTBF
Mean Time Between Failures (MTBF) is really important for hardware/software stability testing. This is set up for any bug, request, and so forth
nobody@mozilla.org
nobody@mozilla.org
no flag should
nobody@mozilla.org
Assignee | ||
Comment 3•11 years ago
|
||
b2g-stability would be a new flag? If so, I need the information here: https://wiki.mozilla.org/BMO/Requesting_Changes#Flags.
Reporter | ||
Comment 4•11 years ago
|
||
I would like to have a new flag for future usage. I mean... currently, there might be only few people caring about it. However, it will be a gate keeper for B2G later. I think I want it now just in case we need it soon.
The name of the flag: b2g-stability
A longer description:
If anything failed in stability testing, like endurance testing or MTBF, it should be blocked.
Which products/components the flag should appear in
Firefox OS / B2G
Whether the flag applies to bugs or attachments
bugs
Whether the flag is requestable (i.e. users can ask for flags of this type to be set)
yes
Whether the flag should be requested from a specific person
no
Whether the flag can be set multiple times
no
If flags of this type are requestable, the group allowed to request them, if any
anyone
The group allowed to grant/deny flags of this type, if any
Taiwan QAs
CC list for request notifications, if any (all valid Bugzilla accounts)
pyang@mozilla.com, wachen@mozilla.com
Flags: needinfo?(wachen)
Assignee | ||
Comment 5•11 years ago
|
||
The components are created & available, but it's come to my attention that you may be better served by the creation of a keyword.
Generally flags only make sense when you need to review and accept/deny something (eg. reviews). looking at the description of your flag, i'm not sure that b2g-stability? and b2g-stability- would ever make sense.
An alternative to flags and keywords is to use the whiteboard, see https://wiki.mozilla.org/BMO/Whiteboard for some examples
Flags: needinfo?(wachen)
Reporter | ||
Comment 6•11 years ago
|
||
I believe it would come to a point that this would be a blocker for b2g releasing later. Actually, it is a blocker for some builds for now. I will ccing more people for further explanation, thoughts, and ideas.
Flags: needinfo?(wachen)
Assignee | ||
Comment 7•11 years ago
|
||
My previous comment was a little unclear, let me rephrase:
We can add a b2g-stability bug flag. Bug flags are used when you need to review and accept/deny a bug for some purpose, for example inclusion in a particular release.
The flag would have three possible values: review ("?"), allow ("+"), and deny ("-").
Instead, we could add a b2g-stability keyword, which is like a tag on the bug. Keywords can be either present or absent.
A third option would be to use the whiteboard, where you could use a string like [b2g-stability]. Using the whiteboard doesn't require any admin assistance.
Which of these options do you think matches the requirements the best?
Flags: needinfo?(wachen)
Comment 8•11 years ago
|
||
(In reply to Walter Chen[:ypwalter][:wachen] from comment #6)
> I believe it would come to a point that this would be a blocker for b2g
> releasing later. Actually, it is a blocker for some builds for now. I will
> ccing more people for further explanation, thoughts, and ideas.
FWIW - I'd suggest using a keyword here. That way you can flag down bugs specifically that you saw during your b2g-stability testing.
Reporter | ||
Comment 9•11 years ago
|
||
ok then. let's not set up a flag for now. Thanks.
Flags: needinfo?(wachen)
Assignee | ||
Comment 10•11 years ago
|
||
Closing this bug then. If you want a flag or keyword added later, file a new bug and I'll be happy to take care of that.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 11•11 years ago
|
||
Thanks so much for the helping
You need to log in
before you can comment on or make changes to this bug.
Description
•