• 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

Build From Branch (and more)

Dates

• Starting: Monday 11th January 2010

• Ending: Friday 15th January 2010

Venue

Accommodation and sprint will take place at West Plaza Hotel
110-116 Wakefield St
Wellington
New Zealand
Tel: +64 4 473 1440

Meeting Schedule

Meeting to start @ *9am*
Lunch break @ *1pm*
End of meeting @ *6pm*

How to get to the Hotel

For directions, please visit:
http://www.westplaza.co.nz/index/West_Plaza_Hotel/Overview/How_to_find_us/
There are several shuttle bus companies covering the leg Airport-town centre, where the West Plaza is located.
Further information can be found on http://www.wellington-airport.co.nz/html/parkingtransport/bus.php.

Attendees

Ideas for Outings/Evenings

• Visit Te Papa, open till 9 on Thursdays.

• http://www.wellingtoncablecar.co.nz/ I might head up there one evening if it's nice and watch the sun set after dinner.

Restaurants and other places

Sprint Goal

Build From Branch is the title but since this original aim we now have the need to process translations jobs in a secure environment also.

• Complete remaining design issues and other problems. See Sprints/BuildFromBranchJan2010#tasks

• Increase collaboration and sense of ownership
• Hack on code like crazed bunnies
• Attempt to at least get one non-Soyuz job through the Soyuz build system on dogfood

Bonus objectives:

• Have both translations and all package branch jobs working end-to-end
• Have a finished UI

What you need?

• A laptop with an up-to-date Launchpad tree

• NZ/AU -> your country power adapter

How it works

• We will pair in 2s, your partner will not be from your team. Julian/Tim will be floating resources.
• We present results at the end of the day
• Each team will have a pre-set list of items to work on, decided on our brainstorming session on Monday
• Laptops closed during talks. People replying to email will have their laptops removed and Windows ME installed on them.

Agenda

9am - Welcome!

• Welcome, set out objectives for the week.
• Why do we need to sprint?
  • Velocity - the hack, test, review cycle is much quicker at a coding sprint
  • Team building - work together to create a sense of ownership for this project and the Soyuz^WLaunchpad build farm which is awesomely complicated and needs more love from more people.
  • Spread the knowledge
  • It's FUN!
• Together, lets:
  • Familiarise everyone with the workflow, how are recipes turned into packages? Tim/Jono/James to present this?
  • Brainstorming session. Work out what needs to be done by throwing ideas to the front.
    • What high level features are we missing?
    • Break these down into manageable chunks of work that can be done in 1/2 or one day by 2 people.
  • Decide on small teams (pairs?) to work on outstanding items.
  • Soyuz will be mostly done at this stage, will be able to float and join with non-Soyuz people to spread the knowledge. Any deficiencies in Soyuz can be rectified on the spot.

Tuesday onwards

Questions

• What do we need to do to move James Westby's package branch importer under the Launchpad umbrella of power and destiny

Ongoing tasks

• [Soyuz] Finish the build start ETA generalisation
• [Soyuz] findBuildCandidate() generalisation
• [Soyuz] Builder page history listing and builder page itself
• [Soyuz] buildd changes to run jobs other than sbuild

• [Soyuz] BuildQueue.specific_job property to cope with multiple job types

• [Soyuz] BuildQueueSet.calculateCandidates() generalisation (currently uses BuildPackageJob)

• [Soyuz] Buildd-manager bugs

• [Soyuz] lib/lp/buildmaster/buildergroup.py: updateBuild() is Soyuz specific for WAITING status, we need to call build type specific code

• [Soyuz] Fix bug 506243 which is to refactor the xmlrpc fault handling away from each build behaviour.

• [Codehosting] Implement builder behaviour and model class(es)
• [Codehosting] Deal with results of build jobs
• [Codehosting] Design the UI
• [Translations] Deal with results of build jobs
• [Translations] Implement builder behaviour and model class(es)