815530 - Meta bug for Firefox OS v1.1 release

Status: RESOLVED FIXED

(Firefox OS Graveyard :: General, defect)

Description

[Kai-Chih Hu [:khu]]

The meta bug for Firefox OS v1.1.

Comment 1

[Jason Smith [:jsmith]]

Do we really want to do a meta bug for tracking a full release? Seems messy in my opinion.

Might be better to introduce a project/tracking flag for it and track that way (similar to how blocking-basecamp is used).

Comment 2

[Kai-Chih Hu [:khu]]

Thank you for your suggestion. I am fine either way. :)

In your opinion, which one is better? tracking flag, project flag, whiteboard, or keywords? 

If we're going to use project flag, or tracking flag, how could I get new flag for v1.1? Thanks!

Comment 3

[Jason Smith [:jsmith]]

I'd add a project flag titled: blocking-ffosv1.1

Same permissions for that flag as the blocking basecamp flag. That way, triage-wise, you can basically follow the same process blocking basecamp already uses.

You can get a project flag created by filing a bug in bugzilla.mozilla.org --> administration and asking for that project flag.

Comment 4

[Jason Smith [:jsmith]]

Putting needsinfo also on akeybl in case he's got an opinion on this as well.

Comment 5

[Kai-Chih Hu [:khu]]

Thank you, Jason!

By the way, sorry to raise a basic question here: I did not see blocking-ffosv1.1 in the project flag list, from any bug. I only see blocking-basecamp and blocking-kilimanjaro flags. I also can't see blocking-ffosv1.1 when doing the search. Could you tell me how to turn on or use this flag? 

Thank you.

Comment 6

[Jason Smith [:jsmith]]

(In reply to khu from comment #5)
> Thank you, Jason!
> 
> By the way, sorry to raise a basic question here: I did not see
> blocking-ffosv1.1 in the project flag list, from any bug. I only see
> blocking-basecamp and blocking-kilimanjaro flags. I also can't see
> blocking-ffosv1.1 when doing the search. Could you tell me how to turn on or
> use this flag? 
> 
> Thank you.

You'll need to file a bug in bugzilla.mozilla.org --> administration to get the flag created under project flags with the same permissions for blocking-basecamp.

Comment 7

[Jason Smith [:jsmith]]

(In reply to Jason Smith [:jsmith] from comment #6)
> (In reply to khu from comment #5)
> > Thank you, Jason!
> > 
> > By the way, sorry to raise a basic question here: I did not see
> > blocking-ffosv1.1 in the project flag list, from any bug. I only see
> > blocking-basecamp and blocking-kilimanjaro flags. I also can't see
> > blocking-ffosv1.1 when doing the search. Could you tell me how to turn on or
> > use this flag? 
> > 
> > Thank you.
> 
> You'll need to file a bug in bugzilla.mozilla.org --> administration to get
> the flag created under project flags with the same permissions for
> blocking-basecamp.

Btw - I'll start a quick thread with Dietrich to get his opinion on this.

Comment 8

[Alex Keybl [:akeybl]]

(In reply to Jason Smith [:jsmith] from comment #4)
> Putting needsinfo also on akeybl in case he's got an opinion on this as well.

I think we need a blocking flag for partner requirements, and a tracking flag for our own usability and stability issues. 

* tracking-b2g18: ?, -, 19+, 20+, 21+, etc.
* status-b2g18: affected, unaffected, etc.
* blocking-b2g: TEF+, DT+, codename+, -, etc.

If we're all in agreement, I can file the appropriate bugs. It'd be a mistake to use something like 1.1 in the name, since we shouldn't be committing to specific version numbers.

Comment 9

[Kai-Chih Hu [:khu]]

I am fine with this. :)

But, I don't really understand how to use tracking-b2g18? Not quite sure what it means. 

For blocking-b2g flag, if we use "TEF", "DT" wordings, would it be a concern because of some level of information leakage? ...

Comment 10

[Kai-Chih Hu [:khu]]

I will use "mno11" in whiteboard for now. If we have better solution to identify Bugzilla cases for each version, I will clean the whiteboard and use the new solution.