UbuntuDeveloperSprintWiesbaden

Differences between revisions 49 and 50
Revision 49 as of 2006-08-22 08:09:04
Size: 6828
Editor: p54A82627
Comment: OLPC discussion
Revision 50 as of 2006-08-23 15:17:47
Size: 6901
Editor: p54A83C35
Comment: release management items
Deletions are marked like this. Additions are marked like this.
Line 79: Line 79:
 * Release management

  * Stop the pain
  * Scheduling milestones

Ubuntu Developers Sprint - August 2006

Dates

The next distro sprint will take place from 09.00 Monday 21st - 17.30 Friday 25th August 2006, Please arrange to arrive on Sunday 20th and depart Saturday 26th.

Venue

The venue will be Hotel Achat, Wiesbaden, Germany http://www.achat-hotels.de/wEnglisch/02_hotels/Uebersicht_Hotels/26_Uebersicht.php?navid=26

How to Get There

The nearest airport is Frankfurt. You can find instructions on how to get to the hotel from the airport from this link http://www.achat-hotels.de/wEnglisch/02_hotels/Anfahrt_Lage/26_Anfahrt_Lage.php

Although anyone is welcome to attend, the sprint is a face-to-face work session for the development team, and takes place before feature freeze to provide an opportunity to finish off projects before the deadline. It's not a spectator event, but a hands-on developer event.

Attendees

Name

Arrival

Departure

Travel Info

Roomie

Confirmed

AdamConrad

BenCollins

Sunday, 07:10

Saturday, 14:20

Richmond => Dallas => Frankfurt, Frankfurt => Chicago => Richmond

RodrigoNovo

Yes

ColinWatson

BA914 Sun 21:20

BA905 Sat 14:30

LHR <-> FRA

IanJackson

Yes

DanielHolbach

Sunday evening

Saturday

Trier->Wiesbaden, Wiesbaden->Trier

SebastienBacher

Yes

FabioMassimoDiNitto

OliverGrawert

FrankSchoep

Sunday ~ 18:30

Saturday ~ 12:00

Train

KenWimer

Yes

HenrikOmma

Sunday, late

Tuesday

By car

IanJackson

20:37 Sun (Hbf)

22:20 Fri (Hbf)

Trains

ColinWatson

Yes

JonathanRiddell

Edinburgh -> Frankfurt arriving Sun 20th 21:15

Frankfurt -> Edinburgh leaving Sat 26th 21:55

Yes

KarianneFogHeen

With Tollef

Fri

Air: OSL -> Frankfurt, Train: Frankfurtf - Wiesbaden

Tollef

Yes

KenWimer

Monday midday

Sat

Train home (Wiesbaden-Bamberg)

FrankSchoep

MartinPitt

Sun around 18:00

Sat around 11:00

train (direct ICE to Dresden, yay)

Yes

MattZimmerman

LH455 0935 Sun

LH454 0945 Sat

Yes

MatthiasKlose

Sun

Sat

Train

MichaelVogt

Yes

MichaelVogt

Sun

Sat

Train or with dholbach

MatthiasKlose

Yes

OliverGrawert

Sun

Sat

Car: Kassel -> Wiesbaden

FabioMassimoDiNitto

Yes

RodrigoNovo

Sun 20 Aug, 01:00 PM

Sun 27 Aug, 07:00 AM

Airplane: CWB->GRU->LIS->FRA, FRA->LIS->GRU->CWB

BenCollins

Yes

ScottJamesRemnant

Sun 15:05

Fri 21:45

BHX -> FRA

Yes

SebastienBacher

Sunday

Saturday

train or with dholbach

DanielHolbach

SimonLaw

Mon 08:55

Saturday 10:50

YUL→FRA, FRA→YUL

Yes

TollefFogHeen

Sun 11:45

Fri 17:20

OSL→FRA, FRA→OSL

KarianneFogHeen

Yes

AndreasLloyd

Sun 20:30

Saturday afternoonish

Train from Copenhagen

Yes

Agenda

Development

https://launchpad.net/distros/ubuntu/edgy/+specs

  • Edgy goals: The Reckoning. It's time to make a decision on goals which are behind on progress, and drop goals which aren't going to make the feature freeze deadline (7 September). My proposed format for this is to sit with each of you individually for perhaps 30-60 minutes to review your progress in depth, bringing in third parties as appropriate where there are dependencies involved.
    • Each goal will fall into one of three categories: keep, defer or rescue. Rescue means that the goal is in trouble, but we think we may be able to rescue it by putting our heads together in a group session.
  • Rescue missions. As above, these will be largish group sessions focused on rescuing a particular Edgy project. We'll identify blocking issues, brainstorm solutions to them, and take a final decision on whether we can reasonably pursue the goal for the release.
  • Hack sessions. These will be focused, pairwise or small group work sessions. They will usually be related to a feature goal, but
    • infrastructure projects are also appropriate where we have time.

      If you want to ensure that you have time reserved with some of your teammates for such a session, list it here

  • Your ideas here

Process Discussions

These will be group sessions (some for the entire team) about process questions: how and when particular tasks should be performed, and how we'll ensure that they happen regularly and efficiently.

  • Archive administration (mdz, archive admin team, et al)
    • queue/new processing
    • Stable release updates
    • buildd operations
    • backports
  • Release management
    • Stop the pain
    • Scheduling milestones
  • Artwork workflow (mdz, dholbach, riddell, fschoep, kwwii, et al)
  • Developer relations (mdz, all)
    • REVU - who and when?
    • Responding to community input (e.g., ubuntu-devel) - who and when?
    • Brainstorm - attracting new developers
  • Bug workflow (sfllaw, all)
    • Triage process
    • Handoff to developers
    • Launchpad workflow (milestones, release targeting, etc.)
  • Feature showcases (mdz, all)
    • Mark has asked that we create a process to showcase features in
      • development. The basic idea is that the assignee will present a short user-oriented explanation of the feature and its rationale, and lead a brief Q&A discussion with the community around it.

    • We'll discuss the format, location, timing and responsibility for these sessions
  • Your ideas here

Bug Day

As a followup to the bug workflow process discussion, I'd like to hold a full-blown bug day during the sprint. This may not end up being exactly a day, but I want to put the process into practice while we're still together. Naturally, the community will participate as well. We can also use this time to dedicate developer time to particularly difficult and severe bugs as nominated by Simon and the QA team in advance.

Goals

At the end of the sprint, we should have:

  • Refined your Edgy goals, with a rationale and roadmap for each which is deferred or rescued
  • Notes / partial drafts for the process items
  • Put a measurable dent in the Edgy bug list
  • NOT lost any laptops, been thrown out of any public establishments, spread any viruses, or taken part in other disasters
  • Enjoyed ourselves immensely

UbuntuDeveloperSprintWiesbaden (last edited 2008-08-06 16:13:51 by localhost)