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)

3.1.12 is a very short cycle and not a lot is happening.

• mwhudson focusing on the recipe work
• abentley integrating ampoule into the job runner
• rockstar making the scanner use branch jobs
• thumper working on the merge proposal UI

The 3.1.13 cycle has our build from recipe sprint.

Standup

abentley

• working on showing status of preview diffs
• dealing with a lot of email, looms vs pipelines vs branches
• tomorrow fixing an annoying bug

mwhudson

• got some recipe model code ready for review
• herded some bzr-svn imports
  • seem to be cpu bound
  • need to start the process of getting some newer faster import machines
• today chasing the review and more model code

rockstar

• chillaxing

thumper

• did emails and calls
• today more emails, calls, flights and expenses

Primary Focus

Build from recipe:

Now:

• mwhudson defining database schema and model

Upcoming:

• integrate bzr-builder into the Launchpad tree
• hook into the bzr-builder parser to identify the Launchpad branches
• store the recipe text with DB ids for branch identities and translate from and to this value using the bzr-builder branch parser hooks
• 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 ?
• 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

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

• use the + icon for propose for merging 498065 (in progress - thumper)

• 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
• Edit target (or resubmit with changed target?)
• Edit prerequisite branch (or resubmit with changed prerequisite?)
• 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
• Break out review status from merge status
• Show messages from superseded proposals on the page
• Add a date_last_modified
• Add the diff sizes to the active reviews page
• 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
• notify when diff generation is pending
• update preview diff when status becomes active, if needed

Code imports

• Code import service important for both the distributed development and daily build efforts.
• "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).

• bzr-hg is approaching the point where it should be integrated soon
  • slightly stuck at the db patch level though.
• new code import emails should include where they are importing from and their type

• 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

January 2010

• Build From Branch - Wellington, NZ

• LCA - Wellington, NZ

February 2010

• Team Lead meeting - London, NZ

Code Team People

Feel free to say something about yourself here

• Aaron Bentley (abentley)
• Paul Hummer (rockstar)
• Michael Hudson-Doyle (mwhudson)
• Tim Penhey (thumper)