Skip to content

Change Timing of Burndown Meetings #148

@jberkus

Description

@jberkus

Contributors, Release Team, SIG Leads:

Previously, burndown meetings have been at 10am PST/PDT every day they are held (MWF in Slush, then every weekday in freeze). This timeslot has two problems:

  1. On Thursdays, it conflicts with the Community Meeting right when the Release Lead needs to be mobilizing the community to close last-minute bugs.
  2. 10am PDT is pretty late for folks in Europe/Asia.

The latter has been a real problem, resulting in a minority of SIG leads actually attending the burndown meetings.

However, I am also aware of the limitations of the schedules of Googlers who work in Mountain View, which makes meetings earlier in the day hard. Given that important roles in each RT are generally filled by MTV googlers, simply switching to 8am PST/PDT meetings would cause a different group of people to drop out. Also, for those of us who work on mixed US/Europe teams, that 8am timeslot is awefully crowded.

As such, I can think of 3 possible courses going forwards:

  1. Ignore the issue and keep the burndown meetings at 10am
  2. Move the meetings to 8am Pacific and ask the googlers to change their commutes when needed for burndown;
  3. Alternate burndown meeting times so that we spread the inconvenience around;
  4. Some other creative solution?

If you are a current or former release team member, a SIG lead, or a contributor with a feature in 1.11, please comment below on what timings would work best to ensure that you attend burndowns.f

Metadata

Metadata

Assignees

No one assigned

    Labels

    sig/releaseCategorizes an issue or PR as relevant to SIG Release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions