Daily builds for server packages

Registered by Chuck Short on 2010-04-26

Upstream projects such as PHP and Apache prefer that users who are reporting bugs with their software to use the latest unmodified software in order to test fixes. We should provide a PPA for users to install unmodified upstream software so we can provide quality bug reports for our upstreams.

This is a continuation of the work started in lucid.

Blueprint information

Status:
Started
Approver:
Jos Boumans
Priority:
Medium
Drafter:
Chuck Short
Direction:
Approved
Assignee:
Chuck Short
Definition:
Approved
Series goal:
Accepted for maverick
Implementation:
Started
Milestone target:
milestone icon ubuntu-10.10
Started by
Jos Boumans on 2010-09-03

Related branches

Sprints

Whiteboard

Status:
Started, was blocked on #599102, should now be fixed-released. Drizzle does not need this, as they already have their own daily trunk build PPA (clint-fewbar)

Complexity:
maverick-alpha-3: 2
ubuntu-10.10-beta: 2
[zulcss] ubuntu-10.10: 2
[clint-fewbar] ubuntu-10.10: 1
[serge-hallyn] ubuntu-10.10: 1

Roadmap notes:
Spec timeboxed to 2 points for Alpha3 & Ubuntu Beta
Write HOWTO so load can be shared among people afterwards

Work items for maverick-alpha-3:
(1) Write Edgers Howto so other people can contribute: POSTPONED
Create memcache Edgers PPA: DONE
Import memcache upstream stream into bzr branch:DONE
(2) Upload memcache to PPA and publicize: POSTPONED
Create varnish Edgers PPA: DONE
Import varnish upstream stream into bzr branch: POSTPONED
Upload varnish to PPA and publicize: POSTPONED
Create drizzle Edgers PPA: DONE
Import drizzle upstream stream into bzr branch: POSTPONED
Upload drizzle to PPA and publicize: POSTPONED
Create php Edgers PPA: DONE
Import php upstream stream into bzr branch: POSTPONED
Upload php to PPA and publicize: POSTPONED
Create libvirt Edgers PPA: DONE
Import libvirt upstream stream into bzr branch: POSTPONED
Upload libvirt to PPA and publicize: POSTPONED
Create nagios Edgers PPA: DONE
Import nagios upstream stream into bzr branch: POSTPONED
Upload nagios to PPA and publicize: POSTPONED

Work items for ubuntu-10.10-beta:
(1) Write Edgers Howto so other people can contribute: POSTPONED
(2) Upload memcache to PPA and publicize: DONE

Work items for ubuntu-10.10:
(1) Write Edgers Howto so other people can contribute: DONE
(1) Verify #599102 is indeed fixed-released: DONE
(2) Import varnish upstream stream into bzr branch: DONE
(2) Upload varnish to PPA and publicize: DONE
[clint-fewbar] Test using the Edgers HOWTO and provide feedback: POSTPONED
[serge-hallyn] Test using the Edgers HOWTO and provide feedback: DONE
[clint-fewbar] Import drizzle upstream stream into bzr branch - drizzle-developers team already maintains a trunk PPA: DONE
[clint-fewbar] Upload drizzle to PPA and publicize - blog post http://fewbar.com/2010/09/drizzle-maverick-ppas-and-you/ explains upstream PPAs: DONE
[serge-hallyn] Import libvirt upstream stream into bzr branch: DONE
[serge-hallyn] Upload libvirt to PPA and publicize: DONE

Targets of opportunity:
Import php upstream stream into bzr branch: TODO
Upload php to PPA and publicize: TODO
Import libvirt upstream stream into bzr branch: TODO
Upload libvirt to PPA and publicize: TODO
Import nagios upstream stream into bzr branch: TODO
Upload nagios to PPA and publicize: TODO
Create munin Edgers PPA: TODO
Import munin upstream stream into bzr branch: TODO
Upload munin to PPA and publicize: TODO
Create opennms Edgers PPA: TODO
Import opennms upstream stream into bzr branch: TODO
Upload opennms to PPA and publicize: TODO
Create openldap Edgers PPA: TODO
Import openldap upstream stream into bzr branch: TODO
Upload openldap to PPA and publicize: TODO
Create corosync Edgers PPA: TODO
Import corosync upstream stream into bzr branch: TODO
Upload corosync to PPA and publicize: TODO
Create pacemaker Edgers PPA: TODO
Import pacemaker upstream stream into bzr branch: TODO
Upload pacemaker to PPA and publicize: TODO
Create rhcs Edgers PPA: TODO
Import rhcs upstream stream into bzr branch: TODO
Upload rhcs to PPA and publicize: TODO

Reviewers: ttx + jib

ttx review / 20100526:
 * In order to prioritize correctly, could you split the set into prio 1/2 based on how desirable each dailyVCS is ?
 * Wasn't libvirt done during the Lucid cycle ?
 * Suggested assignees: zulcss / ?
 * Estimated complexity: 7-9 total
 * Suggested priority: 2/Medium for prio1 and 3/Low for prio2
 * Suggested Subcycle: Iteration 2 (Alpha3) for prio1 and Iteration 3 (Beta) for prio2

jib review:
 * Upto and including libvirt i'd consider prio 1
 * Estimated complexity for prio 1 would be 3-4, which I think is a good load
 * The process of setting up an edgers PPA should be well understood now. Can we
    engage upstream to contribute? See also the server-maverick-community spec for thoughts on this

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.