►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200626
Description
Kubernetes 1.19 Release Team Meeting 20200626
A
Hello,
everyone
and
welcome
to
the
june
26th
kubernetes
119
release
meeting
this
is
week
11.
before
we
get
started,
just
a
reminder
that
this
meeting
is
covered
by
the
kubernetes
code
of
contact,
which
can
be
boiled
down
to
be
excellent
to
one
another,
and
with
that,
let's
kick
it
off
with.
C
Okay,
we'll
go
to
ci
sign,
we'll
come
back
announcements
cool,
so
the
update
is
a
little
light
today
because
chasing
down
another
fix
that
we
need
this
morning,
but
we've
seen
quite
a
lot
of
red
because
of
a
pr
that
was
merged.
That
update
some
of
the
sig
scheduling
tests
and
we
got
a
fix
in
for
that.
They
got
merged
early
this
morning,
but
it
looks
like
a
follow-up
is
needed
as
well,
so
the
boards
aren't
really
reflective
of
our
current
status
right
now.
C
So
we
should
have
that
in
today,
but
I
listed
some
of
the
jobs
that
are
being
affected
by
that
both
the
failing
on
master
blocking
and
then
a
few
on
master
and
for
me
as
well
other
than
that
not
too
many
updates
pretty
much
same
status
as
wednesday.
C
An
update
on
the
windows
jobs
did
have
a
nice
discussion
with
some
folks
over
on
their
team
and
they're
working
on
getting
those
healthier.
They
said
that
they
have
had
some
folks
out
for
various
reasons
over
the
past
couple
months,
so
it's
kind
of
been
difficult
for
them
to
keep
up
there.
So
from
the
ci
signal
perspective,
we're
going
to
see
if
we
can
jump
in
and
get
some
of
those
healthier,
but
we
did
get
some
nice
response
and
they
gave
us
some
direction
about
how
we
can
help
them.
Do
that.
A
That's
great
thank
you
for
trying
to
jump
in
and
help
with
the
windows
tests.
I
think
that'll
make
a
big
difference.
Do
you
need
any
help
chasing
down
the
follow-up
fix
to
the
the
fix
that
went
in?
No,
I
don't
think
so.
I'm
actually
about
to
open
a
pr
for
right
here.
Okay,
awesome!
Thank
you
so
much.
I
just
wanted
to
say
your
your
updates
have
been
consistently
awesome
and
thank
you
so
much
for
the
level
of
detail
that
you
put
into
these
things.
It
makes
it
really
easy
to
look
through
and
see.
B
Hello
yeah,
our
numbers
are
almost
the
same,
just
not
going
down
as
fast
as
I
would
hope.
For
but
yeah
I
mean
we
are
monitoring
a
bunch
of
forecasts
that
are
very
close
to
getting
and
we
are
trying
to
don't
miss
that
opportunity.
B
Yeah
I
mean
we
are
reaching
to
the
very
state
broadcast
that
probably
won't
make
it
and
we
are
actively
monitoring
the
one
that
are
very
close
to
have
that
proof.
So.
D
Hi
everyone,
so
doc
is
green
right
now
we
have
already
nine
pr
34
review
and
we
are
still
and
gotten
good
responses
from
most
of
the
owners
and
the
1.19
branch
is
frequently
synced
with
the
master
and
the
branch
is
looking
healthy
and
not
so
many
merged
conflicts,
and
it's
all
going
on
well
from
that
side
of
the
world
too.
E
There
we
go
yeah,
sorry,
so
we're
just
being
no
changes
in
this.
Since
the
last
meeting.
F
So
adolfo
is
my
lead.
I
wanted
to
ask
him
on
the
calls
that
everyone
also
understands
what
we've
been
working
on.
We've
had
a
couple
of
releases,
I
think
1.16
that
we
failed
to
generate
notes
for
that.
I
think
the
previous
teams
didn't
generate
notes
for
them,
but
we
keep
getting
some
errors.
F
E
Yeah,
that's
still
something
I
have
to
look
into
it
from
what
you
told
me
there.
There
was
a
problem
generating
the
patch
release,
notes
for
1
16
11.
I
think
yeah,
that's
true.
E
Okay
yeah!
I
I
still
haven't
had
any
chance
to
see
what's
causing
the
error,
but
should
be
probably
this
weekend
and
probably
this
weekend
should
be
resolved.
A
Cool
thanks
for
that
update
any
other
questions
for
release,
notes.
A
Okay,
I
will
sync
up
with
them
offline
and
see
if
we
can
get
an
async
update
dropped
in
here.
I
think
carlos
said
he
wouldn't
be
able
to
join
today.
Sasha
any
release
branch
management
updates
beyond.
What's
here
hey?
No,
we
are
pretty
green,
so
no
updates.
Since
wednesday.
From
our
side,
all
right
sounds
good.
I
don't
see
tim
on
either,
probably
nothing
of
import
for
him
to
report.
A
So
we'll
move
on
to
the
release
lead
update.
We
have
a
few
milestones
coming
up.
The
docs
prs
are
supposed
to
be
ready
for
review.
That
again
falls
before
code
freeze,
so
we're
going
to
treat
that
kind
of
like
a
soft
deadline,
just
encourage
people
to
have
them
ready
to
go
just
so.
People
don't
put
it
off
until
the
week
between
code,
freeze
and
docs
deadline
code
freeze
will
be
on
the
ninth
and
we'll
go
into
a
period
where
we'll
allow
tests
and
stuff
to
be
merged
in.
A
But
you
know,
code
is
good.
It's
mostly
going
to
be
like
normal
code
freeze
and
then
the
doc
said
line
will
be
the
week
after
that,
on
the
16th
and
crazy.
We
have
only
nine
weeks
to
go
we're
going
to
release
on
the
25th
according
to
the
plan
and
we're
like
pretty
pretty
close
to
that
we're
week,
11
right
now,
so
more
than
halfway
there,
there
wasn't
any
additional
update
from
sixth
scalability.
So
we'll
move
on
past
that
to
open
discussion
items
it
looks
like
laurie
has
added
a
couple
so
take
it
away.
A
G
Hi
so
yeah,
I'm
glad
to
be
your
program
manager
here.
So
it's
my
first
time
as
that.
So
two
things,
I'm
scheduling
chats
with
I
started
with
the
role
leads
first,
but
anybody
here
is
welcome
to
schedule
some
time
with
me.
There's
a
spreadsheet
in
the
agenda
and
you
can
just
drop
your
name
for
20
minutes
slot.
G
The
idea
here
is:
what
can
I
do
to
help
you
so
keeping
in
mind
that
this
doesn't
mean
we
want
to
change
all
of
the
roles,
but
basically
like
what
what
gaps
can
I
feel,
and
especially
for
the
119
cycle?
What
are
what
are
your
urgent
needs
things?
You
would
need
support
with
to
get
things
moving,
get
things
done,
and
then
we
can
think
in
through
that
we
can
talk
long
term
about
you,
know
future
needs
and
then
luckily,
we've
been
having
our
breakouts
on
the
different
priorities.
G
I
had
done
a
sweep
in
april
and
then
I
was
just
updating
my
notes
based
on
a
bunch
of
different
github
queries,
and
so
I
did
the
needs.
Sig
query
and
the
bug
triage
team
has
graciously
agreed
to
help
with
that.
But
if
anyone
else
would
like
to
get
involved
to
help,
please
do
so
there's
only
like
31
issues
or
so
because
we
don't
want
to
treat
really
new
issues.
We
can
wait
for
them
to
be
triaged
through
cigs
processes,
but
there
are
some
old
items
that
have
been
in
that
bucket
for
a
while.
A
That's
it
awesome.
Thank
you.
We
forgot
to
go
back
to
enhancements,
so
let's
do
that
now
too.
Harsha
is
your
audio
okay.
A
Now:
okay,
well,
the
the
update
was
green.
You
know
at
this
point
there's
not
a
lot
of
change
that
happens
for
enhancements
next
week,
we'll
look
to
see
if,
if
how
comfortable
we're
feeling
with
the
things
that
haven't
merged
yet
and
oh
wait,
harsh
unmuted.
A
Nope
doesn't
sound
like
it:
okay,
well
yeah,
so
the
update
for
enhancements
is
still
green.
If
you
have
any
things
you
want
to
add,
asynchronously
harsha
or
anybody
else
from
the
enhancements
team
feel
free
to
drop
them
in
the
meeting
notes
with
that
I'll
open
it
up
for
any
other
questions,
and
if,
if
there
are
no
other
questions,
we
can
end
a
little
bit
early
today
have
a
few
minutes
back
of
your
friday.