►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200805
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-
this
is
another
119
release.
Team
meeting
today
is
august
5th
2020.,
it
is
wednesday.
I
hope
you
all
are
doing
well.
This
is
a
kubernetes
meeting,
so
we
abide
by
the
kubernetes
code
of
conduct
which
simplifies
to
peace.
Please
be
excellent
to
one.
Another
should
be
no
problem
for
everyone
here.
Y'all
are
fantastic.
B
Hello,
everyone
hi
happy
wednesday,
so
enhancements
is
green
right
now
we
are
tracking
34
enhancements
in
total,
with
nine
of
them
being
new
enhancements
graduating
to
alpha
15
enhancements
graduating
to
beta
and
10
announcements
graduating
to
stable
and
that's
all
on
the
enhancement,
split
awesome.
A
Dan,
I
thought
I
saw
dan
on
the
call.
A
Yet
another
good
case
for
jeopardy
theme:
song
music.
We
can
come
back
to
that.
We
can
jump
to
bug
triage
with
you.
A
Okay,
let's
jump
over
to
I'll,
give
them
two
seconds
here:
hey!
A
What's
going
down
me
perfect?
Yes,
yeah!
We
just
skipped
over
to
bug
triage,
but
yeah.
Let's
hear
from
ci
signal,
okay,.
E
So
sorry
for
the
the
microphone
issues
we
are
yellow,
so
we've
had
some
flakes
since
yesterday,
a
number
of
them
don't
look
super
critical.
One
thing
that
was
identified
this
morning
is
it
looks
like
some
of
the
cube
ctl.
E
Skew
testing
is
going
against
the
wrong
version,
so
basically,
on
those
tests
where
we're
checking
you
know
the
change
from
the
last
stable
version
to
current
and
right
now,
some
of
the
version
markers
so
the
when
builds
happen.
Basically,
they
they
publish
the
latest
version
to
a
file,
so
you're
able
to
read
it
and
download
it
and
those
look
to
be
skewed,
so
the
stable
one,
for
instance,
is
still
saying
1.17.
E
We
think
we
found
where
that
is
occurring,
but
that
obviously
needs
to
be
updated.
In
the
meantime,
we
could
update
them
to
just
use
the
latest
and
explicitly
mention
the
branch
rather
than
the
stable
and
beta
version
markers,
but
shouldn't
be
a
huge
issue,
but
hopefully
get
that
corrected
today.
E
And
then
there
are
a
number
of
tests
here
that
flight
due
to
connectivity
issues
so
not
sure
if
that's
infrastructure
related
or
not,
but
most
of
them
have
recovered
today,
and
the
last
major
thing
is:
there
is
a
fix
open
for
run,
cube
control,
applied
tests,
and
it
looks
like
I
think
that
was
approved
just
before
that
meeting
just
for
this
meeting.
So
we
should
be
seeing
green
there.
A
Signal
excellent
think
again:
dan,
let's
go
to
docs
with
anna.
F
Hey
everyone
happy
wednesday,
no
changes
in
the
doc's
world,
we
are
still
green
and
our
branch
for
1.19
is
healthy.
A
Excellent
glad
to
hear
thank
you
so
much
anna
any
questions
for
docs
all
right.
Let's
move
on
to
release
notes
with
james.
G
Hello
happy
to
report
that
we
are
green.
Both
pull
requests
for
rc4
have
merged.
We
had
a
minor
k-rub
bug
that
meant
that
a
manual
adjustment
of
the
generator
commits
was
needed,
but
we've
done
that
it
was
pretty
easy
and
we've
notified
the
relevant
people.
G
We
also
identified
that
not
being
a
k-6
org
member
on
github
meant
that
prowl
wouldn't
actually
test
one
of
them
without
someone
else
going
and
tagging
them.
Frankly,
steven
augustus
came
to
my
rescue
and
also
added
me
to
kasich.
So
it's
what
happened
again.
We
hadn't
identified
internally
that
this
is
probably
useful
for
everyone
on
the
release,
notes
team.
So
I've
got
a
pr
open
to
add
that
to
the
handbook
for
release,
notes
members.
G
So
if
people
want
to
take
a
look
at
that,
if
I
have
any
opinions,
that's
good
also
one
general
question
and
this
might
be
a
better
place
for
a
sig
release
meeting.
So
please
tell
me
to
bring
it
up
there
if
you'd
prefer
it's
about
which
exact
version
of
krell
should
be
used,
whether
we
use
the
latest
released
version
in
terms
of
github
releases
or
whether
we
should
use
the
master
branch
of
case
release.
G
The
docs
are
relatively
silent,
but
they
link
to
the
krel
build
instructions
on
master.
So
that's
what
we
used,
but
I
didn't
know
if
anyone
had
any
particular
opinions
on
this.
But
again,
I
have
to
say
that
another
meeting
of
people
prefer.
A
Yeah,
I
think
that
I
can't
remember
the
last
the
last
time
I
checked
in
with
k-ro.
I
think
it
was
0-3-3.
At
least
you
know,
that's
the
one
that
serves
that's
the
best
memory
can
do
right
now.
I
think
that
I
think
that
would
be
good
for
sig
release
and
in
determining
that
I
know,
sasha
has
worked
quite
a
bit
with
that
tool,
as
well
as
steven
and
all
the
other
kubernetes
superheroes
that
you
mentioned.
A
Thank
you
so
much
james.
Any
questions
for
release.
A
All
right,
let's
move
on
to
release
branch
management
with
carlos.
E
Rc4
was
released
successfully
yesterday
and
the
issue
we
were
seeing
before,
which
was
kind
of
motivation
for
another
rc,
was
resolved,
and
that
was
confirmed.
So
that's
pretty
much.
The
update
on
that
front
awesome.
A
All
right.
Let's
move
on
to
emeritus
advisor,
I
don't
think
tim
was
able
to
join
us
today,
my
updates,
so
we
have
quite
a
bit
coming
up
here
tomorrow
we
have
the
cherry,
pick
deadline
and
test
freeze
on
tomorrow
august
6th,
the
following
two
weeks.
We
are
going
to
be
on
a
break
for
kubecon,
so
kubecon
is
the
17th
through
the
20th,
but
the
week
leading
up
to
it
in
a
week
of
we
won't
be
having
any
meetings.
Things
will
still
be
happening.
A
Asynchronously,
I'm
certain,
so
please
be
sure
to
communicate
via
slack
and
and
any
other
asynchronous
means,
but
wanted
to
you
know
in
talking
with
steven
and
other
leads,
definitely
wanted
to
give
everyone
a
break
leading
up
to
kubecon
and
then
during
the
week
of
kubecon.
Thank
you
again
so
much
for
all
of
your
help.
This
has
been
quite
the
marathon
release.
I've
been
told
quite
a
few
times.
A
We
are
still
targeting
august
25th
as
our
release
date.
That's
tuesday.
We
will
resume
our
meetings
on
the
24th
of
august,
so
that
monday.
So
if
there
are
any
critical
issues
or
anything
like
that,
please
be
sure
to
raise
them
up
to
your
leads
or
to
us,
and
we
can
do
it.
We
can
work
with
that
and
and
get
the
comments
out
accordingly.
A
I
don't
believe
that
there's
a
skill
ability
update,
but
I
did
see
that
note
from
dan.
Thank
you
so
much
on
that
front.
Awesome
with
that.
Let's
go
into
open
discussion
and
I
believe
that
lori
might
have
an
update
there,
but
I
know
there
have
been
some
talk
there
with
using
the
project
board.
I
know
that
we're
just
about
you
know
done
with
this
release,
but
any
place
that
we
can
use
that
that
would
be
helpful
to
kind
of
see
what
still
remains
out
there.
A
If
there
are
any
critical
issues
that
come
up.
Do
you
want
to
speak
anymore
to
that
that
one
laurie.
H
Sure
so,
basically,
it's
like
all
about
the
project
boards.
Today
there
are
three
items
of
interest
to
this
group
that
I
just
want
to
update
you
all
on.
So
for
one,
the
ci
policy
improvements,
work
is
now
underway,
and
some
of
you
are
actually
claiming
items
and
getting
underway
with
work.
There
is
a
project
board
which
I've
linked
to
in
the
agenda
where
you
can
find
all
of
the
items
that
aaron
and
ben
and
others
have
spun
up
that
are
related
to
that.
First
top
priority
policy
topic,
which
is
about
the
guaranteed
qs
pods.
H
Then
there
will
be
other
issues
underway,
but
the
idea
here
that
I
think
we
all
realize
that
we
have
lots
of
work
in
progress
and
we
try
to
limit
the
work
and
progress
so
that
we
just
focus
on
one
thing
at
a
time
on
this
and
then
that
increases
the
chances
of
us
being
able
to
just
ship
it,
and
then
also
it
reduces
the
stress
for
everyone
else
like
they
have
so
many
different
topics
to
think
about
and
be
on
their
minds.
H
So,
let's
pace
ourselves
for
a
greater
sustainability
and
that
mindset
is
also
directed
to
my
thinking
towards
like
the
different
prioritization
sessions
and
the
results
of
those
sessions
that
all
of
you
participated
in.
So
basically,
today
I
sent
out
an
email
that
got
six
user
stories
related
to
some
of
the
high
priority
items
that
you
identified
as
like
things,
we
that
we
should
do
and
those
relate
to
onboarding
documentation
and
then
how
we
relate
to
each
other.
H
So,
like
the
asynchronous
team
topic,
how
do
we
make
this
team
more
asynchronous
and
then
how
do
we
actually
just
work
together
as
a
team?
And
so
if
you
look
at
that,
email
that
send
it
on
the
mailing
list,
for
this
group,
you'll
see
details
and
so
far
max
has
claimed
one
of
the
user
stories.
The
one
on
documentation
again,
my
advice
is
that
we
just
focus
on
one
or
two
of
those
user
stories
at
a
time.
H
H
H
I'm
looking
at
the
release
engineering
project
board
and
it's
the
same
situation.
There's
a
really
high
concentrated
workload
for
some
key
individuals,
and
so
then
again,
how
can
we
spread
those
efforts
more
widely
get
more
involvement
from
more
contributors
and
also
ship?
More
of
the
higher
priority
items
so
that
so
that
they
get
done
and
they
don't
linger
in
our
backlog
for
a
long
time.
H
So
the
mindset
around
all
of
this
is
sustainability
for
all
of
you
as
individuals
to
help
you
not
take
on
so
much
work
that
it
is
either
not
possible
to
do
because
there's
only
24
hours
in
all
of
our
days
or
it
creates
stress
for
you.
So
if
you
have
any
questions
or
concerns
about
that,
I'm
happy
to
discuss
with
you
individually,
but
this
is
just
a
way
to
help
us
pace
ourselves.
That's
the
intent
so
that
we
can
breathe
a
bit
sometimes
there's
just
so
much
to
do.
A
I
don't
disagree
with
that.
I
think
there
might
be
a
bug
ticket
open
for
hours
in
the
day
to
increase
up
to
48
as
well.
So
if
you
could
I'd
like
to
talk
about
that
separately,
but
yeah.
A
Thank
you
so
much
laurie.
Are
there
any
questions
for
lori?
On
that
front,
I
I
would
like
to
encourage
any
feedback
as
well
to
be
put
into
the
retro
so
that
we
can
act
on
that
and
then
kind
of
tune
those
boards
or
address
any.
You
know
just
concerns
or
items
that
we
can
get
a
little
bit
better
with
too.
That
would
be
really
helpful.
So.
H
I'm
going
to
tune
the
boards
now,
but
like
they're,
very
flexible,
so
that
you
can
spin
up
columns
and
tear
them
down.
It's
very
much
like
the
technologies
that
we
like
to
use
so
yeah.
I
will
show
it
with
to
all
of
you
like
what
I
do,
but
it's
a
work
in
progress,
cool.
A
Awesome
any
questions
for
lori.
A
One
item
I
wanted
to
address
before
opening
back
up
to
everyone:
the
release
is
drawing
close
close
to
an
end,
and
so,
as
you
proceed
through
your
weeks,
please
think
about
potential
successors
for
1.20
any
questions
on
that
front.
Obviously,
please
please
escalate
that
up
I'll
be
more
than
happy
to
talk
with
you.
A
You
know
tim,
stephen,
myself,
bob
jeremy
and
looking
forward
to
seeing
120
get
into
motion
and
119
out
the
door,
any
other
questions
comments
or
concerns
that
anyone
like
to
bring
up.
F
I
have
a
question
about
retro.
I
think
it
was
scheduled
or
it
is
scheduled
for
the
13th.
Is
that
still.
A
I
think
I
know
it's
been
changed
a
couple
times
I'll
take
a
look
at
that.
I
think
it
should
be.
I
can't
remember
if
it's
scheduled
for
the
27th
or
two
weeks
after
the
release,
I
think
it
might
have
gotten
moved
two
weeks
after
the
release,
but
I
can
double
check
on
that.
One.
C
The
the
doc
still
says
the
27th.
A
Cool
okay,
so
that
should
be.
I
think
that
should
be
okay,
I
think
there's
there
are
still
a
few
things.
I
need
to
do
there
like
a
secure
moderator
and
a
couple
items
on
that
front,
but
yeah,
I
think
20
27,
I
think,
is
it
should
be
okay,
I
haven't
heard
anything
other
otherwise
than
that
front,
but
yeah
I'd
say:
plan
for
the
27.
A
Absolutely
any
other
questions,
comments
or
concerns.