►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200519
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
All
right
welcome
119
release
team.
It
is
Monday,
May,
18th,
2020
I.
Think
don't
quote
me
on
it
very
happy
to
see
you
all.
This
is
a
kubernetes
meeting
which
hides
by
the
kubernetes
could
have
conduct,
which
is
be
respectful
and
absolute
best
to
one
another.
This
meeting
will
be
uploaded
to
YouTube
and
available
later
on
today.
So
please
fold
down
anyone.
Please
please
go
and
your
name
to
the
agenda.
If
you
haven't
already
and
again
welcome
I
know:
we've
switched
to
bi-weekly
meetings.
A
Our
next
one's
gonna,
be
on
June
1st
next
week
on
the
25th
is
a
u.s.
holiday,
Memorial
Day,
so
I'll
be
outside
grilling,
burgers
and
hotdogs,
and
things
like
that
I
hope.
You
all
had
a
wonderful
weekend.
I
have
a
couple
announcements
away
to
the
end:
I'd
love
to
turn
it
over
to
number
room
for
enhancements,
hello.
B
Everyone
happy
Monday
good
morning
evening,
depending
on
the
time
zone,
so
we
have
a
important
milestone
coming
up
this
week
this
week,
that
is
tomorrow.
We
have
announcements,
please,
and
we
are
tracking
43
enhancements
in
total,
with
all
Tina's
not
ready,
and
that's
the
reason
why
we
are
too
yellow.
B
Other
than
that
I
have
listed
down
all
the
caps
that
are
not
ready,
grouped
by
sync
for
others
to
look
at
and
then
Iceman's
team
will
be
reaching
out
to
the
six
either
on
slack
or
pinging,
the
authors
directly
about
what
is
left
and
how
can
we,
as
a
release
team,
help
out
in
getting
more
free
viewers
or
approvers
so
yeah?
That's
all
from
my
side.
Any
questions,
a.
B
A
Yeah
definitely
curious:
I
know
that
we'll
probably
push
back
a
little
bit
more
this
time,
just
with
you
know
again,
current
state
of
the
world
and
just
trying
to
get
a
good
sense
of
everyone's
evil
ability
to
commit
time
to
each
of
those
cups
and
those
features
so
well
we'll
be
setting
records
one
way
or
another.
Thank
you
very
much.
Any
other
questions.
D
Hey
folks
hope
everyone
it
is
doing
well,
we
are
yellow
today
we
just
have
a
few
flakes
on
master
blocking,
but
a
lot
of
improvement
since
the
last
meeting,
specifically
with
some
of
the
kind
jobs
we
are
seeing
quite
a
lot
of
time
outs
on
jobs,
that's
leading
to
regular
flakes
so
we're
trying
to
get
that
addressed.
That's
why
I'm
instructure
side,
one
thing
to
mention
here
in
the
notable
events
is
we
recently
merged
a
PR
to
start
assigning
CI
signal
team
members
to
issues
alongside
whoever
from
the
sig
is
addressing
it.
D
So
the
idea
there
is
that
we
have
more
ownership
from
shadows
and
that
sort
of
thing
and
all
the
shadows
on
the
CS
signal
team
have
been
really
eager
to
get
started.
So
it
kind
of
spreads
the
load
and
also
make
sure
that
issues
don't
get
lost.
I
mean
we
have
a
seamless
transition
from
cyclo
disciples,
so
that
was
great
to
see.
I
mentioned
those
kind
jobs
looking
better,
there
are
fixes
in
our
open
for
a
number
of
jobs
as
well.
D
Gc
cost
master
default
is,
has
APR
open
right
now
that
we
think
will
fix
that.
Moving
on
to
master
informing,
there
has
been
some
progress
made
on
Windows
tests
in
that
there
was
a
part
of
the
guest
book
application
and
it
was
identified
as
flaking.
However,
that
has
not
improved
the
overall
status,
so
we're
still
getting
no
signal
there,
but
folks
from
cig
windows
have
mentioned
that
they
are
investigating
and
we
continue
to
to
poke
them
to
continue
to
do
that.
So,
hopefully,
looking
for
more
more
signal
there,
GC
master
scale
correctness.
D
This
just
happened
this
morning
and
it
was
just
a
flake,
a
number
of
flakes
in
a
row
that
led
to
a
failing
test.
So
not
a
lot
of
concern
there.
There
was
an
identification
with
some
of
the
cluster
API
jobs
that
the
GCP
project
names
are
causing
flakes
because
the
pod
names
are
generated
from
the
project
names.
So
basically,
if
the
project
names
get
too
long,
pod
names
get
too
long
and
that
fails
to
provision
them
so
we'll
have
a
fix
in
for
that
and
then
the
last
thing
there
is
the
cube
admin
jobs.
E
F
G
Happy
Monday,
everyone
release
notes
were
green.
We
merged
the
release,
notes
for
119
alpha
3.
We
updated
release
instructions
and
flexibility
on
our
tools
and
also
merge
the
updates
for
release,
notes
and
roll
handbook
to
reflect
changes
based
on
discussion
for
our
discussions.
We've
also
scheduled
the
release
notes
for
beta
coming
this
week.
A
C
We
are
Queen
so
far,
actually
we're
looking
forward
for
the
enhancement
freeze,
checking
out
currently,
what's
all
tracked,
what
are
the
hot
shots
where
we
can
go
and
maybe
slice
and
dice
a
nice
feature
blog
posts
out
of
it?
So
this
was
officially
then
starts
tomorrow,
and
then
we
would
reach
out
to
the
cichlids.
H
I
Not
too
much
to
mention
this
week
just
a
reminder
that
if
anybody
both
shadows
and
leaves,
if
you
have
any
questions
along
the
way
or
concerns
need
to
chat
about
anything,
feel
free
to
reach
out
to
me
for
the
shadows
in
particular,
I
should
be
singing
out
a
doodle.
Hopefully,
today,
I've
been
behind
on
it
on
just
having
a
meeting
for
us
to
get
together
and
chat.
Miss
general
things,
and
it's
one
thing
for
me
to
say
like
Bing
me.
I
If
you
have
a
question
but
different
things
come
out
in
conversation
when
we
actually
just
get
together
and
have
a
meeting.
Somebody
mentioned
something
maybe
out
loud
and
everybody
else
says.
Oh
I've
been
wondering
that
too.
So
it's
kind
of
time
in
the
cycle
have
one
of
those
meetings
just
to
kind
of
chat
a
bit.
So
hopefully
I'll
have
a
doodle
out
to
your
emails
for
that
shortly
and
then
I
was
talking
to
the
Marquis.
Who
is
the
emeritus
advisor
last
time
around
about?
I
A
All
right,
the
biggest
updates
that
I
had
for
you
were
really
just
around
milestones
and
if
you
haven't
heard
enhancements,
freeze
is
happening
tomorrow,
end
of
day
Pacific
time,
it's
very
important
and
again
we're
gonna
be
a
little
bit
less
lenient
on
some
of
the
exceptions
going
forward
with
those
caps.
Just
because
we
want
to
keep
this
light,
this
release-
and
you
know,
make
sure
that
again,
everyone
has
the
time
the
commitments
available
to
actually
put
into
those
caps
and
making
them
happen.
A
There
is
again,
you
know
reiterating
Sasha's
point,
there's
a
beta0
release
tomorrow
as
well
and
yeah.
That's
that's
we're
looking
at
I
do
also
owe
you
a
doodle
on
the
upcoming
changes
to
our
schedule.
I'm
gonna
talk
with
you
all
about
it,
a
little
bit
more
just
in
cig
release
and
a
couple
other
contexts
about
how
we
go
with
our
meetings
going
forward.
A
Sig
scaleability
I,
don't
believe
that
Matt's
here
to
talk
to
it
but
said
that
the
scaleability
jobs
look
good,
the
Russians.
As
of
this
point
in
time,
I
would
like
to
remind
everyone
that
the
retrospective
document
is
available,
and
so,
as
you
hit
certain
things
within
the
release,
things
that
you
think
we're
doing
good
could
be
better
any
problem
areas
or
things
that
we
can
work
on.