Improve Linaro Android Branch Names

Registered by Zach Pfeffer on 2012-03-29

The names we've given to our branches could be improved.

Some subprojects that are not included in, and not really related to, upstream AOSP (e.g. busybox) are maintained in branches named after specific Android versions, when really all Android versions should be using the same branch.

Similarily, some subprojects that typically don't change between minor releases (e.g. device/linaro/*) would be better off being on more generic branch names.

This will make it easier to update to newer Android releases, to support several Android versions at the same time, and to create a build based on an older Android release but with newer additions (e.g. do a gingerbread build for a device too low-end to run ICS).

Blueprint information

Status:
Started
Approver:
Zach Pfeffer
Priority:
Medium
Drafter:
Bernhard Rosenkraenzer
Direction:
Needs approval
Assignee:
Bernhard Rosenkraenzer
Definition:
Drafting
Series goal:
Accepted for 2012q1
Implementation:
Good progress
Milestone target:
milestone icon backlog
Started by
Bernhard Rosenkraenzer on 2012-04-04

Related branches

Sprints

Whiteboard

Notes:
[2012/4/11 pfefferz] Put notes here.
[2012/4/30 pfefferz] Moving to 12.05 because the binary components still nee to be done.
[2012/5/29 pfefferz] Moved to backlog due to tree being in flux.

Meta:
Roadmap id: ANDROID2012-ICS-RELEASE
Headline: Linaro Android branch names have been improved.
Acceptance: All branch names that can be improved, have been.

(?)

Work Items

Work items:
Reogranize platform/external/busybox branches: DONE
Reorganize device/linaro/* branches: DONE
Update manifests to use them (done after 12.04 release cut): DONE
Reorganize platform/hardware/samsung/origen/gralloc_ump branches: TODO
Reorganize platform/hardware/samsung/origen/ump branches: TODO
Reorganize ti/proprietary-open branches: TODO
Identify other subprojects with suboptimal branching: INPROGRESS
Reorganize them (if any are found): TODO

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.