Aki, I can't speak for updates but please keep making the builds for us
(Web QA). We are using the Unagi engineering builds extensively.
The main reason is that we are having a hard time getting enough of the
new devices to replace the old ones (we need about a dozen of them).
We really should have replacing the old Unagi devices out in the wild
with the new device as a pre-req for switching off the builds, which
would solve the device problem for the locale team too.
Zac
On 28/08/2013 18:05, Aki Sasaki wrote:
On 8/27/13 8:27 PM, Nicolas B. Pierron wrote:
On 08/27/2013 06:38 PM, Aki Sasaki wrote:
At today's cross-functional B2G meeting, I asked whether it made sense
to point the old unagi update channels at the new ones, so older builds
would get updated to the latest:
https://bugzilla.mozilla.org/show_bug.cgi?id=909311
However, it turns out that we're phasing out unagi as a testing
platform. Would it make sense to turn off unagi updates (and
potentially releng-supported unagi builds, as well)?
Does that mean that we will remove it from the sources, or that we will
stop making builds for it on TBPL?
The latter.
Do we still want to support
compiling for it?
What is the ETA for that, and what is the spec of the substitute
hardware of reference for benchmarking?
I don't have answers for those.
The ETA would be sometime after we get a decision here.
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
