Just thinking, if we were to go on the train model; I think Product UR and
UX should be in a pre-Nightly branch.
One of the main issue is that UX is currently behind because of loss of
people power. Dev and UR/UX should still talk in this phase to help iron
any engineering kinks that might come out of it; at the same time if we
possibly try to have this ahead, maybe the spec will be out before Dev
start the cycle?
Without a schedule that people are following and can follow; I don't think
we're in a position to ship on time for everything.
I believe we're currently at risk for a number of items. Why do I say that
these items are at risk? Because they are landing near the end of the
schedule with not enough time for testing and refixing:
1. Pin-the-web
1. Pin video
2. Pin photo
3. View top pages
4. View history
2. Telemetry
3. Performance
4. Late customisation
5. RTL
6. Some NGA
QA cannot fully test integration until everything is completely in. We may
be able to test parts during the cycle provided that the UI is there for
the backend items.
I really believe that we have to leave a 2 week to 1 month buffer in future
scheduling so that we can ship with quality. So far every time we estimate
a schedule, we have been at least a month off. We might as well start
accounting that way.
Regards,
Naoki
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
