Technical Requirements by Topic (draft)

Draft of technical requirements for each of the proposed 1105 topics

Continuous integration

Ref

Name

Description

Reference

I1.1

Get server from IS.

Make a public, central, location for Hudson dashboard.

I1.2

Transfer current Hudson configurations.

Move over the existing Hudson deployments from Loic to Linaro infrastructure.

I1.3

New Hudson targets.

Talk to working groups to find additional targets for continuous integration tests under Hudson.

I1.4

Additional Hudson builders.

Investigate whether additional builders are needed for Hudson CI infrastructure. Investigate whether ARM and x86 builders are required. Do we need a farm in the datacentre?

I1.5

Run test suites for Hudson targets.

Investigate whether test suites for selected Hudson targets can be run after a build.

Requirements for new targets for continuous integration testing are expected to be gathered via the new stakeholder process. As these requirements are gathered the need for additional Hudson builders will be evaluated. This is expected to be an ongoing process as working groups evolve.

Patch Management

Ref

Name

Description

Reference

I2.1

Investigate candidate patch management tools for Linaro adoption.

Investigate proposed solutions to see if it meets stakeholder needs.

I2.1.1

Review Toolchain WG solution based on using LP bugs.
http://ex.seabright.co.nz/helpers/patchtrack

I2.1.2

Investigate solution based on using Patchwork.
http://ozlabs.org/~jk/projects/patchwork/

I2.2

Patch tracking requirements.

Generate a list of features required by patch tracking solution.

I2.2.1

Track upstream commits. Solution for identifying patches that have gone upstream and burying them, or flagging them for cherry-picking

I2.2.2

Track local commits. Track local patches to identify whether they are local only, need-upstream, or already upstream.

I2.2.3

Track progress of upstreaming patches.

I2.3.4

Capture versions of software patch was generated from and was upstreamed against.

I2.3

Patch tracking metrics.

Generate a list of metrics to evaluate patch tracking ability.

I2.3.1

How many patches is the WG carrying.

I2.3.2

How long has each patch been carried.

I2.4

Deployment.

Deploy patch management tool for all in Linaro infrastructure.

Derived Archives

Ref

Name

Description

Reference

I3.1

Derived archive rebuild.

I3.1.1

Improved copy archive support.

I3.1.2

Build record support.

I3.1.3

API's for requesting rebuilds.

I3.1.4

BinNMU support.

I3.2

Private archive hosting.

arm-m-private-archive-hosting-infrastructure

I3.2.1

Easily deployable

I3.2.2

Easy to create new archives through a web UI

I3.2.3

Ability to define upload permissions on a per-archive basis

I3.2.4

Accepting uploaded packages into archives

I3.2.5

Publishing archives, so that apt can get packages from them

I3.3

Archive management tools.

arm-m-development-tools

I3.3.1

Currently derived archives are a new feature, and so there are few developer tools that support them. We will improve and create tools as needed based on feedback from Linaro engineers.

I3.4

Support for Linaro use of derived archives

We will support the use of derived archives within Linaro, giving help, advice and fixing bugs

Quality Assurance

Ref

Name

Description

Reference

I4.1

Test suites and benchmarks.

https://wiki.linaro.org/Platform/QA/AbrekTestsuites

I4.1.1

Document automated tests.

Document benchmarks and test suites added to Abrek.

I4.1.2

Extend automated tests.

Investigate adding additional benchmarks and test suites to Abrek.

I4.2

Improve QA Dashboard based on feedback and working group needs.

https://blueprints.launchpad.net/ubuntu/+spec/arm-m-validation-dashboard

I4.2.1

???.

I4.3

QA Tracker

Improvements to QA Tracker and test cases documented on the wiki.

http://qatracker.linaro.org/

I4.3.1

Image test plans.

Add test plans for each image type to the wiki.

I4.3.2

Hardware test plans.

Create test plans for board-specific features.

I4.3.3

QA Tracker changes.

Modifications to QA tracker source.

I4.4

Image testing

Perform testing on milestone and interim image releases

Requirements for QA tracker improvements and new test cases are expected to be gathered via the new stakeholder process. This is expected to be an ongoing process as Linaro evolves.

Image Building

Ref

Name

Description

Reference

I5.1

Improvements to image building infrastructure

Once the image build infrastructure is available, there will be requests for improvements.

I5.2

Better support for developer test images

Currently a developer building a test image has to go through too many steps. We will streamline the process and integrate it better with other infrastructure (e.g. derived archives).

I5.3

Hardware Pack improvements

There will be improvements to hardware packs required to enable their use for hardware enablement

I5.4

Image software selection

There should be a better way for developers to choose which software goes on the image than the current approach of seed/tasks/package lists. Predefined profiles with suggested additions should be available.

I5.5

Abrek/Offspring integration

Investigate integrating Abrek with Offspring to run test suites automatically on images.

I5.6

Android backend for Offspring

Backend for Offspring to build Android targets.

Project Management

Investigate and implement changes in Launchpad for improved project management and reporting.

Ref

Name

Description

Reference

I6.1

Better blueprint management

Blueprints are a central part of specifying work in Linaro, but we are stretching the system currently. We need better ways to manage groups of blueprints, and visualise the progress of each in a particular group

I6.2

Better work tracking

Launchpad is only able to provide the current state of bugs/blueprints/etc., whereas we also want to know how we have done since the last milestone etc.

I6.3

Add work estimation to work item system

Currently we lack a way to tracking time investment, and so estimating based on past performance is hampered. We should provide a way to track the time for completed work items, and so allow velocity/capacity/predicted duration estimates to be made.

Requirements for project management improvements are expected to be gathered via the new stakeholder process. This is expected to be an ongoing process as Linaro evolves.

Cycles/1105/TechnicalTopics/InfrastructureCommentary (last modified 2011-03-25 18:15:23)