►
From YouTube: Kubernetes 1.20 Release Team Meeting 20200914
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
The
okay
welcome
everyone
to
the
first
kubernetes
1.20
release
team
meeting.
This
is
week
one.
My
name
is
jeremy.
Before
we
get
started
just
a
reminder,
this
meeting
is
recorded
and
will
be
available
on
the
internet.
A
This
is
a
kubernetes
release
team
meeting,
so
we
are
bound
by
the
kubernetes
code
of
conduct,
which
can
be
boiled
down
to
be
excellent
to
each
other.
Don't
say
anything
that
you
wouldn't
want
said
to
yourself.
A
So
this
is
the
first
meeting,
so
I
thought
we
could
just
start
out
by
having
all
of
the
area
leads,
introduce
themselves
and
just
tell
us
a
little
bit
about
yourself.
Your
previous
experience
on
the
release
team
and
what
you're
looking
to
get
out
of
out
of
the
release
this
time
around
and
we'll
we'll
start
as
we
always
do
with
enhancements
in
kirsten.
B
Hi,
I'm
kirsten
I'm
a
software
engineer
at
red
hat
and
I
am
the
enhancements
lead.
I
was
a
shadow
for
two
release
cycles
and
then
I
was
also
a
shadow
on
bug
triage.
I
think
my
first
cycle
and
yeah.
I
guess
I
really
enjoyed
working
on
enhancements
before
and
getting
to
know
all
of
the
issues
and
stuff.
So
I
just
felt
like
it
would
be
pretty
cool
to
do
it
again
and
try
to
you
know,
lead
a
team
and
yeah.
I
guess
that's
it.
I
just
really
enjoy
working
on
the
release
team
too.
A
Awesome,
thank
you.
So
much
I've
dropped
the
agenda
into
the
chat,
so
anybody
that
missed
it,
please
add
yourself
as
a
attendee.
So
we
have
a
record
of
who's
here.
Next,
we'll
go
to
ci
signal
with
rob.
C
Hey
hello,
I'm
rob
I'm
in
between
contracts
at
the
moment,
and
I
was
a
shadow
on
the
119
release
team
and
very
happy
to
take
up
doing
team
lead
for
120
and
so
just
want
to
say
thanks
to
dan
for
all
of
the
support
and
help
and
sort
of
onboarding
on
119
and
for
this
release
and
together
with
dan
and
jorge
and
tess
jennifer.
We
wanted
to
try
and
automate
some
of
the
reporting
for
the
weekly
meeting,
and
so
I've
made
a
start
on
I'm
looking
at
that.
C
A
Thank
you.
Moving
on
bug
triage
with
vlad.
D
Hey
I'm
glad
I
work
on
many
things
at
shopify,
observability
search
and
streaming.
I've
been
a
bacteria
shadow
for
119
with
john
lucca,
so
this
cycle,
I'm
happy
to
be
leaning
back
triage,
exciting
times.
Thank
you
for
having
me.
A
Yeah
thanks
for
coming
back,
I
seen
here
there's
some
numbers
associated
with
prs
and
and
issues
have
you
gone
through
and
done
that,
or
did
I
copy
that
from
the
last
time
around.
D
That's
me:
I
updated
them
a
few
hours
ago.
Awesome.
A
Thank
you.
Oh
we
can
can
review
those
next
time
and
just
thanks
for
updating
the
documents
we
have
that
next
up
docs
with
anna.
E
Hey
everyone,
I've
been
on
shadow
since
1.7,
I
believe
yeah.
So
I
was
a
shadow
for
various
roles
and
I
was
able
to
become
a
lead
this
time
for
dogs.
So
I'm
like
super
excited
for
this
release
and
I'm
glad
to
meet
everyone
here
and
work
ever
work
with
everyone.
F
F
I've
been
a
release,
note
shadow
since
118,
so
a
couple
of
releases
now
and
I'm
looking
to
continue
with
the
release,
notes
ongoing
automation,
which
is
something
that
relent
is
working
on
so
I'll,
be
hopefully
working
working
with
them
to
try
and
get
that
move
forward,
and
I'm
looking
forward
to
working
with
you
all
awesome.
Thank
you
so
much.
A
Comms
with
james
or
with
joseph
sorry,
everybody,
I
know
exactly
I'm
joseph
sandoval,
I
am
the
sre
manager
with
the
adobe
advertising
cloud,
so
anything
that
is
with
platform
tooling
making
developers
go
fast
with
kubernetes.
It
falls
into
my
domain.
I
shadowed
with
kubernetes
119
under
max,
which
was
a
really
enjoyable
experience,
and
the
goal
really
was
for
me
to
like.
A
I
was
going
to
try
to
see
if
I
could
bounce
around,
but
I
got
asked
to
actually
be
the
lead
for
this
120,
which
is
kind
of
great
and
exciting,
because
I
think
the
knowledge
that
I
have
just
coming
off
of
119.
I
think
some
of
the
other
shadows
experience
I'm
hoping
to
kind
of
inject
and
really
try
to
take
some
of
those
learnings
and
improve
the
experiences
and
help
the
individuals
who
are
kind
of
going
through
the
same
things.
A
I
was
so
really
excited
about
this
and
then
hopefully,
long-term
goal
is
you
know
I
love
hanging
out
with
the
the
overall
release
team
like
steve
and
all
them
like
I've
learned
so
much
about
the
process,
so
just
kind
of
enjoying
just
being
involved
in
this
aspect
of
it.
A
Thanks
for
stepping
up
to
do
120.,
okay,
release
branch
management
with
carlos
no
updates,
do
you
have
plans
for
doing
the
120
branch
cut?
What,
when
will
that.
G
G
I
work
on
the
sig
release
signs.
I
guess:
release
115
as
a
branch
manager
associate
in
that
time.
We
don't
have
this
role
anymore.
We
have
the
branch
man
branch
managed
shadow.
We
now
have
the
branch
measure
associated
with,
because
it's
a
little
bit
different
from
the
the
entire
release
team
and
size
116
by
acting
as
a
branch
manager
and
helping
you
all
to
succeed
in
their
release.
I'm
gonna
help
on
the
120,
maybe
change
in
the
future.
We
don't
know
we
had
didn't.
H
Absolutely
hello,
my
name
is
lachlan
evenson.
I
work
at
microsoft
as
a
pm,
I
have
served
in
the
kubernetes
release
team
I've
done
from
114
through
116..
I
came
back
as
an
ea
for
118,
and
now
I'm
back
as
120.
so
excited
to
serve
with
you
all.
Thanks
for
having
me
jeremy,
I'm
very
excited
about
this.
Being
the
last
kubernetes
release
for
the
year,
2020.
we're
going
to
go
out
with
a
bang,
which
would
be
a
lot
of
fun
excited
to
serve
with
you
all.
H
The
the
role
of
the
ea
is
really
to
support
the
team
and
bring
any
knowledge
from
past
releases
and
context
from
how
we've
dealt
with
issues
in
previous
releases.
So
if
you
have
any
questions,
please
feel
free
to
reach
out
to
me
on
slack
happy
to
answer
those
questions.
My
main
role
for
the
first
two
weeks
is
really
helping
you
all
with
shadow
selection.
So
all
the
leads
have
been
given
access
to
the
responses
for
the
shadow
selection
applications.
H
I
would
like
you
all
to
individually
go
through
those
responses
and
make
your
pre-selections
and
then
work
with
me
to
finalize
those
selections.
So
I've,
given
you
all
a
couple
of
days
to
at
least
pre-select
that
list,
but
we
would
really
like
to
get
them
finalized
within
the
next
week
or
so.
So,
if
you
have
any
questions,
feel
free
to
reach
out
to
me
or
if
you
haven't,
don't
have
access
to
that
document.
I
can
certainly
help
with
that
and
then
any
other
questions
you
might
have
about
this
process.
H
I'm
happy
to
discuss
that
with
the
leads,
and
I'm
just
generally
available
for
any
questions
I'll
be
showing
up
to
all
the
meetings
and
helping
driving
long
longer
term
processes.
So
I'm
meeting
tim
pepper,
who
was
the
ea
for
119
this
afternoon
and
he's
going
to
be
handing
over
a
long
laundry
list
of
things
as
as
laurie
of
ongoing
changes
that
we
want
to
make
in
the
release
process.
H
So
if
you
have
anything,
feel
free
to
ask
I'm
here
to
help
help
you
all
get
through
the
120
release
and
excited
to
be
serving
with
you
all
so
back
to
you,
jeremy.
Thank
you.
A
Thank
you
lucky,
okay,
so
now
moving
on
this
is
the
point
in
the
meeting
where
we
would
normally
do
the
release,
lead,
update
I'll
pause
really
quickly
and
let
dan
and
nabaroon
introduce
themselves
they're
going
to
be
two
of
the
three
release
lead
shadows.
Savitha
will
be
the
third.
She
is
not
available
today,
so
she's
not
on
a
call
but
nabaroon
and
dan.
If
you
could
give
just
a
brief
intro
on.
I
I
think
I'll
go
first,
go
for
it,
yeah
hi
everyone,
so
this
is
nabarun.
I
have
been
involved
with
the
release
team.
Since
1.17
two
cycles
is
really
shadow,
then
last
cycle
is
sorry.
Two
cycles
is
enhancements,
shadow
and
then
one
cycle
is
announcements,
lead
and
right
now
shadowing
the
released,
indeed
so
glad
to
be
back
on
the
team
for
one
more
cycle
and
yeah,
we
will
end
the
year
with
the
bank.
A
Cool
that'll
be
awesome.
Dan
said
he
was
on
another
zoom,
so
he
may
not
be
able
to
to
chime
in
so
we
can
get
him
next
time
in
the
chat
kirsten
mentioned.
She
has
an
update
for
enhancements,
so
we
can
go
back
to
that
real
quickly
and
then
I'll
give
an
update
on
the
calendar,
and
then
we
can
move
on
to
have
have
laurie,
give
us
an
update
on
project
management
stuff.
So
take
it
away
kirsten.
B
Hi
I'm
in
kirsten
again.
I
basically
this
weekend
was
working
on
the
enhancements
tracking
sheet,
which
I'm
gonna
like
do
a
pr
for
the
for
the
link,
probably
today
or
tomorrow.
I
just
wanted
to
get
it
into
shape
right
now,
there's
like
155
enhancements
and
I
basically
went
through
all
I
made.
I
made
the
sheet.
I
went
through
all
of
them.
B
I
basically
pinged
all
of
them
and
I
kind
of
took
a
look
at
what
was
there
and
I
took
some
out
because
some
of
them
were
closed
and
I
also
made
some
notes
that,
like
we
do
have
a
case
of
like
a
lot
of
enhancements,
are
just
like
kind
of
blatantly
unresponsive
and
I'm
thinking
that
it
might
be
useful
to
add
that
as
one
of
the
drop
downs
for
the
we
have
the
enhancement
status
drop
down
and
it's
usually
like,
pending
inclusion
at
risk,
exception
required
deferred
removed
from
miles
to
attract
and
untracked.
B
But
I
know
that
we're
trying
to
optimize
the
enhancement
process
going
forward
and
I
thought
that
it
might
actually
be
a
good
idea
to
just
track
the
sort
of
non-responsive,
because
we
do
have
open
enhancements
issues
that
are
non-responsive
for
multiple
release
cycles
and
I
think,
like
maybe
indicating
that
somehow
will
potentially
help
us
like
optimizing
in
the
future
to
see
how
many
you
know
enhancements
are
just
unresponsive
once
the
the
release
cycle
kicks
off,
because
I
know
that
there's
a
lot
of
optimizations
there,
but
then
also
it
gives
us
a
better
way
to
track
things
that
they're
not
going
to
respond
they're
not
responding.
B
They
haven't
responded
for
four
cycles.
This
issue's
still
open.
It's
just
something
I
was
thinking
about
because
I
don't
want
like
shadows
to
keep
going
through
and
like
pinging
things
that
you
know
they've
already
been
pinged
like
eight
times
in
the
last
three
releases,
and
I
ping
them
again
and
they
don't
respond.
You
know
you
don't
really
have
to
like
ping
them
another
five
times
during
the
release
cycle.
Just
a
little
more,
I
guess,
granularity
in
the
status,
because
unresponsive
is
a
little
bit
different
than
just
untracked
like
untracked.
B
Is
somebody
saying
like
no
we're
not
doing
it
or
you
know
we're
yeah
we're
not
we're
not
working
on
this
for
1.20,
but.
B
B
Those
as
well-
and
it
should
be
really
good
for
the
shadows,
because
I
didn't-
I
just
thought
that
going
through
once
and
taking
a
look
at
all
the
enhancements
and
making
sure
they
were.
You
know
alive
and
kicking
before
the
shadows
had
to
come
and
look
at
them
would
give
us
a
good
head
start
to
the
release
cycle.
So
that's
my.
A
Update
awesome,
thank
you
and
that
will
lead
us
into
my
update,
so
the
calendar
for
the
release
has
been
merged
in
with
some
tentative
dates
like
these.
These
are
always
tentative
as
things
progress.
You
know
we
can
always
communicate
changes
if
they're
needed,
but
the
the
big
milestones
to
keep
track
of
for
120.
So
far
are
enhancement,
freeze
and
they'll,
be
the
first
milestone
so
kirsten
and
her
team
will
have
a
lot
of
work
ahead
of
them
for
the
next
four
weeks.
Enhancement
freeze
will
be
on
october.
A
A
A
If
you
have
any
questions
or
concerns
about
that
feel
free
to
reach
out
to
me
or
to
the
whole
release
team
in
sig
release,
and
we
can,
we
can
chat
about
those
release
dates.
A
We
have
a
six
scalability
update
in
here,
looks
like
there's
a
test,
infrared
issue.
We
can
circle
back
offline
with
that
with
that
I'll
turn
it
over
to
lori
lori.
Can
you
introduce
yourselves
for
anybody
that
hasn't
met
you
before
sure
and
then
go
into
your
update.
J
J
I
work
for
a
company
tin
travel,
so
you
can
imagine
how
that
goes
with
coronavirus,
and
so
we
went
to
half
time
and
that
gave
me
more
latitude
to
start
helping
out
this
community,
and
I
do
program
management
here,
which
is
essentially
trying
to
drive
delegation
alignment,
communication
and
collaboration
as
well
as
prioritization,
so
like
helping
this
team
prioritize
work,
build
more
sustainability
into
your
workflow,
also
get
more
control
over
your
workflow
and
establish
boundaries
between
release
cycle
and
with
other
cigs,
so
that
you
don't
take
on
too
many
other
things
work
actually
at
all.
J
So
with
that
last
point
in
mind,
I
wanted
to
share
some
information
with
this
group
about
a
effort
that
I
recently
did.
That
was
mainly
on
behalf
of
the
release
team,
but
also
the
ecosystem
generally,
and
that
was
to
find
out
which
cigs
are
currently
doing
future
health
checks.
So
the
feature
health
check
was
an
idea
that
actually
cygnode
has
created.
They
created
a
template
a
couple
weeks
ago,
where
they
did
their
own
feature.
J
So
I've
talked
to
all
sigs,
but
two
who
didn't
respond
and
the
data
is
in
the
link
that
you
can
click
on
in
the
agenda.
So
if
you
look
at
the
notes,
especially
if
you're
in
the
enhancement,
enhancements
team
or
also
the
release
lead,
shadows,
you'll
find
some
interesting
points
there.
There
are
some
sigs
that
already
have
some
of
their
kept
for
120
shares
written
down.
So
what
are
their
intentions
for
120
they've
had
meetings
to
figure
that
out.
They
have
documented
that
information
and
if
they
did,
then
they
usually
shared
it.
J
A
little
bit
of
proactive
planning,
so
if
that's
an
interest
to
you,
we
can
talk
more
about
it
online,
but
basically
the
goal
is
here
to
help
drive
responsiveness
from
the
cigs
and
then
by
also,
you
know,
having
them
thinking
about
process
as
part
of
their
of
their
everyday
and
engage
in
more
conversations
about
that,
but
also
transparency
for
for
all
of
us.
B
I
actually
have
a
question
if
there's
like,
because
there's
there's
two
kinds
of
enhancements
where,
like
the
sig,
has
planned
out
this
work
and
they're
like
this
is
what
we
get
behind.
But
then
there
are
always
like
other
people
who
are
pretty
consistently
like
opening
up
enhancements,
which
the
sig
may
or
may
not
have.
B
You
know
heard
about
or
vetted
or
given
the
thumbs
up,
and
I
guess
my
question
is
are
like
they
have
their
list
of
things
that
are
their
priorities,
but
are
they
also
like
committed
to
kind
of
regularly
going
through
their
sig
enhancement
issues
in
the
repo
and
like
basically
saying
like
no
we're
not
working
on
this?
This
relief.
J
That
would
be
a
great
follow-up
question
to
ask
them,
so
that
would
overlap
okay,
quite
a
lot
with
the
triaging
mechanisms.
So
a
lot
of
cigs
are
triaging
issues,
but
that's
quite
that's
rather
broad
like
how
are
they
triaging
bugs
and
just
other
things
that
come
through
from
potential
contributors
versus
the
caps
that
they
have
that
they
have
filed
and
that
others
have
filed
on
their
behalf?
We
didn't
go
into
detail,
but
if
that's
helpful
to
you,
then
we
we
should
talk
about
it.
A
Super
useful,
like
harrison
mentioned,
there's
a
ton
of
them
that
people
they
they
get
to
prove.
Obviously
these
things
have
to
be.
They
kept
steps
to
be
approved
by
the
sigs
to
merge
in
and
stuff,
but
then
we
get
to
like
the
code
review
or
the
code
implementation
phase
of
the
release,
and
then
we
get
to
code
freeze
and,
like
a
whole,
bunch
of
things
didn't
get
reviewed
or
they
didn't
get
merged
just
because
there
wasn't
a
lot
of
back
bandwidth
and
priority
from
the
sigs.
D
A
Was
approved
and
merged
and
was
implementable
for
several
releases,
but
then
we
would
get
to
code
freeze
and
like
oh,
we
didn't
quite
get
the
review.
We
didn't
quite
get
the
review
done
and
then
like
after
we
poked,
because
it
was
like
the
third
or
fourth
time
that
it
was
gonna.
Miss
then
like
oh
yeah.
Actually
this
isn't
something
we're
prioritizing
right
now.
B
Yeah,
I
mean
part
of
the
caps.
Are
that
like
keep
like
the
kept.yaml
file,
like
people
have
to
specify
the
state
like
provisional
or
implementable,
and
then
they
also
specify
the
milestone.
So
I
think
that
there's
an
expectation
once
the
cap
is
actually
like
merged
as
implementable
with
a
milestone.
The
cap
holder
does
expect
that
they're
going
to
be
able
to
do
the
work
in
the
milestone
that
they
specified.
B
You
know,
and
maybe
this
means
that
they
should
be
using
provisional
more
and
not
letting
people
merge
with
a
milestone
as
much,
but
there's
definitely
that
like,
because
it
should
be
pretty
straightforward
like
once,
once
all
once
the
enhancement
cutoff
is
there.
I
should
expect
that
most
of
the
enhancements,
barring
something
happening
to
the
enhancements
owner
get
merged.
B
But
there's
this
other
thing
like
jeremy
was
saying
that
happens
where
they
think
that
they're
going
to
get
it
in
because
it's
been
approved
for
1.29
or
1.85
or
whatever,
and
then
there's
nobody
who's
going
to
review
it
and
actually
let
them
merge,
and
I
think
that
that's
like
the
tension,
so
maybe
provisional
more
often,
maybe
after
the
enhancements
are
all
you
know,
accepted
we
go
through
and
we're
like
hey.
These
are
all
of
the
enhancements
that
you've
approved
for
this
milestone.
D
J
You
want
to
we
want,
you
know
we
want
to
be
proactive
and
getting
ahead
of
this
problem
that
we
know
already
exists,
so
I'm
open
to
having
a
conversation
with
you
person,
and
maybe
everyone
wants
to
join
jeremy
with
your
expertise
and
past
experience.
I
would
just
keep
it.
You
know
whoever
else
might
want
to
draw
join.
That
wants
to
actually
work
on
this
because
it'll
it'll
be
a
little
difficult,
because
we're
talking
about
habit,
change
and
habit
formation.
D
J
A
I
think
that
would
be
great
thanks,
lori
for
that
update
and
kristen
for
that
input.
A
Super
super
helpful,
okay.
Moving
on
to
open
discussion
items
generally
in
this
part
of
the
release
meeting.
We
we
open
it
up.
You
can
add
any
topics
you
want
into
the
the
open
discussion
and
we
can
discuss
them.
I
added
one
here
to
discuss
time
zones
so
typically,
we've
not
had
very
time
zone
friendly
meetings
for
people
that
are
outside
of
the
u.s,
like
it's
getting
late
in
the
day
for
people
in
europe,
it's
getting
very,
very
late
in
the
day
for
people
in
india
and
it's
even
worse
for
anybody.
A
That's
east
of
that,
so
we've
discussed
having
in
the
past
like
how
we
move
towards
more
asynchronous
release,
team
actions
and
reporting
things
like
that.
I
think
lori
and
maybe
lockheed
and
david
mckay
from
a
previous
release,
are
going
to
start
looking
at
some
of
that
a
little
bit
more
in
depth.
But
we
thought
as
part
of
a
like,
a
starting
effort
for
that.
Maybe
we
could
think
about
having
two
release
meetings,
one
that
would
be
more
friendly
for
everybody.
A
A
In
the
u.s,
it's
going
to
exclude
people
if
we
go
too
late
in
the
u.s,
it's
going
to
exclude
people
that
are
not
in
the
u.s.
So
it's
really
hard,
I
think,
to
hit
all
of
the
the
balancing
points
of
the
various
time
zones,
I'm
just
having
worked
on
a
team
at
my
day,
job,
that's
in
lots
of
lots
of
geos
like
it's
really
hard
to
to
hit
those
things
for
people.
A
So
what
does
everybody
think
about
having
you
know,
two
release
meetings
and
then
having
some
sort
of
asynchronous
coordination
between
them
to
hand
off
if
there
are
any
action
items
or
if
there
are
any
big
reporting
items
that
we
need
to
do,
I
think,
generally,
as
part
of
this
release,
we
want
to
do
more
communication
to
the
community
around
like
when
release
dates
are
going
to
change
and
stuff,
but
also
like
when
there
are
problems
with
ci
signal,
let's
report
those
things
out
and
and
do
a
little
bit
better
job
of
getting
getting
things
happening,
and
I
think
that
all
those
things
need
to
be
asynchronous
like
those
don't
need
to
occur
in
in
the
release
team
meetings.
A
So
I
just
wanted
to
open
it
up
to
see
what
people
think
are
there
people
that
would
be
in
favor
of
doing
a
release
meeting
in
the
non-us
time
and
then
coordinating
with
us
to
to
hand
it
off
I'll
open
it
up
there.
If
anybody
has
any
feedback
or
any
thoughts
around
that.
A
General
question:
are
you
running
the
meeting
in
apac
time
or
someone
else,
so
it
will
probably
be
somebody
else.
I
would
look
to
maybe
nabaroon,
since
he
is
in
that
time
zone.
Do
you
feel,
like
you
could
take
on
running
an
asia-pacific
central
centric
meeting.
I
Yep
we
could
so
we
already
have
a
sig
contributor
experience
effect
coordinators
meeting,
which
actually
happens
at
5
utc,
which
actually
was
suited
because
it
could
cover
new
zealand
time
as
well,
which
was
for
them.
It
would
be
like
evening-ish
and
for
europe
slash
middle
east.
It
would
be
like
early
morning-ish
like
six
seven,
something
like
that.
I
So
that
was
tuned
so
that
the
eastern
hemisphere
can
at
least
attend
those
meetings
and
have
epic
centric
discussions.
I
think
we
can
try
to
pull
it
off.
The
only
attention
I
have
right
now
is
that
we
have
not
traditionally
been
very
async
right,
so.
I
A
cultural
change
inside
the
team
that
we
need
to
bring
in
how
do
we
communicate
more
effectively,
so
we
can
drive
a
meeting,
that's
completely
possible,
just
that
we
need
to
figure
out
the
communication
part
like
how
does
the
handover
occur?
How
do
we
not
discuss
duplicate
items
on
both
the
meetings?
I
How
are
the
thoughts
being
considered
from
both
both
sets
of
people?
Obviously,
in
this
time
I
can
attend
both
the
meetings
at
the
current
state
of
the
meeting.
It's
like
10
30
see
it's
11
p.m.
For
me,
right
now
so
yeah
to
answer
your
question
shortly,
I
can
drive
the
media.
A
Yeah
I
mean
obviously
11
is
not
ideal
for
anybody
to
be
dedicating
time
expecting
the
shadows
to
do.
That
is
also
rough.
I
think
so.
I
think
personally,
I
think
it
would
be
good
if
we
could
do
another
meeting
that
would
be
more
friendly
and
and
handle
some
of
that
asynchronous
communication.
I
think
it
also
might
be
telling
an
instructive
for
us
to
start
laying
down
some
more
just
general.
A
A
You
know
it's
not
the
end
of
the
world.
If
we
we
have
to
make
some
changes,
so
I
think
one
thing
we
can
do
is
send
out
a
doodle
to
to
kind
of
gather
times
for
both
the
u.s
one.
Is
this
a
good
time
or
is
it
not
a
good
time
and
then
for
the
asia
pacific
centric
time?
I
can
send
one
out
one
of
those
out
today,
unless
anybody
has
any
other
concerns
or
thoughts.
E
I
have
one
concern:
if
it's
just
you,
jeremy
and
nebu
running
those
meetings,
like
I'm
worried
that
you
know
if
nevermind
is
out
sick
one
day
or
something
like
who's.
Gonna
fill
that
role
just
something
to
think
about.
I
get
I
guess,
but
just
in
general
I
don't
have
any
problem
with
with
that.
I
think
we
should
try
it
out
to
see
how
it
works,
but
go
ahead.
Lori
yeah!
No
thanks!
I
I.
I
So
the
current
team
stands
as
it
like.
The
release
lead
is
in
u.s,
centric
time
zone.
Two
of
the
three
shadows
are
in
eurocentric
time
zone
and
one
shadow
is
in
east
hemisphere,
centric
time
zone.
So
do
we
delegate
so
in
in
a
scenario
where
I
am
not
able
to
attend
the
meeting?
For
some
reason,
do
we
delegate
it
to
a
shadow
of
other
teams
or
like.
A
Yeah,
I
think
we
can
once
we
select
the
shadows,
we'll
have
a
better
idea
of
what
the
team
makeup
is
going
to
look
like,
and
I
think
we
can
identify
people
to
to
be
the
backups
to
run
the
meetings
once
we've
identified
who's
going
to
be
on
the
shadows
like
if,
if
we
end
up
not
having
any
shadows
that
are
in
that
time
zone,
then
maybe
this
doesn't
make
a
lot
of
sense.
Like
looking
at
the
numbers,
I
think
we'll
end
up
with
some
that
are
in
that
time
zone.
We
can.
A
We
can
work
on
making
sure
that
there's
coverage
I
mean,
I
think,
to
laurie's
point.
This
is
a
great
way
of
just
leveling
everybody
up,
and
it's
not
it's
not
traditionally
like
the
role
of
like
the
enhancements
shadows
or
the
bug
tree
eye
shadows
to
run
these
meetings.
But
you
know
it
is
part
of
their
remit
to
do
a
part
of
the
meeting,
so
we
can
always.
A
A
D
A
We,
I
think
we
get
to
the
point
where
there
are
only
pieces
that
may
need
to
have
active
discussions,
and
we
can
can
think
about
how
we
restructure,
how
the
meetings
run.
B
B
And
maybe
the
docs
there's
like
overlap
there,
we
use
the
same
sheet.
They're
gonna
get
the
docs
for
the
enhancements
that
we're
working
on.
So
I
would
just
keep
in
mind
like
the
complementariness
of
who
absolutely
has
to
be
in
a
meeting
and
even
though
shadows
can
be
in
the
meeting,
sometimes
the
lead
might
need
to
be
in
the
meeting
as
well,
but
I
I
think
like
for
leads
it's
like
who
is
the
caught
like?
Is
there
a
group
that
you
usually
talk
to?
B
I
might
have
to
try
to
schedule
a
meeting
with
you,
and
maybe
that's
also
something
like
talking
to
each
other
yeah,
more
yeah.
J
J
You
know
the
time
zone
specific
the
two
different
meetings
for
the
different
time
zones
like
having
more
people
in
both
of
those
meetings
just
being
able
to
run
a
meeting
and
know
what
to
do
and
know
how
to
like,
facilitate
conversation
about
follow-up
and
things
of
this
nature
like
it's.
It's
empowering
to
have
more
people
in
the
group
being
able
to
just
run
the
meetings,
because
this
means
that
you
get
practice
for
being
a
release,
lead
at
some
point
and
and
also
it
just
it's
a
good
exercise
and
delegation
for
everybody.
J
So
there's
that
and
then
the
other
thing
is
that
we
were
we,
we
have
a
lease
leads
sink
on
mondays,
and
so
we
had.
We
had
the
conversation
about
like
making
the
release
team
more
proactive
and
less
reactive
and
reporting
things.
So
you
know
there's
a
question
of
like
what
do
we
actually
have
to
communicate
in
a
meeting
versus
what
do
we
just
have
to
make
sure
we
communicate
and
maybe
a
meeting
itself
isn't
the
right
framework
for
like
a
status
update,
but
something
like
kirsten.
J
What
you're
saying
a
discussion
with
enhancements
and
docs
about
complex
matters
that
might
need
a
meeting,
but
then
again
does
it
need
everybody
involved
in
this
group.
You
know,
maybe
you
just
have
a
breakout
or
you
structure
that
or
you
time
box
some
time
in
advance
during
this
meeting
for
your
conversation
and
then
people
can
drop
off
if
they
don't
want
to
join.
So
it's
it's
some
tricks
like
that.
You
know,
but.
B
Well
at
work,
we
have
like
meetings
that
are
on
the
calendar
and
like
for
those
meetings,
we
have
like
an
agenda
that
we
have
open
ahead
of
time
and
yeah.
I
mean
that
that
could
be
what
we
also
use
a
little
bit
more
than
just
like
hey.
I
have
this
many
bugs
or
this
many.
This
is
where.
J
Right
now,
this
is
a
great
point,
like
the
only
the
only
thing
we'll
have
to
figure
out
through
this
handoff
process
is
making
sure
that
that
agenda
gets
looked
at
by
somebody
in
advance.
You
know
whether,
whether
it's
the
lead,
who
can
or
can't
join
a
meeting
or
someone
else,
who's
delegated
that
task
of
making
sure
that
the
agenda
has
things
in
it
and
isn't
blank,
but
we
can
see
how
that
goes.
C
So
if
I
can
make
a
suggestion,
one
of
the
things
that
I'd
like
to
see
happen
more
on
the
project
in
relation
to
dealing
with
asynchronicity
is
I'm
coming
from
a
ci
signal.
Point
of
view
here
from
a
task
point
of
view.
C
I
see
the
the
world
wideness
as
an
advantage
generally,
insofar
as
that
the
people
in
asia
pacific
and
get
first
by
the
cherry
when
it
comes
to
finding
flakes
and
reporting
them,
and
that
then
that,
basically
we
there's
a
follow
the
sun
hunt
for
flakes
and
essentially
in
terms
of
capturing
the
activity
our
work
is,
is
github
issue
based
and
what
I,
what
I
want
to
be
able
to
see
from
from
the
point
of
view
of
hand
over
what
I
want
to
be
able
to
see
is
leveraging
of
project
boards
in
order
to
go
okay
right.
C
Let's
look
at
let's
walk
the
board
here,
so
so
my
expectation
is,
is
that
from
the
people
who
are
up
first,
when
when
they
log
issues
that
I
that
I,
that
I
see
those
updates
on
the
board
and
that
I
then
are
in
a
then
I'm
in
a
position
to
walk
that
board
and
log
issues
myself
and
then
hand
that
over
to
the
us
as
they're
getting
up,
and
so
I'd
like
to
see
so
rather
than
it-
and
this
kind
of
speaks
to
using
a
meeting
for
what
a
meeting
is
good
for
and
and
and
and
that
is
having
a
chat
about
something-
that's
onerous
tricky
or
we
need
to
get
some
heads
together
and
fix
a
problem.
D
A
Yeah,
I
I
totally
agree
with
that,
and
I
think
that
kind
of
naturally
leads
into
our
next
discussion
item.
If
we
want
to
move
on,
lori
has
asked:
are
there
any
objections
to
using
the
project
board,
walking
the
board,
and
we
actually
used
to
do
this
in
the
release
meetings?
I
don't
think
we
did
it
much
right
at
all
in
119,
but
in
previous
releases
I
know
we
we
would
walk
the
board,
which
is
why
there's
a
project
board
link
at
the
end.
A
I
definitely
think
that
it
would
be
good
to
do
that
more
proactively.
I
think
one
of
the
things
we
also
took
away
from
the
119
retro
was
that
there
were
some
things
that
would
get
reported
in
these
meetings
and
needed
to
be
actioned
and
like
carried
forward,
and
we
didn't
really
do
that
all
the
time
so
kind
of
along
those
lines.
I've
added
a
an
action
items
section
at
the
top
of
this
document.
So
when
there
are
things
that
arise
in
this
meeting
that
you
know
that
like
would
be
good
to
status
and
follow
through.
A
I
think
we
should
add
them
to
the
project
board
and
then
have
a
record
of
like
what
issue
on
the
project
board.
Is
that
decision
and
kind
of
follow
through
and
the
meetings
to
make
sure
we
we
get
it
resolved
and
not
we
don't
say
hey.
This
is
a
problem
and
then
it
kind
of
falls
off.
J
I
have
a
iteration
on
that,
which
would
be
that
when
we
note
an
item
that
needs
to
have
follow-up,
that
an
owner
pops
up
during
the
meeting
and
makes
the
github
issue
yeah
yeah
the.
A
J
But
if
we're
using
the
project
board,
we
can
also
see
yeah.
We
don't
need
the
list.
We'd
only
need
it
for
issues
that
don't
get
an
owner,
so
that
would
help
with
the
tracking,
because
the
list
we
had
this,
we
had
a
similar
conversation
near
the
end
of
last
cycle
where
it
was
like
yeah.
If
we
have
a
list
of
things,
then
how
do
we
see
the
updates
easily?
You
know
with
the
board,
you
can
do
it.
J
D
C
C
One
of
the
things
that
that
I'm
seeking
to
do
this
time
around
is
to
build
on
work
that
I
don't
know
elena's
surname
off
the
top
of
my
head.
But
but
a
previously,
I
signaled
shadow
did
some
work
on
reporting.
What
issues
were
on
this?
C
The
the
flakes
reporting
board
and
the
ci
signal
board,
and
and
and
as
I
look
at
that
code
now
with
the
review
of
automating
the
weekly
report
and
effectively
making
it
an
asynchronous
dashboard
and
there's
a
couple
of
there's
a
couple
of
nudges
that
I
want
to
be
able
to
put
into
that
report
in
relation
to
grouping
issues
by
sig,
etc,
etc
and
grouping
issues
by
status,
whether
they're,
just
reported
or
reported
and
triaged.
Or
you
know
this
fixed
emotion
or
whatever.
C
So
so,
if
anyone's
interested
in
that
sort
of
level
of
automation,
I
think
possibly,
I
should
log
in
as
you
to
kind
of
track
that
work
actually
and
yeah.
Let's
just
start
doing
it
now,.
J
I
mean
a
lot
of
the
items
on
the
project
board
in
y119
were
pretty.
Some
of
them
are
pretty
large
and
long-term
issues
and
with
the
release
team,
you're
you're
talking
with
the
tighter
talking
about
a
tighter
cycle,
so
I
think
for
the
board
to
make
any
sense.
We
would
need
to
think
about
what
do
we
want
to
do
with
those
longer
term
issues
that
affect
the
release
team
specifically,
and
what
about
all
these
little
other
things
that
come
up,
that
we
should
just
track.
J
M
J
J
Yeah,
nobody
drops
anything
here.
We
would
just
push
you
know
that
might
be.
That
was
what
I
was
thinking.
They
would
go
to
sig
release,
but
let's
see,
if
that's
actually
the
most
reasonable
approach,
it
might
be
that
they
would
just
stick
in
a
backlog
column
for
the
release
team,
but
there'd
be
a
lot
of
other
smaller
items
that
will
move
faster
through
through
the
weeks
that
we
would
mainly
keep
our
eyes
on.
K
C
If
we
can
do
like
what
we
did
on
what
the
testing
protein
did
for
us
on
ci
signal,
which
was
to
to
formulate
policy
change
and
have
umbrella
issues
and
have
some
tasks
hanging
off
them,
if
we
can
achieve
that,
then
then
we
can
capture
that
sort
of
long-term
goaliness
of
of
big
projects.
But
if
we
can
do
a
breakdown,
then
we
can
say:
okay,
let's
bite
some
things
off
and
get
things
done
with
this
cycle.
J
I
think
what
just
like
think
about
what
what
could
go
wrong
if
we
push
those
longer
term
release
term
release
team
items
to
the
sig
release
board,
do
we
can
we
think
of
anything?
Any
reason?
Why
not
why
we
should
not
do
that
and
then
maybe
I'll?
Oh,
I
can
reach
out
to
you
all
again
on
the
channels
to
say
like
have
you
thought
of
anything
and
you
can
post
there
as
a
reminder.
H
A
Yeah,
so
I
think
those
longer
term
things
might
make
sense
to
land
there
with
that,
as
the
the
owner.
J
B
B
If
you
just
box
it
onto
the
team
specifically,
then
it
kind
of
feels
like
well
it's
over.
So
I
guess
that
somebody
else
is
saying
and
it
feels
a
little
weirder,
so
it's
like
yeah
having
them
trapped
in
both
places
could
also
let
people
like
continue
to
maybe
make
the
improvements
that
they
didn't
have
the
time
or
capacity
to
do
in
the
actual
release
cycle.
A
Cool,
I
think
that
was
a
really
productive.
First
meeting
lots
of
good
discussion
stuff
anything
else
we
want
to
discuss
on
using
the
project
boards.
We
can
start
doing
that
next
week.
A
We
will
start
that
next
week.
Last
thing
really,
the
the
retro
document
is
linked
here.
So
as
we
go
through
the
the
release
cycle,
when
things
pop
up
that
you
think
we're
doing
really
well
for
things
that
we're
not
doing
so
well,
please
add
them
to
the
retro
so
that
we
don't
forget
them
and
we
have
them
tracked.
You
know,
I
think
we
had
a.
D
A
Of
good
stuff
on
the
retro
for
119-
and
I
think
part
of
that
was
people
added
them
as
we
were
encountering
difficulties
or
we
didn't
have
a
lot
of
like
what
went
well
in
the
119
retro.
So
if
you
notice
things
that
are
going
well,
please
add
them
so
that
we
have.
We
have
happy
things
to
talk
about
as
well.
At
the
end
of
the
cycle.
A
All
right
with
that
I'll
open
it
up
any
other
topics
that
anyone
would
like
to
to
bring
up
or
discuss.
That's
not
on
the
agenda
now,
if
not
I'll,
give
you
10
minutes
of
your
time
back
and
if
you
oh
go
ahead.
M
Yeah,
can
I
just
ask
a
question:
that's
a
good
question.
I
signed
up
for
the
120
channel
and
I'm
kind
of
curious
about
like
the
shadow
elections,
so
that
will
happen
like
you
recently
well
two
weeks
I
assume
and
like
it
will
send
out
an
email
for
confirmation.
Is
that
correct.
A
That's
correct
yeah!
So
today
the
the
application
closed
on
friday
and
today
lockheed
sent
out
a
list
of
all
the
applicants
to
the
different
leads
so
rob,
and
anna
and
kirsten
and
james
and
joseph
and
and
vlad
will
be
going
through
that
right
now
like
starting
this
week
starting
today
and
ideally
we'll
try
to
have
all
of
the
selections
done
by
the
end
of
the
week
and
notify
everybody
so
that
we
can
get
everybody
on
board
for
next
week.
A
Thanks
for
applying
happy
to
have
everybody
join
us
and
be
interested
in
the
release
team.
Thank
you.
A
All
right
with
that
I'll
give
you
back
10
minutes
of
your
time
and
everybody
have
a
fantastic
monday,
whatever's
left
of
it,
not
broon.