The default bug view has changed. See this FAQ.
Bug 844910 (b2g-v-next)

Tracking: v.next technology

NEW
Unassigned

Status

Firefox OS
General
4 years ago
2 years ago

People

(Reporter: cjones, Unassigned)

Tracking

(Depends on: 49 bugs, {meta})

Firefox Tracking Flags

(Not tracked)

Details

Architectural work and big platform features we deferred to post-v1.  Mostly gecko items, but tracking from b2g product since these are items important to b2g.
Depends on: 811636
Depends on: 803471
Depends on: 785592
Depends on: 627635
Depends on: 717872
Depends on: 716140
Depends on: 763555
Depends on: 761935
Depends on: 787363
Depends on: 580784
Depends on: 771367
Depends on: 689623
Depends on: 789358
Depends on: 471915
Depends on: 631527
Depends on: 716859
Depends on: 801176
Depends on: 648417
Depends on: 644362
Depends on: 644368
Depends on: 644389
Depends on: 663286
Depends on: 674062
Depends on: 674080
Depends on: 711613
Depends on: 674741
Depends on: 677989
Depends on: 767189
Blocks: 738172
Depends on: 839446
Depends on: 763198
Depends on: 784816
Depends on: 821450
Depends on: 845086
Depends on: 783638
Depends on: 715824
Depends on: 725967
Depends on: 775449
Depends on: 775452
Depends on: 775469
Depends on: 785933

Updated

4 years ago
Depends on: 835247
Depends on: 746062
Depends on: 746065
Depends on: 744713
Depends on: 775456
Depends on: 783488
Depends on: 783919
Depends on: 787417
Depends on: 790858
Depends on: 796690
Depends on: 796697
Depends on: 796705
Depends on: 799658
Depends on: 803772
Depends on: 822833
Depends on: 820241
Depends on: 820282
Depends on: 821524
Depends on: 823284
Depends on: 831237
Depends on: 833897

Updated

4 years ago
No longer depends on: 471915

Updated

4 years ago
Keywords: meta
OS: Linux → All
Hardware: x86_64 → All
I'm going to use this for bugs that are sort of "general platform improvements", what we can pick and choose on train-like schedules for products.

We already track product requirements, so I'm going to leave those off here, even where they would fit the theme.
Alias: b2g-v-next
Depends on: 842217
Depends on: 844009
<Jesse> of course, "next" will become incorrect at some point :/

There's always a v.next, which is why I chose that name ;).
Depends on: 747798
Depends on: 842102
Depends on: 816869
Depends on: 750011
Depends on: 779297
Depends on: 845191
Depends on: 790923
Depends on: 777948
Depends on: 837591
Depends on: 845200
Depends on: 845202
Depends on: 845209
There will be more to come, but I'm going to start tagging these bugs (with explanations where possible) as

 [tech-bug]: user-visible defect that we need to fix asap.  Highest priority.
 [tech-p1]: needed for competitive parity, or major use case for content
 [tech-p2]: important use case for content, or major technical issue to fix
 [tech-p3]: nice-to-have use case, or important technical issue
No longer depends on: 783919
No longer depends on: 746065
Depends on: 746073

Comment 4

4 years ago
Facebook developer ringmark [1] the following way:
They looked at popular native mobile apps in non-web platforms and sat down to see how they could reproduce these apps with web technologies on mobile. They gave priorities based on frequency and developed the rings tests.

I'm adding the ringmark bug as dependency as I feel it contains a lot of interesting information for B2G to follow in terms of mobile app developer expectations.

[1] http://rng.io/
Depends on: 748248
(In reply to Chris Jones [:cjones] [:warhammer] from comment #3)
> There will be more to come, but I'm going to start tagging these bugs (with
> explanations where possible) as
> 
>  [tech-bug]: user-visible defect that we need to fix asap.  Highest priority.

Should clarify that these *technical* priorities, not product priorities.  Except for tech-bug's which we need to fix yesterday, for a product I would probably take some tech-p2 bugs over tech-p1.  F.e. bug 842217 over bug 711613.
Depends on: 746074
I'm the defacto maintainer of Ringmark/rng.io and also working fulltime on Gaia (@ Bocoup)
Just a random thought (since this is a big bug tree with lots of management involved) - it might be a bit more scalable to make use of a project flag here. Something like:

v1 technical next <-- flag name
v1 technical next = ? <-- nomination from random person
v1 technical next = bug, P1, P2, P3 <-- exact info you just stated

Then build simple dashboards/queries that allow you to look at this from each perspective - noms, bugs, P1, P2, etc.

You could do something similar with whiteboards I guess, but this seems general enough to b2g that a project flag might be worthwhile to make use of.
tracking flags are a different use case that we will need for these bugs eventually too.  sadly there's not a more general mechanism serving both in bz.

phone
Depends on: 797561
Depends on: 391286
Depends on: 525444
Depends on: 650295
Depends on: 721199
Depends on: 822325
Depends on: 846199
Depends on: 834010
Depends on: 846421
Depends on: 846461
Depends on: 846520
Depends on: 846535
Depends on: 1020135
No longer blocks: 738172
Depends on: 738172
You need to log in before you can comment on or make changes to this bug.