►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200701
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
Hello,
hello,
hello,
everyone.
This
is
another
installment
in
the
release
team,
early,
119,
release,
team
meeting,
it's
July
1st
2020
I,
have
posted
the
octopus
of
the
agenda
and
chat
and
saw
Carlos
comment:
fantastic
yeah,
that's
nice,
nice
weather
all
routes
actually
clowder
in
LA.
It
does
not
look
like
this.
You
can
usually
not
see
the
mountains
should
be
a
pretty
quick
meeting
today.
I,
imagine
and
with
that.
Let's
get
started
with
the
incidents
with
number
in
every.
B
Happy
day
evening
night,
so
announcements
still
remains
the
same.
We
had
yellow
we're
tracking
the
same
number
of
enhancements.
Nobody
has
dropped
out
since
the
last
meeting
other
than
that
some
enhancements
have
gone
out
of
the
at-risk
category
and
some
have
gone
in.
So
the
number
still
remains
same
at
12.
We
have
reached
out,
through
slack
github,
to
several
enhancements
that
we
feel
may
need
more
attention
and
over
the
course
of
the
rest
of
this
week,
and
probably
by
Friday,
we'll
have
more
enhancements
at
risk
and
probably
will
go
to
the
red
territory.
D
D
There
is
ongoing
work
going
on
with
that
and
both
so
I'll
be
able
to
add
detail
to
that
on
the
next
day's
update
and
for
the
flaking
jobs,
and
we
have
we've
have
a
couple
of
issues
loved
there
and
and
basically-
and
if
you
click
through
to
them,
you
can
see
where
we're
at
with
them.
So
there's
there's
ongoing
work
and
taking
place
to
to
sort
out
those
jobs.
One
of
the
one
of
the
peers
and
therefore
cube
ADM
needs
approvals.
So
it
would
be
great
if
we
have.
D
Somebody
have
a
look
at
that
in
kind
master
parallel.
We
have
an
a
similar
range
of
jobs
and
failing
such
flaking
there
and
and
on
you
on
the
cubelet
master,
and
I
there
has
a
pea
or
been
merged
on
that.
So
we're
kind
of
tracking
that
at
the
moment
so
contain
container
d,
has
flipped
back
from
flaking
to
passing,
and
there
was
one
issue
that
I
had
visibility
on
and
cluster
up.
And
where
do
you
failed
one
day
a
few
days
ago,
but
hasn't
happened
since
and
so
on.
D
And
so
yeah,
so
that
there
is
so
there
is
one
job
that
is
a
conformance
conformance
test
job
that
runs
twice
a
day
and
then
asked
and
one
of
the
issues
do
we
want
to
run
more
than
twice
a
day.
I
was
just
wondering:
would
anyone
have
any
and
thoughts
and
that
I
could
talk
to
the
the
conformance
people
offline
if
needs
be,
and
but
if
anyone
had
an
opinion
on
that
and
could
share
now,
that
would
be
great.
But
but
if
not,
we
can
move
on
I.
Think.
E
He
was
originally
bringing
that
one
up
because
it
was
flaking,
so
we
were
getting
like
some
weird
say:
no,
where
we
weren't
really
sure.
If
you
know
conformance
test,
failing
is
kind
of
a
big
deal,
so
I
think
that
one
was
flaking,
so
it
was
difficult.
It
was
taking
a
long
time
essentially
to
realize
if
there
was
an
actual
issue
or
if
it
was
just
the
flake
being
exposed
so
depending
on
the
flakiness
of
that
job,
which
I
can
also
take
a
peek
at,
we
might
want
to
run
it
more
often.
A
G
The
dog's
status
is
ello.
We
have
like
21
draft
PRS
that
needs
to
be.
You
know
that
that
needs
to
go
into
the
PR,
editor
review
state
and
the
status
at
all,
because
we
have
like
nine
ish
finish
list,
even
though
the
deadline
is
on
six.
It's
a
soft
we
are
treating.
That
is
a
soft
midline
and
it's
a
that's
about
the
PRS.
G
And
the
next
thing
is
the
branch
think
a
bit
so
I
think
the
branch,
the
del
1.90
website
branch
in
I
think
the
master
branch
from
the
website
into
the
day
of
1.19
to
keep
all
the
changes
in
place
so
that
it
avoids
the
merge
conflicts
later
during
the
release
day.
And
while
doing
so,
it's
done
frequently
every
week
or
every
other
week
and
the
it
was
to
us
today
and
I
did,
and
there
were
two
issues.
I
thought
I
bring
it
up
and
mention
it
here.
G
The
first
one
was
in
Italy
for
a
shoe
and
the
website
wouldn't
build.
It
was
because
of
it
was
trainable
even
from
a
calendar
and
the
talking
was
changed.
A
pedo
chemistry,
intro
I,
don't
know
what
happened
there.
There
was
an
unauthorized
issue
and
that
has
been
resolved.
The
second
one
is
an
invalid
comet,
massage
issue,
and
because
of
that,
the
saint-pierre
cannot
be
merged.
This
has
been
propagated
from
the
master
branches
or
from
the
localization
branches,
and
these
I
looked
into
the
issues
and
they
don't
have.
G
Some
of
them
are
March,
some
of
them
are
closed
and
the
the
invalid
comet
issue
in
those
PRS
are
actually
addressed,
and
this
looks
like
a
pro
issue.
It's
picking
up
those
messages
and
Tim
banister
has
it's
kind
of
that.
He
has
agreed
to
share
knowledge
and
help
me
debug
these
issues,
so
I
want
to
shout
out
to
them
here
and
I'm
working
with
them
on
solving
the
invalid
comment.
Machine
message
issue.
G
That
was
one
issue,
and
this
is
another
issue,
even
though
the
mod
the
arts
are
March
and
they
are
good
to
go
and
this
filters
and
just
pulls
the
addressed
issues
and
brings
on
to
the
branch,
sync
and
I.
Don't
know
why
that's
happening
I
could
work
with
those
folks
on
getting
that
resolved.
Does
anyone
have
any
input
on
like
any
background
on
why
this
could
be
happening?
Or
is
it
something
new
that
new
to
everyone,
any
thoughts
and
opinions
on
that.
A
I've
seen
a
few
when
working
in
Docs
I
have
seen
a
few
invalid,
commit
message
issues
and
it's
typically
I
can't
remember
if
it's
just
a
linting
rule
within
prowl,
but
I've
seen
that
where
it
doesn't
like
some
of
the
characters.
Sometimes
it
doesn't
like
just
the
format
of
the
get
commit
messages
but
I
think
that's
it
I'm,
not
sure.
If
it's
the
same
context,
however
yeah,
that's
that's
the
the
context
in
which
I've
seen
it,
but
not
sure.
If
anyone
else
is
the
insight
on
that
front,.
A
G
C
Happy
Wednesday
everyone
on
release
notes.
We
are
green.
We
have
had
no
particular
change
or
update
since
the
last
release,
especially
at
least,
and
we
don't
anticipate
anything
particularly
changing
until
the
first
release
candidate,
which
is
I
believe
over
scheduled
the
Thursday
after
next.
So
I
thought
it
was
really
any
questions.
H
X
is
not
here
today
you
got
Joseph,
so
I'm
gonna
come
give
it
to
you.
Sorry,
everybody
I'm
not
on
camera
I'm
out
in
the
middle
of
nowhere
just
got
on
satellite,
just
to
kind
of,
say
hello
and
our
update,
basically
we're
looking
green.
Everything
is
good
right
now
we
have
505
feature
blogs
that
are
aligned.
We
have
scheduled
our
webinar
for
kubernetes
119
for
the
28th
of
August,
but
this
is
when
things
get
really
hot
in
heavy
parts.
H
A
I
A
I
I
A
Awesome,
thank
you
so
much
I
I
believe
Tim
had
a
conflict
and
it's
not
able
to
make
it
here
today.
So
I'm.
Moving
on
to
my
updates,
like
was
said,
July
6th,
we
have
docked
pr's
ready
for
review
July
9th.
We
have
code,
freeze,
July,
16th,
no,
no
docks
deadline
and
finalized.
Today,
as
was
said,
is
Canada
Day.
So
that's
why
some
of
us
are
missing
on
Friday,
it's
the
3rd
of
July,
but
it's
the
4th
of
July
observed
in
the
States
I
will
not
be
here.
A
Jeremy
will
be
leading
on
Friday
and
then
currently,
the
we
Bob
myself,
Tim
and
Stephen
are
and
Jeremy
all
working
on
messaging.
For
that,
like
you
had
said,
Carlos
we
have
a
blurb
going
on
right
now,
we're
just
trying
to
work
on
the
messaging
around,
what's
different
from
118
to
119
and
kind
of
like
what
the
cherry-pick
process
looks
like
what
code
freeze
looks
like
and
what
the
expectations
are
need
to
be
set
there.
A
So
I'm
hoping
that
will
I
saw
a
lot
of
comments
around
that
yesterday,
so
we're
in
like
draft
two,
so
we
should
have
that
very
soon.
In
here,
I'd
say
either
today
or
early
tomorrow
is
we're
likely
to
push
that
out
we're
going
to
be
sending
to
ke
dev
sig
release
and
the
release
team
groups
so
should
have
more
on
that
soon.
Any
questions
on
deadlines
or
messaging
on
that
front.
A
A
All
right
well,
thank
you
so
much
everyone
for
the
action-packed,
Wednesday
I
hope
you
all
are
doing
well
we're
halfway
through
the
week.
I
can
see
the
the
weekend
in
the
distance.
I
will
see
y'all
next
week
again,
Jeremy
will
be
leading
on
Friday
and
wish
you
well
I.
Guess
everybody
going
bye,
bye,
bye,.