703693, 703694, 703696, 703700, 742639, 744491, 744549, 746385, 747505, 749487, 749519, 750515, 750526, 751943, 752117, 752685, 753660, 753801, 753983, 756315, 756976, 758477, 759505, 759590, 759593, 760086, 760616, 761867, 762833, 763164, 763183, 763375, 768521, 769170, 769842, 772447, 775703, 775962, 775963, 791810, 795852, 841929, 847520, 892020, 896679, 899656, 899661, 899675, 899704, 899707, 905374, 907931, 914275, 914391, 914754, 914846, 914848, 914850, 914868, 919799, 931055, 961502, 964069, 965340, 965775, 973958, 977231, 977863, 978524, 980010, 981250, 988062, 989569, 994965, 995005, 1001860, 1007357, 1015758, 1021785, 1029662, 1029925, 1037247, 1038533, 1046258, 1055037, 1057832, 1058109, 1073790, 1080088, 1081220, 1084382, 1087362, 1089504, 1093239, 1097243, 1100442, 1116756, 1121758, 1157332, 1157463, 1159463, 1163067, 1165479, 1166386, 1168608
all webRT bugs on desktop blocking this bug https://bugzilla.mozilla.org/buglist.cgi?component=Web%20Apps&component=Webapp%20Runtime&product=Firefox&bug_status=__open__&order=bug_id
Hi Myk and Vishy, Is the WebRt team ready to go-live with the Desktop Program? Any outstanding issues / concerns other than those open bugs called out? Please Comment. Thanks!
> Is the WebRt team ready to go-live with the Desktop Program? Erm, I'm not the right person to answer this question, as I've only been peripherally involved in the latest push to deliver a desktop runtime and marketplace. > Any outstanding issues / concerns other than those open bugs called out? From the engineering perspective, my primary concern is the same as it has been for a while now: successful software products need ongoing development, maintenance, and quality assurance, but the desktop runtime has not received any such attention for a very long time. Thus it is likely to be a frustrating and incomplete experience that does not meet the needs nor satisfy the desires of its users. On another note, I'm unsure how y'all intend to use the "depends on" field of this bug to track work, but it seems like a grab-bag of open desktop bugs rather than a focused list of requirements. If it's intended to track all desktop bugs, then it'll get out-of-date constantly and will never be driven to zero (because there are never zero bugs in any software product, and the runtime is no exception), so it would be better to use the query in comment 0 to track those bugs. Otherwise, if it's intended to track high-priority bugs, or just blockers, then it needs pruning, since it currently includes bugs that are very low priority and will not be resolved for a very long time, if ever.
(In reply to Myk Melez [:myk] [@mykmelez] from comment #2) > From the engineering perspective, my primary concern is the same as it has > been for a while now: successful software products need ongoing development, > maintenance, and quality assurance, but the desktop runtime has not received > any such attention for a very long time. Thus it is likely to be a > frustrating and incomplete experience that does not meet the needs nor > satisfy the desires of its users. Having been involved in recent triage sessions with Vishy and Harald, and having seen the results of Michael Ellis's testing of apps we want to feature for desktop, I think the current state of the desktop runtime is good enough for us to expose it to a larger audience. When it gets more uptake, we will definitely find more bugs and we'll need resources to address them.
Per bug 1238079, we're going to disable the desktop web runtime and remove it from the codebase, so we won't fix these bugs in it.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.