►
From YouTube: Kubernetes 1.20 Release Team Meeting 20200921
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
Welcome
everyone
to
the
kubernetes
120
release
team
meeting
for
week.
Number
two
today
is
of
course
september
21st.
This
meeting
is
a
kubernetes
release,
a
meeting
that
falls
under
the
kubernetes
sig
release
umbrella.
So
this
meeting
will
be
covered
by
the
kubernetes
code
of
conduct,
which
can
be
boiled
down
to
be
excellent
to
one
another.
This
meeting
will
also
be
recorded
obviously
and
will
be
available
on
youtube.
B
Hi,
so
this
is
kirsten,
I'm
the
enhancements
lead.
I
I
said
that
we
were
green
right
now.
I
pinged
all
of
the
enhancements,
maybe
a
week
ago
or
two
weeks
ago,
and
the
response
rate
has
been
pretty
good.
We
have,
I
think,
at
this
point,
26
enhancements
that
are
tracked
and
I
feel
pretty
good
about
the
momentum
on
most
of
those.
The
rest
were
still
waiting,
but
I
think
that
this
is
like
a
pretty
good
sustainable
rate
of
enhancements.
B
B
But
I
think,
like
week,
two
we're
actually
doing
really
well
and
three
of
my
four
shadows
have
confirmed,
and
I
think
that
they're
here
and
I
think
we're
gonna-
try
to
schedule
a
meeting
this
week
I'll
send
out
a
doodle
to
all
of
them
just
to
pick
a
good
time,
because
I'm
hoping
that
this
release,
like
we
do
a
little
bit
less
just
pinging
the
world
and
focus
a
little
bit
more
on
the
people
who
are
actually
working
on
their
enhancements
and
making
sure
that
they
meet
all
of
the
enhancements
criteria.
B
So
getting
the
jump
start
a
couple
weeks
ago,
I
think
was
good
for
that
as
well
and
not
not
like
pinging
unresponsive
enhancements
like
20
times
so
I'll
also
be
sending
out
just
an
email
to
probably
kdev
or
tvd
email
list
about
the
enhancements
freeze
as
well
and
yeah.
I'm
not
sure
if
the
shadows
should
introduce
themselves
or
if
we're
just
going
to
go
to
the
next
group
or
not
jeremy
yeah.
A
Let's
go
ahead
and
we
can
have
people
introduce
themselves.
So,
just
as
a
general
note,
we
have
mostly
finalized
shadow
selection.
I
think
we'll
be
sending
out
an
email
today
to
everybody
that
wasn't
selected
just
for
for
reference,
but
we'll
start
we'll
be
onboarding
everybody
starting
today.
So
if
you're
in
this
meeting
go
ahead
and
introduce
yourself.
C
Hi
everyone,
my
name,
is
jeremy
morris,
I'm
a
software
engineer
for
digitalocean
and
I've
been
selected
as
a
shadow
for
the
enhancements
team.
So
this
will
be
my
first
time
doing
it
based
out
of
princeton
new
jersey.
D
Yeah
hi
everyone,
I'm
kenara.
I
work
as
a
software
engineer
at
rancho
labs,
I'm
from
cupertino,
and
this
is
also
my
first
time
working
in
any
of
the
six.
So
I'm
pretty.
E
Yeah
hi
everyone,
my
name
is
kendall
rhoden
and
I'm
also
going
to
be
on
the
enhancements
team.
As
a
shadow
last
release,
I
was
actually
on
the
communications
team,
so
super
excited
to
have
a
little
bit
of
an
idea
of
what's
going
on
and
hopefully
I'll
be
able
to
contribute
a
bit
more
this
time
around
so
happy
to
see
everyone
again.
F
F
The
the
manual
reports
today
and
I've
been
working
on
automating
the
report-
and
I
am
not
quite
ready
for
demo
but
essentially
where
I
have
that
automation
is
that
it's
outputting,
what's
nearly
an
org
mode
style
output
and
I
think
by
next
week
we'll
be
picking
formats
and
recording
point
in
time
snapshots
of
the
state
of
ci
signal.
So
at
the
moment
I
think
I
started
to
update.
F
I
think
I
was
updating
the
template
and
and
we've
seven
flaky
jobs
and
master
blocking
and
I'll
put
those
in
the
right
place
and
we're
in
the
middle
of
dropping
in
the
master
and
forming
reports.
So
we
don't
have
a
full
report
this
week,
but
this
should
be
better
next
week.
A
Great,
if
any
of
your
shadows
are
on
the
call,
do
you
want
to
have
them
introduce
themselves.
G
Hi
yeah,
my
name
is
joyce.
This
is
my
first
time
acting
as
a
shadow
for
the
ci
signal
and
I'm
currently
in
my
last
year
of
computer
science
at
the
university
of
waterloo.
F
H
H
glad
to
be
working
with
you
all
again
and
looking
forward
to
an
amazing
release.
This
time.
F
Yeah
thanks
so
much
for
stepping
up
and
I'm
doing
that
report
manually
and
sam.
That
was
fantastic.
I
really
yeah.
I
really
appreciated
that
today,
so
I'll
be
happy
to
to
demo
the
automatic
report
this
week
and
I'll
be
pushing
that
up,
and
I
have
to
give
a
shout
out
to
to
elena
varkakova
who
worked
on
this
report
and
this
time
last
year,
so
we've
resurrected
her
work
on
that
and
and
basically
what
I
did
today
was
updated.
F
Google
goal
line,
github
api
module
and
and
I'm
kind
of
hitting
up
against
learning,
about
rate
limits
and
and
thinking
about
making
my
own
proxy,
but
I
might
talk
to
people
and
test
info
about
that
and
yeah.
Hopefully
we'll
have
that
automated
for
next
week.
A
A
Okay
next
I'll
hand
it
over
to
vlad
for
bug,
triage.
I
Hey
so
we
are
green,
we
don't
have
much
to
do
right
now.
We
usually
step
in
a
little
bit
later
in
the
cycle.
I
J
I
Hey,
thank
you
max.
K
Everyone
I'm
max,
I'm
basically
a
cloud
native
engineer,
or
I
have
a
small
team
to
manage.
Also
I'm
working
on
small
consulting
company
currently
called
storm
reply.
It's
actually
my
fourth
round
on
the
release
team
and
I
was
in
the
previous
release.
Comms
lead
and
now
joined
back
as
the
shadow
for
the
buck.
Triash.
L
I
M
I
Thank
you.
We
have
one
more
shadow
who
could
make
it
today
due
to
doctor's
appointment,
but
over
to
you,
jeremy,.
A
N
Hey
everyone,
I'm
anna,
I'm
the
docs
lead
for
this
release.
I
don't,
I
think,
we're
green.
I
don't
have
any
like
updates
for
this
week.
I
do,
however,
want
to
get
with
kristen
to
make
sure
that
I
get
access
to
all
the
tracking
sheets
and
all
my
shadows
as
well
so
I'll
be
doing
that
this
week
and
actually
all
my
shadows
are
on
this
call.
So
I
really
want
to
introduce
them
to
everyone
here.
So
I'm
going
to
start
off
with
some
top
some
tochi.
O
Yeah,
that's:
okay,
hello,
everyone!
My
name
is
sumtochi,
and
this
is
my
first
time
on
the
release.
Docs
team.
This
is
my
first
time
as
a
shadow
on
the
release
team
and
I
just
finished
interning,
my
g-shock
and
google
sum
of
code
internship
with
kubernetes,
so
yeah,
I'm
pretty
much
excited
to
be
here.
It's
nice
to
meet
you.
Thank
you.
N
You
and
ray.
P
Hello,
my
name
is
ray.
This
is
my
third
release
team.
I
was
on
118
and
on
119
for
release
notes.
So
this
is
my
first
time
on
docs
super
excited
to
be
on
the
docs
team
and
yeah
looking
forward
to
it.
Q
Yes,
hello,
everyone,
so
my
name
is
leslie.
This
is
my
first
time
in
the
process
of
cabinet's
release
and
especially
for
this
team,
so
I'm
very
glad
to
participate
to
that
effort,
and
I'm
kind
of
stressed
too
so.
Currently,
I'm
working
on
cloud
architecture
for
autonomous
vehicles
and
I'm
freelance,
that's
it.
Thank
you.
R
Hello,
this
is
my
third
zig
release
tour
of
duty-
I
guess
with
I
worked
before-
with
anna
and
jeremy,
on
enhancements
for
117
and
prior
to
that
release,
notes
with
sasha.
So
I'm
really
excited
about
120
and
working
with
you
all
again-
and
I
am
a
software
engineer
at
zillow
group
thanks.
N
Welcome
back
kristen,
that's
it
for
dogs.
A
Cool,
thank
you
we'll
make
sure
that
everybody
gets
access
to
the
the
tracking
sheet
this
week
and
just
in
general,
we'll
do
that
on
boarding
for
all
the
shadows
as
we
go
through
the
week.
Next,
we'll
have
james
with
release,
notes.
S
S
Outside
of
this,
I
work
as
a
solutions
engineer
for
jetstack,
which
is
a
uk-based
kind
of
professional
services,
company
focused
on
kubernetes
and
cloud
native.
So
I
do
this
all
day
every
day.
In
terms
of
how
we
are
doing,
I
can
say
this
is
green.
We
don't
generate
release,
notes
for
the
alpha
zero
release,
so
we're
just
waiting
on
one
twenty
zero
alpha
one
tomorrow
to
start
generating
those.
We
do
have
a
new
process
this
time
around
that
I
believe,
is
currently
in
flight.
S
I
need
to
catch
up
with
adolfo
to
double
check
exactly
whether
we're
using
the
new
process
of
the
old
process
yet
and
kind
of
helped
make
sure
we
get
some
documentation
merged
for
that.
S
Beyond
that,
we
have
confirmed
all
four
shadows
for
release
notes,
and
at
least
a
few
of
them
are
on
this
call,
so
I'll
ask
them
to
just
use
themselves.
I
can
only
apologize
if
I
get
names
wrong.
First
of
all,
we
have
wilson,
who
I
don't
think
he's
actually
managed
to
make
this
call.
I
think
he
had
a
conflict
yeah
but
wilson
from
release
notes
last
time
as
well.
I'm
sure
he
can
introduce
himself
in
the
next
meeting.
S
Then
we
have
celeste.
I
believe
he's
here.
T
Hi
yeah-
I
am
indeed
here-
I'm
celeste.
I
actually
work
with
the
cncf
directly
as
a
technical
writer
on
kubernetes
and
other
cncf
projects.
This
is
my
first
release
team
shadowing
for
release
notes,
but
also
very
likely
also
going
to
help
out
docs.
So
where
you
can
usually
find
me
is
that
in
sig,
docs.
C
Yeah,
of
course,
hi
everyone.
My
name
is
jackie.
I'm
a
software
engineer
for
caseware
based
out
of
toronto,
canada.
It's
my
first
shadow
experience
with
this
release.
I'm
very
excited
to
work
with
every
one
of
you.
Thank
you.
S
U
Hello
yeah,
my
name
is
wilson.
I
was
a
shadow
for
119
and
I'm
back
for
shadowing
120
again.
S
Cool
then
yeah
unless
sonia
is
on
the
call,
which
I
believe
she
is
then
that's
it
for
release,
notes.
A
Awesome
thank
you
and
welcome
everybody
on
the
release.
Dance
team
next,
we'll
have
the
last
of
our
little
sub
teams
and
that's
comms,
so
joseph
take
it
away.
A
Everybody
I'm
joseph
sandoval
and
I'm
glad
to
be
back
on
the
release
team.
That
was
part
of
the
119
team
with
comms
and
now
here
I
am
when
120
as
the
comms
lead,
so
really
grateful.
Salt
max
is
back.
So
thanks
max
for
all
your
help
so
appreciate
all
the
feedback
you
left
behind,
as
well
as
like
the
work
that
you
did.
I
work
currently
with
adobe,
I'm
managing
sre
teams
that
are
building
kubernetes
platforms,
cloud
native
toolings
and
all
that
fun
and
being
able
to
you
know
enjoy
this
journey.
A
So
as
far
as
like
our
shadows,
we're
all
covered
there
and
we
have
a
team
that
is
split.
So
we
got
half
the
team,
that's
going
to
be
in
ist
and
then
part
of
the
team
is
in
esd,
which
is
pretty
much
exactly
like
what
my
work
situation
is.
So
here
I
am
on
the
west
coast
and
probably
means
I'm
going
to
be
working
around
the
clock
as
I
you
normally
do.
So
this
works
perfectly.
A
So
what
I'll
do
is
I
notice
a
few
of
them
are
on
the
call
and
I'll
let
them
introduce
themselves,
starting
with,
I
think,
divya.
I
think
I
saw
her
there.
V
Yeah
hi
everyone,
I'm
glad
to
be
back
in
the
release.
1.20.
I
was
a
part
of
the
docs
team
on
1.19
excited
to
learn
new
things
about
the
release
from
different
areas.
So,
yes,
okay,.
W
Hello,
everyone.
Chris
short,
I
work
over
at
red
hat.
This
is
my
first
official
release
team
responsibilities,
even
though
I've
run
retros
and
such
in
the
past
for
folks
very
happy
to
be
here
very
happy
to
shadow
and
just
see
how
this
whole
process
works.
Also,
one
of
the
key
roles
that
I
want
to
play
is
working
with
the
kate's
upstream
marketing
team
to
kind
of
help
glue
some
of
those
pieces
together
to
make
some
more
automated
marketing-
and
you
know,
communications
type
functions
happen
in
the
background.
X
Hi,
my
name
is
tony
gosselin.
I
also
work
with
adobe.
I
actually
work
under
joe
over
at
the
advertising
club,
bu
and
yeah
this.
This
is
my
first
release,
first
sig
to
be
involved
in,
and
I'm
excited
to
be
here.
A
And
I
think
that's
it-
we
have
one
another
buddy.
I
don't
believe
he
is
here
so
I'll
hand
it
back
cool.
Thank
you
so
much
any
questions
for
comms
before
we
move
on
all
right.
Next
super
exciting
marco
will
be
telling
us
about
the
branch,
management
updates
and,
first
we'll
say,
congratulations
to
marco,
on
his
promotion
to
a
release
manager.
Y
Okay,
folks,
so
if
jeremy
said
I
have
been
promoted
to
a
release
manager
and
for
this
recycle,
I
will
be
taking
over
the
role
that
carlos
did
for
the
pass
release
cycles.
So
I
will
be
taking
care
of
updates
and
that
will
be
the
liaison
between
the
release,
engineering
team
and
the
release
team.
So
if
you
have
any
questions
or
any
stuff
feel
free
to
ping
me
and
I
will
make
sure
that
it
gets
handled
and
so
on
and
from
our
site
from
now
is
that
we
are
green.
There
is
not
a
lot
of
updates.
Y
It
has
been
mentioned.
There
is
the
1.2
20.0
alphabet
release
planning
for
tomorrow.
Daniel
is
responsible
for
this
one
and
he
will
be
cutting
it.
So
if
you
have
any
questions
about
or
anything
feel
to
pin
him
or
on
release,
manager's
channel
or
something
like
that,
so
I
think
that's
it
from
our
side.
From
now.
A
Awesome
thank
you
and
welcome
to
the
release
team.
We're
happy
to
have
you
joining
us
for
this
this
cycle,
any
questions
for
really
for
the
branch
managers.
A
All
right
next,
move
on
to
lockheed
and
he'll
provide
us
with
his
emeritus
lead,
update.
Z
Thanks,
jeremy,
hello
and
welcome
everybody,
if
this
is
your
first
release
team
meeting,
welcome
if
you're
coming
back
to
join
us.
Welcome
back
the
120
release
is
going
to
be
awesome,
last
release
of
2020.
So
let's
make
it
a
good
one
and
a
fun
one
in
the
last
week,
so
I'm
actually
the
emeritus
advisor.
So
I've
been
on
five
release
teams.
This
is
my
fifth
I'm
actually
here
to
help
you
all
make
it
through
this
process.
Z
So
if
you
need
anything,
feel
free
to
reach
out
to
me
feel
free
to
reach
out
to
jeremy,
we're
all
here
to
support
you.
If
you
have
any
questions
where
to
look,
no
questions
are
too
hard
for
us.
You
know
bring
it
all
to
us
and
if
you
need
any
help,
we're
here
to
support
you
in
the
last
week
I've
been
working
with
the
leads
to
select
all
the
shadows,
so
I
helped
with
the
shadow
application
process
and
helped
guide
the
leads
through
that
process.
So
kudos
leads.
I
know
it's
extremely
challenging.
Z
We
had
one
of
the
the
largest
amount
of
applicants,
I've
seen
in
any
release,
at
least
for
all
releases.
I've
been
on
with
over
100
applicants,
so
it's
very
hard
to
go
through
and
process,
but
welcome
to
everybody
on
the
team,
and
I
want
to
just
thank
the
leads
for
making
it
through
that
process.
So
we've
almost
completed
all
the
selections.
I
just,
I
think,
I'm
waiting
on
enhancements
just
to
make
sure
that
everybody's
confirmed,
but
I
did
hear
three
people
are
here
today.
Z
Z
So
I'm
going
to
take
an
hour
and
guide
you
through
all
the
tools
that
we
have
and
all
the
processes
that
we
have
to
help
you
on
board
as
a
shadow.
So
if
you're
here
with
a
lot
of
questions
and
worried
about
what
I
need
to
do
and
what's
expected
of
me,
we
hope
to
answer
all
those
things.
But
we
ask
you
know
that
you
you
talk
to
your
leads.
The
leads.
Are
there
to
mentor
you
and
to
help
you
through
this
process,
but
we're
all
here
to
support
you.
Z
So
I'm
excited
to
work
with
you
all
and
you
will
see
a
doodle
once
we've
finalized
all
the
shadows
and
we've
locked
them
all
into
the
roster.
I
will
send
it
out
directly
to
all
the
shadows
so
help
us
find
a
time
in
the
next
two
weeks
to
actually
make
that
happen.
I
think
that's
about
it
from
me
right
now,
I'll
be
around
in
in
slack
if
you
need
anything
as
you
onboard
and
get
familiar
with
the
process.
So
thanks
for
having
me
and
I'll
pass
it
back
to
jeremy
thanks
jeremy.
A
Lockheed
any
questions
for
lockheed
before
we
move
on.
A
Okay,
so
next
is
the
part
of
the
meeting
where
we
normally
would
get
the
release
lead
update
from
me,
or
whoever
from
my
team
is
leading
right
now
I'll,
just
pause
and
let
my
shadows
that
are
online
reintroduce
themselves.
So
everybody
is
familiar.
I
think
dan
had
to
drop
off,
but
I
think
savitha
and
nabarun
are
online
so
savita.
If
you
want
to
go
first.
AA
Sounds
good
to
me,
hello,
everyone!
This
is
avita,
and
this
is
my
third
release
team.
It's
it's
a
honor
to
be
a
part
of
this
release
team.
AA
I
work
as
a
platform
engineer
at
mathworks
and
you
can
say
I
love
and
breathe
kubernetes,
and
I
want
to
make
it
more
and
more
better,
and
one
of
the
reasons
that
I'm
here
is
the
community
is
so
welcoming,
and
I
want
to
keep
that
culture
going
and
be
more
inclusive
and
be
excellent
to
each
other.
Thank
you.
AB
Everyone
happy
like
good
morning
evening
afternoon,
whatever
it
is
in
your
time
zone,
so
I'm
navarron.
This
is
my
fourth
I'm
in
the
release
team.
I
have
been
here
since
1.17.
AB
I
have
been
in
the
enhancements
team
as
a
shadow
for
two
cycles,
and
then
I
let
the
announcement
stream
last
cycle
and
it's
great
to
be
back
to
the
team,
shadowing
jeremy
and
it's
it's
awesome
to
be
in
the
team
and
it's
really
great
to
see
such
a
diverse
team
this
time
around
thanks
everyone.
I
hope
you
all
will
have
a
great
release.
1.20
thanks.
A
Thank
you.
We'll
have
dan
introduce
himself
next
week.
Some
for
those
who
don't
know
me,
my
name
is
jeremy.
I
am
a
software
engineer
at
vmware
I
work
with
derek.
Coincidentally,
I
have
been
on
the
release
team,
I'm
trying
to
count
how
many
times
a
few
times.
A
Let's
just
say
that
I
shadowed
bug
triage,
I
think
in
113
and
then
I
came
back
to
shadow
enhancements
in
117
and
then
I
led
enhancements
in
118
and
I
shadowed
the
release
team
lead
taylor
last
cycle,
and
so
this
cycle,
I'm
picking
up
the
release,
lead
helm,
helping
everybody
to
be
successful
for
this
release.
A
A
We
also
neglected
to
add
a
test
freeze
date
to
this
calendar,
so
I
have
an
open
pr
that
I'll
link
after
the
meeting
just
so
people
can
review
it
will
be
towards
the
end
of
the
release.
Obviously
I
think
it's,
the
30th
it'll
coincide
with
the
docs
deadline
and
just
that's
a
fairly
new
phase
that
has
been
added
to
the
the
release
cycle.
We
want
to
make
sure
that
tests
are
pretty
healthy.
So
generally
that
would
coincide
around
the
time
of
code.
A
Freeze
it's
a
little
bit
later,
but
that'll
get
merged
in
after
I
make
some
updates
to
the
phases
document
as
well
and
then
again
we're
shooting
for
a
release
on
december,
8th,
obviously,
that's
a
little
aspirational.
Things
can
come
up,
but
that's
the
date
we're
shooting
for
right
now,
release
team
side.
We
will
be
trying
something
a
little
different,
this
cycle.
So
generally,
we've
had
one
set
of
release
meetings
and
those
have
been
mostly
us
time
zone
centric,
which
is
not
great
for
people
that
are
not
in
the
us,
especially
people
in
india.
A
It's
quite
late
right
now,
so
we
will
be
sending
a
doodle
after
this
meeting
is
over
at
some
point
that
we'll
have
some
proposed
times
for
a
meeting.
That's
a
little
more
centric
around
asia.
Pacific
time.
I
don't
think
we
have
anybody
east
of
india
on
the
release
team,
this
cycle
so
we'll
we'll
add
some
times
and
that'll
shift
and
maybe
give
a
little
bit
of
overlap
with
the
european
time
zones
as
well.
A
So
people
in
europe
can
pick
which
meeting
works
better
and
then
we'll
try
to
do
some
asynchronous
handoffs
and
see
how
that
works
and
obviously
we'll
make
some
course
corrections
through
the
cycle,
as
we
go
feel
free
to
offer
any
input.
You
have
on
that.
If
you
find
anything's
not
working,
speak
up
to
your
your
release,
lee
your
your
sub,
your
project,
lead
or
speak
up
to
lockheed,
come
to
me
we're
happy
to
take
any
and
all
input
along
with
that
and
please
feel
free
to
speak
up.
A
This
is
a
an
environment
where
everybody
should
feel
like
they
have
a
voice,
and
we
want
to
make
sure
that
you
all
feel
comfortable
presenting
talking
to
us
anything
like
that
and
yes,
that
is
a
tocochico
lime
behind
me.
It's
my
my
favorite,
oh
yeah.
I
love
it
any
any
questions
about
the
calendar,
any
questions
about
the
meeting
times
or
schedule.
A
Cool,
thank
you
everyone
for
that.
Generally.
We
next
have
an
update
from
sixth
scalability.
They
don't
generally
attend
this
meeting.
I
don't
think
anybody
from
scalability
is
online
right
now,
but
gener
they'll
generally
add
the
update
into
this
agenda.
So
we
can
keep
track
of
that
and
if
we
notice
any
problems,
we'll
we'll
of
course
circle
back
with
them.
A
Next
up
is
lori
and
she
will
give
a
pro
a
program,
management,
update
and
lori.
Can
you
introduce
yourself
for
all
of
the
folks
that
haven't
met
you
before.
AC
Oh
sure
so
I'm
lori
apple,
I'm
in
berlin,
germany
and
I'm
the
program
manager
for
sig
release
and
the
release
team
and
release
engineering.
Basically,
all
the
sub
projects,
in
addition
to
the
main
sig,
and
so
I'm
here
to
help
drive
alignment
collaboration,
communication,
prioritization,
so
things
like
road
mapping,
our
processes,
yeah
kind
of
this
road
mapping,
try
to
help
everyone
organize
work
into
into
themes
so
that
we
deliver
the
highest
value,
work
and
get
our
goals
met.
And
so
I've
made
some
progress
with
the
help
of
many
of
you
since
last
week's
meeting.
AC
So
last
week
we
discussed
using
our
project
board,
so
we
have
a
github
project
board
that
has
a
lot
of
items
of
varying
varying
sizes
and
ages,
and
we
wanted
to
use
the
project
board
to
store
longer
term
issues
of
relevance.
The
release
team
in
a
column
just
to
keep
them
on
our
radar
screen,
but
use
the
project
board
for
small
items
that
will
have
a
quicker
turnaround.
For
you
know
our
120
cycle
efforts.
AC
AC
I
will
post
more
threads
in
the
slack
channel
after
we've
closed
out
a
couple
of
the
other
ones,
so
I
think
we
close
out
one
or
two
so
probably
tomorrow
I
would
like
to
post
two
more
so
please
be
on
the
lookout
they'll
be
in
the
sig
release
channel
and
then
I've
closed
out,
116
and
117
retro
github
issues.
So
these
were
the
to
do's
from
past
retros.
AC
AC
If
you
have
any
suggestions,
I
would
be
great
like
you
want
to
have
a
brand
new
github
issue,
and
then
we
would
just
check
off
whatever
is
actually
been
done,
but
the
issue
is
some
of
these
might
need
some
discussion,
so
I
think
maybe
we
have
a
slack
thread
and
about
those
items
I'll
figure
that
out,
but
would
be
some
sort
of
combination
of
github
issues
and
slack
be
best
for
everybody.
AC
Okay,
so
that
will
be
the
plan
and
then
we
can
also
go
over
them.
There's
a
120
lead
sync
just
for
leads,
and
we
can
go
over
that
like
what
do
these
retro
items
mean
for
the
long
term
picture.
A
Yeah,
I
think
that'd
be
great
and
then
the
leads
can
help
identify
shadows
on
the
team
that
can
help
us
push
some
of
those
things
to
completion.
AC
Okay,
so
I'll
put
that
as
a
note
for
the
find
items
for
leads
to
pass
on
to
shadows
all
right.
So
the
next
item
I
had
was
last
week.
I
mentioned
this
feature
health
check
that
signate
has
done
to
review
their
caps
and
status
of
their
cups
and
just
decide
what
they
wanted
to
prioritize
in
120
or
what
they
wanted
to
close
and
kristen
and
jeremy.
AC
Had
the
question
that,
let's
ask
cigs
about
the
caps
that
others
file
on
their
behalf,
so
like
random
cups
that
just
kind
of
come
in
and
might
challenge
the
road
maps,
so
just
want
to
say
I'm
now
doing
that
so
there'll
be
some
data
on
that
coming
in
the
next
few
weeks
and
then
for
the
enhancements
team.
This
is
my
final
update,
basically
trying
to
present
I'm
having
trouble
with
my
browser.
Today.
AC
There
we
go
basically
wanting
to
have
two
goals
for
the
enhancements
processes
and
mechanisms
around
this
one
would
be
to
I
need
to
meet
with
steven
and
talk
through
the
receipts
process.
If
you
don't
know
what
that
means,
that's
okay,
there
will
be
details
to
come,
but
many
of
you
have
already
heard
of
this
receipts
process
concept.
AC
So
it's
basically
to
help
us
try
to
automate
more
of
the
interactions
with
cigs
and
create
a
healthy
boundary
of
accountability
between
what
the
release
team
needs
to
take
on
and
what
the
sigs
need
to
do
to
get
their
enhancements
in
on
time.
AC
So
we
need
to
just
kind
of
figure
out
what
that
will
look
like
write
it
down.
I
think
steven
knows
what
it'll
look
like,
but
just
write
it
down
and
share
it
with
everyone
and
get
get
that
more
transparent
and
then
a
caps
website
using
existing
metadata
that
we're
already
collecting.
So
this
would
actually
be
really
attractive
for
open
source
program
managers
like
paris,
pittman
other
program
managers.
Maybe
your
company
so
basically
like.
AC
How
could
we
query
on
the
website
what
kepts
her
in
progress
and
the
status
of
those
and
other
details
that
people
often
want
to
know
so
that's
what's
to
come,
but
hopefully
that
will
make
make
our
lives
a
bit
easier.
If
we
have
this
in
hand
and
and
moving
forward,
but
nothing
would
nothing
will
change
in
120.
This
would
all
be
for
gearing
up
for
121.
A
Thank
you
lori.
Any
questions
for
lori
before
we
move
on.
A
Cool
actually
one
question
for
you:
laurie:
do
you
want
to
walk
the
project
board
this
week,
or
should
we
start
that
next
week
after
we
do.
AC
Yeah
we
could
do
that
if
you're
willing
to
pull
it
up,
yeah
sure.
AD
A
Oh
wow,
all
right,
savitha
and
navaroon
are
also
co-hosts,
so
we'll
get
to
that
in
one
second,
just
another
brief
mention
here
generally
at
this
point
in
the
meeting
we
get
to
the
point
where
we
can
bring
up
open
items
so
as
we
go
through
the
process,
if
anything
comes
up,
that
you
need
to
bring
up
or
discuss,
feel
free
to
add
it
into
the
open
discussion
topic
here.
A
We've
also
linked
the
retro
document,
so
at
the
end
of
every
release
cycle,
we
do
a
retrospective
to
see
what
worked
well,
what
didn't
work?
Well,
what
could
do
better
and
generally
I
I've
found
that
as
we
go
through
the
cycle,
when
those
things
come
up
put
them
in
the
document,
so
that
we
don't
forget
them
and
we
have
a
good
set
of
of
what
went
well
and
what
didn't
go?
Well
just
so,
we
can
discuss
those
things
at
the
the
retro.
A
I
think
anybody
that's
been
on
the
release
team
before
or
chris
can
attest
that
the
the
retros
have
lots
of
good
discussion
topics,
but
those
are
really
driven
by
what
we
bring
and
add
to
the
the
retro
document.
So
please,
as
we
go
through
the
cycle,
let's
go
ahead
and
add
things
as
they
come
up,
so
we
don't
forget
them
and
just
make
sure
that
we
have
a
good
set
of
things
to
discuss
at
the
end
of
the
release.
A
A
AC
AC
So,
if
we
start
with
could
close
so
steven
said
he's
going
to
follow
up
on
this
note,
does
anyone
else
here
have
context
and
what
this
is.
A
The
request,
the
gift
yeah,
so
one
of
the
things,
the
release,
manager
or
sorry
the
release
lead
does
as
part
of
the
cycle,
is
to
pick
a
release
theme
and
then
generally
there's
a
release.
Gift
they'll
have
something
with
that
theme.
So
if
you
were
on
the
118
team,
jorge
produced
some
really
awesome
shirts
with
the
logo,
you
can
actually
go
back
and
find
them
across
different
releases
lockheed
had
a
really
really
excellent
one,
with
his
unlimited
breadsticks
for
all
theme
for
116..
So
I
think
that's
related
to
that.
A
I
don't
think
so
I
mean
I
think
that
should
be
assigned
to
to
win,
maybe
stephen,
to
follow
up
on
that.
AC
Okay,
I'll
check
in
with
stephen
again
see
if
there's
a
to-do
and
then
the
next
item
create
a
shadowing
retrospective.
We
had
a
little
bit
of
discussion
about
this
and
our
release
leads
meeting.
A
Yeah,
I
don't
think
we
should
action
this,
yet
I
think
the
consensus
was
that
we
should
try
to
not
do
a
separate
shadow
retrospective.
We
should
make
sure
that
we
have
a
an
environment
where
everybody
feels
free
to
speak
up
and
if
you
don't
feel
free
to
speak
up,
talk
to
lockheed
talk
to
me
talk
to
steven
or
tim
or
or
laurie.
Z
Z
We
can
keep
that
this
this
release
and
see
how
effective
it
is,
but
we
just
want
to
make
sure
that
the
shadows
have
feel
supported
and
have
appropriate
feedback
channels,
but
we
also
are
conscious
that
we
don't
want
to
throw
more
meetings
on
everybody's
calendars,
yeah
for
more
retros,
and
so
I
think
we
could
probably
manage
it.
L
AC
Feeling
comfortable
talking
in
the
bigger
group,
so
two
two
points
on
this
is
that
we
will
start
having
monthly
lead
sinks,
and
this
is
where
we
can
talk
about
communication
and
helping
the
shadows,
stay
integrated,
working
with
the
shadows
to
help
them
feel
comfortable
and
speaking
up
in
any
of
the
meetings
and
then
also
basically
just
having
retrospective
like
check-ins.
AC
Z
Yeah
so
there's
there's
two
items
on
this.
I
actually
went
back
to
the
last
two
eas
and
and
made
sure
the
survey
actually
hasn't
changed.
There
was
one
suggestion
that
I
think
robert
made,
which
was
to
add,
preferred
pronouns
to
the
to
the
shadow
application.
So
I'm
going
to
update
the
template
that
we
passed
between
and
take
and
add
that
as
a
comment
too.
So
thanks
for
that
feedback,
robert
we'll
get
that
added
to
the
119
shadow
application
form,
and
I
think
we
can
close
that
too.
A
C
A
Okay,
so
we
have
about
20
minutes
left,
hopefully
we'll
finish
this
up
a
little
bit
earlier.
Z
A
People
back
some
time
should
we
review
the
blocked
waiting
stuff
next
or
yeah.
AC
Okay,
how
about
that
so
we
have
this,
enable
cherry
pick
plugin
in
kubernetes
org.
If
you
want
to
open
that
and
just
see
what
that
is.
AC
AD
A
Okay,
yeah:
let's,
let's
follow
up
with
the
release
engineering
slack
and
our
sig
release,
and
we
can
figure
out
where
to
drop
this
one.
AC
A
I
think
no,
these,
this
is
they'll
mostly
be
impactful
to
the
release
to
the
branch
management
and
the
release
managers
since
they're
the
ones
that
do
most
of
this
I
think
it'll
become
it'll,
become
if
we
enable
this
now
it'll
be
more
widely
impactful
for
everyone.
When
we
lift
the
120
milestone,
that's
actually
going
to
be
discussed.
A
I
think
a
sig
release
tomorrow,
so
we
can
I'll
go
out
of
that
to
the
agenda
and
then,
when
we
get
to
code
freeze
like
generally,
then
we
start
requiring
cherry
picks,
so
this
may
or
may
not
be
having
any
impact
in
120
if
it
happens
during
the
120
time
frame.
Okay,.
AC
All
right,
then,
updating
ci
signal
issue
format
to
be
more
conducive
to
triage.
F
F
There's
some
things
that
I
would
like
to
do
on
this
and
so
yeah.
Let's
keep
that
open
and
maybe
maybe
assign
it
to
me,
okay,
yeah
and
I'll
review
it.
I
I
don't
fully
under.
I
don't
know
I've
not
seen
this
before,
but
but
just
from
that
quick
scan
of
the
title,
I
think
that
there's
a
it
could
do
it
a
bit
of
fine
tuning.
Okay,.
A
I'll
I'll,
actually
in
sig
release,
we
can
start
a
thread
to
discuss
it.
There
cool
so
dan
can
also
chime
in
yeah.
AC
A
AC
A
All
right,
so
the
in
review
section,
which
handbook
is
this:
let's
fix
the
royal
handbook
url
to
point
to
the
right
directory,
looks
like
this
is
open,
so
we
should
have
the
let's
just
see
which
one
it
is.
A
A
Okay,
next,
after
that,
patch
update
release
schedule
for
119
118
and
117.
opened
by
carlos
marco.
Do
you
have
any
comments
you
want
to
add
on
this
one.
Y
A
Okay,
so
maybe
we
can
move
this
one
to
a
more
release,
engineering
or
release
manager,
centric
board.
A
Okay
next
is
12
46
and
that's
an
issue
that
I
just
opened.
It's
got.
Some
changes
requested
that
I
need
to
resolve
today,
but
essentially
that's
going
to
add
a
test
freeze
deadline
to
the
schedule
right
now
we
don't
have
one,
and
it
was
pointed
out
in
sig
release
that
we
needed
to
have
one
so
this
this
pr
is
aimed
at
doing
that.
A
Hopefully
I'll
have
that
resolved
today,
and
then
we
can
get
tim
to
re-review
it.
He
was
one
that
requested
some
changes
and
then,
lastly,
our
in
progress
section
assemble
the
kubernetes
120
release
team.
This
is
in
progress
and
we
will
hopefully
resolve
that
this
week,
once
we
have
all
of
the
shadows
identified
and
onboarded
we'll
be
able
to
close
this
one
and
then
lastly,
rob
do
you
want
to
discuss
your
automate
ci
signal
weekly
status
updates.
F
Yeah
sure
so
so,
there's
prior
art
here
from
nice.
I
mentioned
this
at
the
top
of
the
meeting,
and
so
elena
did
did
some
work
on
this.
I've
updated
that
to
to
kind
of
get
a
handle
on
how
that
works,
and
I
think,
from
from
next
week
on
from
next
week
on
I'll
I'll,
have
a
I'll
have
the
ability
to
generate
that
report.
F
The
the
thing
that
we
would-
and
this
might
be
better
discussed
in
release
engineering
and
the
thing
that
I
that
I'd
like
to
be
able
to
do,
is
to
have
a
place
to
record
and
the
snapshots
that
we
take
of
the
state
of
the
signal
in
relation
to
flakes
and
the
issues
open
so
that
we
can
track
metrics
over
time.
So
right
now.
So
so,
right
now,
when
we
manually
create
the
report,
we
go
to
test
grid.
We
go
to
the
test.
F
We
go
to
the
tab
grouping,
we
click
on
sort
by
status,
and
we
manually
review
the
the
contents
of
that
summary
and
and
what
the
what
the
code
that
elena
created
basically
goes
to
the
project
board
and
goes
through
the
issues
on
the
project
board.
But
also
goes
to
test
grid
and
gets
the
summary
counts
of
what's
flaking,
what's
not
flaking,
so
so
we
have
the
opportunity
to
store.
Okay.
F
On
monday
afternoon
we
had
at
nine
flaking
jobs,
and
then
tuesday
we
had
five
flaking
jobs
or
more
or
whatever,
so
that
we
can
track
those
metrics
over
time.
That's
something
that
we're
interested
in
in
getting
to,
and
so
I
what
I
would
like
to
do
on
this
is
is
basically
architect
something
whereby,
whereby
this
has
a
proper
home
in
in
in
a
kubernetes
repo,
not,
but
not
only
that,
I
just
want
to
basically
leverage
off
our
existing
ci
infrastructure.
F
In
order
to
basically,
I
presume,
I'm
kind
of
thinking,
maybe
using
prometheus
or
grafana
to
to
dashboard
out
and
show
trends
over
time.
So
so
we're
at
the
stage
where
I
can
now
run
this
report,
I'm
going
to
do
some
work
on
it
to
maybe
produce
json
or
or
whatever,
and
what
I
want
to
do
is
stick
a
timestamp
on
it
and
find
a
home
for
that
on
the
disk
somewhere
and
then
start
using
that
as
a
data
source
for
for
trend,
analysis.
A
Awesome,
I
think,
that'll
be
really
really
useful,
especially
as
we
get
towards
the
later
half
of
the
release,
and
we
really
really
care
about
this
data.
F
Yeah,
absolutely,
and,
and
and
and
and
the
thing
that
that
I
need
to
do-
is
to
update
that
issue
with
that
brain
jump
and,
and
just
start
some
conversations
about
well,
how
can
I
make
this
official
currently
elena's
work
is
in
a
private
repo.
I
forked
from
her
work
and-
and
we
just
need
to
find
a
home
for
this.
A
Okay,
that'd
be
awesome.
Yeah
we'll
have
some
some
more
discussions
about
this
later
on
for
sure,
yeah.
AC
AC
Yeah
sure
it's
also
in
the
agenda
for
everybody.
Just
so
you
know
it's
there,
but
sure
I
can
totally
just
do
that.
A
U
A
Yeah
and
if
you
have
questions
about
any
of
them,
feel
free
to
start
threads
in
sig
release
and
we
can
can
iterate
from
there
awesome
well.
Thank
you.
Everybody
thanks
to
everybody
for
joining
us
for
the
first
time,
thanks
to
everybody
else,
that's
that's
here.
It's
not
your
first
time
for
sticking
with
us.
A
If
you
have
any
questions,
feel
free
to
reach
out
to
me,
or
anybody
on
my
team
society
or
dan
or
nabaroon
on
slack,
we'll,
be
happy
to
answer
any
questions
or
concerns
you
may
have
yeah.
I
guess
that's!
That's
it
for
today
see
everybody
next
week
and
see
everybody
on
the
internets.