Pilot and explore options for componentizing release services
Basic idea is that we need to be able to better slice and dice the results from our release data collecting efforts.
This Pilot should investigate and pilot with ARM VE doing:
a) an all-linaro as well as a component/build specific release notes
b) an all-linaro as well as a component/build specific release announcement (so you can forward sub-announcements to specialist communities
c) a view of all relevant release notes and release announcement text for a release for an individual board/target
later: d) a view of all relevant release notes and release announcement text for a release for each engineering build baseline
Blueprint information
- Status:
- Not started
- Approver:
- Alexander Sack
- Priority:
- Undefined
- Drafter:
- Fathi Boudra
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- Accepted for trunk
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Meta:
Roadmap id: RELEASE_
Headline: Release Team has explored option to produce a set of community directed release notes and announcements from one input set in a slice and dice manner.
Acceptance: Release Team has presented a plan about how to tackle this issue and have run a manual pilot with ARM. All-arm, all-VE-board, all android release notes and announcements are available.
Work Items
Work items:
Arrange a kick off call with relevant brains: TODO
Start an idea pool to collect approaches we could take: both on presentation (output) as well as input side to ensure that we have maximum reuse, but still high customization: TODO
Discuss and collect requirements from all output channel stakeholders (distribution owner, baseline owner, board owner, component owner): TODO
Work on solutions; make a proposal to management: TODO
Pilot proposal manually for ARM VE: TODO
Decide on roadmap steps to move forward: TODO
