• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Code Team Dashboard

Goal

The following themes are drive the high-level direction of our implementation:

• Launchpad 4.0 Themes: Themes

• Codehosting scalability and stability

• Zero OOPS (OOPS bugs)

10.01 has the build-from-branch sprint and bzr-hg based imports

• mwhudson focusing on the recipe work
• abentley integrating ampoule into the job runner
• rockstar finalizing branch upgrade job work
• thumper working on the merge proposal UI

Standup

abentley

• CHR this week

mwhudson

• Email clearout

• work on code import bug 512678

rockstar

• QA
• fixing scanner bugs

thumper

• clearing email and QA
• planning work for the next cycle

Primary Focus

Build from recipe:

Done:

• defined database schema and model
• integrate bzr-builder into the Launchpad tree
• hook into the bzr-builder parser to identify the Launchpad branches
• translate the recipe to and from bzr-builder's data structures and the database tables
• job to turn a recipe into a source package
• work out how to get this source package into a builder to make the binary package

Upcoming:

• recipe branches are linked to the recipes that they are used in
• some portlet or page real-estate to show linked recipes from the branch page
• a list of recipes for the source package view
• recipes owned by a person or team portlet ?

Other areas of concern

As well as having the build from recipe work being a team focus, there are other areas that still need work. Here we have a list of things that we'd like to do in the not too distant future. If there is an existing bug for this work, and it isn't linked, please link them up. If there isn't a bug for it, one should be filed and linked. Ideally we should also have some guesstimate of effort.

At this stage the ordering is not important, but that may change.

Codehosting

• Only have one area for branches, which means pushing into what we now call the "mirrored" area
• Have multiple codebrowse boxes
• Have the smartserver work on a machine that isn't crowberry and use NFS
  • there is an RT for setting this up on staging to test
• Have multiple smartserver front end machines
• Have a job to update stacked information when a branch changes identity
  • or have other magic stacking information that we rewrite

The branch scanner

• Mark bugs as in progress when revision properties are found
• Mark bugs as fix committed when the --fixed property is in trunk ?
• Set the revision id when marking a merge proposal as merged

The branch-index page

• The import details for import branches should be much further up the page
• Add official links portlet
• Don't show the merging section if there is nothing to show (import branches - or not logged in)
• Branch subscriptions should record the registrant, and be editable by the registrant

Code reviews

• Spacing in initial email for bugs
• Extra options for propose merge

• Resubmit should allow changing all branches (Bug #504369)

• Merge it! button and associated branch job
• Add a description
• Initial email on needs review

• Revision email should only show most recent proposal for source branch (Bug #504356)

• Break out review status from merge status
• Show messages from superseded proposals on the page
• Add a date_last_modified
• add js-action class to reply links to make them green
• keep reply links for merged proposals
• the diff hyperlink at the top should scroll the user down to the diff
• general keyboard short cuts
• refresh list of reviews after review submitted via ajax
• garbage-collection for diffs
• update preview diff when status becomes active, if needed

Code imports

Code import service important for both the distributed development and daily build efforts.

• Code imports that don't add revisions shouldn't request a pull - bug 512678 in progress

• Add a new code import result for success of partial import - (bug 512680)

• Foreign branch imports should incrementally import branches - (bug 512683)

• "We should be prepared for 5000 new imports"
  • Will require more machines for sure (existing machines are quite old and slow)
  • Also some bugs should be fixed to make best us of the machines we have

• An API for code imports is needed (bug 366102).

• Exponential backoff for failing imports (bug 413637)

• new code import emails should include where they are importing from and their type - (bug 512689)

• should upgrade existing imports to 2a format

• All bugs tagged 'code-import'

Branch information on other pages

• Latest branches touched portlet for project
  • should be generic so it works for project groups, person, distro et al

Upcoming Sprints

April 2010 Dunedin (TBC)

Code Team People

Feel free to say something about yourself here

• Aaron Bentley (abentley)
• Paul Hummer (rockstar)
• Michael Hudson-Doyle (mwhudson)
  • I do lots of codehosting, code imports and codebrowse stuff
• Tim Penhey (thumper)