I dogfood, on v180+ v2.1, and it's been testing me a bit lately too.
I feel like I'm in a catch 22 between moving to v2.2 to get all of the
fixes I need and all the latest functionality and being on v2.1 for
stability. As v2.2 is unstable, you want to run on v2.0 or v2.1 which is
more stable.. but if you file a bug against v2.1 it's unlikely to get
any attention unless it's very severe or you have very very clear STR,
so what's the point in dogfooding if your bugs aren't attended to?
Some of this lies in the project's focus upon the v2.2 branch. I feel a
dogfooder has little chance of getting feedback from v2.1 addressed
because the project's focus has already moved onto v2.2.
Also our weakness in letting device bugs slip in (ie not enough
on-device testing). This is my area (no need to remind me!) and we're
working on it of course.
However it'd be great to get more commitment from the project managers
on addressing UX issues and papercut-type issue that come from v2.1 via
people who've used the device extensively.
That way we can recommend to the majority of dogfooders (especially
non-staff who have less patience), to be on v2.1, which has a better
balance of features and stability, rather than getting frustrated on the
bleedin' edge of nightly.
Zac
On 14/10/14 14:20, smaug wrote:
Hi all,
the recent instability of Flame nightlies + v180 has been rather massive:
not being able to answer the calls (possibly fixed now),
somewhat broken proximity handling (leading to random clicks on the
screen when one happens to be able
to place/answer a call),
OTA being broken, running out of battery in couple of hours etc.
Do we have any concrete plans to try to keep dogfooding phones
actually dogfoodable most of the time
(in other words at least to backout changes more aggressively).
And how can a dogfooding phone user help here?
I decided to move back to old unagi for now until I hear feedback
about nigtlies being usable again.
br,
-Olli
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
