Summary

This discussion will talk about defining new member deliverable for Android LEBs, reviewing what's been delivered and assessing if we can raise the bar, discuss other low-cost high-volume board that currently exist or are on the way (Nexus One, Nexus S, Snowball), talk about LEB candidates, discuss cost ceilings (is the Elba board too expensive, for instance).

Recommended reading: https://wiki.linaro.org/Platform/Android/EvaluationBuild/MemberDeliverables (as presentation)

Discussion points.

  • What are we going do with the LEBs?
  • Minimum requirements on HW enables in LEB?
  • Deliverables from member
  • legal (Copyright...)
    • How can we contribute code to AOSP if it based on code from members?

Release Note

Rationale

We need to know when a board (+ code/binary delivery) qualifies as a LEB.

User stories

Assumptions

-

Design

-

Implementation

-

Verify patches for all boards

-

Test/Demo Plan

(This need not be added or completed until the specification is nearing beta.)

Unresolved issues

-

Additional information

Description

Link

Android Evaluation Build Member Deliverables

https://wiki.linaro.org/Platform/Android/EvaluationBuild/MemberDeliverables

internal/archive/Platform/Android/Specs/LEBBoardReviewAndDeliverableRequirements (last modified 2013-08-29 09:01:49)