DailyServerBuildsSpec
Launchpad Entry: server-lucid-daily-vcs
Created:
Contributors:
Packages affected:
Summary
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples.
Release Note
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
It is mandatory.
Rationale
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.
User stories
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
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.
Agenda:
* Discuss why we need it * packages that are targeted (and why) * How we might do it
- Generally using bzr-builder infrastructure
- Soon, LP will do it
- When imports don't work?
* Which packages to include and why?
- apache [chuck]
- samba [chuck]
- openldap [mathiaz]
- puppet [mathiaz]
- qemu-kvm [dustin] (maybe kvm-autotest)
- libvirt [dustin]
- eucalyptus [dustin]
- mysql [mathiaz]
- couchdb [chuck]
- postgresql [chuck]
- postfix [chuck]
- cups [???]
* Which packages should we have daily builds for:
- ones that move quickly
- ones that are easily tested
- automated tests ftw
- (ideally, all of them)
* How can we promote it?
- Blog about it
- Create teams with badges ala xorg-edgers (sp?)
- Linking in Launchpad
- From the package, see the daily build
- From a bug, see PPAs that link to the daily builds that fix it
- From project, link to the daily build
Use cases
- daily builds of qemu-kvm (git).
- daily build bisection (to figure out which version broke/fixed):
- need to archive the daily builds (deb-marshall does this)
- users wants to test the latest tip of postgresql (git), couchdb (apache svn repo), erlang (soon on github).
- machines using the daily builds to detect regressions etc.
Issues
- LP git import is breaking
- How to get a community excited about the daily builds?
- Hard to for server packages (db), easier for desktop packages.
- If we're only building daily packages for lucid, then we have a high barrier
- to entry for casual testers.
- Takes a while to set up right now, need to think of how it actually helps
- If upstream build breaks often (tsk tsk) then be careful about subscribing
- lists.
- Maintaining difference between minimally patched debian/ directory for daily
- builds and debian/ directory for Ubuntu release is time consuming.
- Difference increases the closer to release we get.
Contacts
Everyone below knows how to do this.
- dustin
- james_w
- mathiaz
ChuckShort [chuck]
Launchpad and Bazaar are working on daily builds as #1 focus. Talk to jml or vila (or any othe bzr team member).
Actions
ACTION: jml to investigate reducing the roundtrip time from "bug in code imports" to "working code imports". (Probably moving code imports to edge) (an alternative is having another code import service and publish the fixed imports from there)
ACTION: jml to investigate keeping archives of daily builds for improved debugging bisection.
ACTION: (someday) bzr team to look into which packages move the fastest
ACTION: james_w to find out whether the git hash is preserved (and if not, make it so)
ACTION: people noted above to start packaging this.
ACTION: chuck to set up & publish PPA location for this