Landing ubuntu touch common components to saucy

Registered by Didier Roche-Tolomelli

Continue work to land ubuntu touch components to saucy

Blueprint information

Status:
Complete
Approver:
Jason Warner
Priority:
High
Drafter:
Didier Roche-Tolomelli
Direction:
Approved
Assignee:
Didier Roche-Tolomelli
Definition:
Approved
Series goal:
Accepted for saucy
Implementation:
Implemented
Milestone target:
milestone icon ubuntu-13.05
Started by
Sebastien Bacher
Completed by
Didier Roche-Tolomelli

Related branches

Sprints

Whiteboard

(?)

Work Items

Work items:
[cyphermox] Have indicators, hud, location, network and qa stacks daily landing to saucy (running AP tests): DONE
[ken-vandine] help transitionning to autopilot 1.3: DONE
[cyphermox] help transitionning to autopilot 1.3: DONE
[sil2100] help transitionning to autopilot 1.3: DONE
[timo-jyrinki] help transitionning to autopilot 1.3: DONE
[sil2100] Have unity, misc and oif, stacks daily landing to saucy (running AP tests): DONE
[robru] Ensure all pre-requisite are available in saucy (stuff we are not upstream for): DONE
[timo-jyrinki] Qt 5.0.2 all official modules to saucy: DONE
[timo-jyrinki] Have sdk and platform stacks daily landing (running AP tests): DONE
[ken-vandine] Have webcreds, media and phone stacks daily landing (running AP tests): DONE
[robru] Have webapps, friends and apps stack daily landing to saucy (running AP tests): DONE
[robru] have all the webapps script separated: DONE
[sil2100] diverge between trunk and raring latest components: DONE
[sil2100] have daily release with tests passing of unity-gtk-module: DONE
[didrocks] fix daily release for corner cases due to webapps and diverging the branches: DONE
[didrocks] finish updating the documentation for splitting S and raring: DONE
[didrocks] ignore Vcs-Bzr when splitting branches in daily release: DONE
[didrocks] list all commits by default in cupstream2distro for having full changelog, but still collects bugs: DONE
[ken-vandine] Package uoa-integration-tests: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.