►
From YouTube: Kubernetes 1.19 Release Team Meeting 20200601
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
well
happy
Monday.
Everyone
again
today
is
June
1st
2020.
My
name
is
Taylor
Dolezal,
and
this
is
the
119
release
team
meeting
I
do
have
a
couple
things
for
you
here
at
the
end.
I
did
want
to
remind
everyone
that,
since
this
is
a
kubernetes
organization
meeting,
this
falls
under
the
the
kubernetes
policy,
which
simplifies
to
the
excellent
to
one
another,
and
certainly
in
these
times,
and
everything
that
we're
seeing
definitely
in
the
u.s.
really
do
want
to
dig
in
on
that
point
and
say
now
is
the
best
time.
A
Every
day
is
the
best
time
to
be
excellent
to
one
another
and
I
think
I'm
thankful
that
we
exist
in
such
a
fantastic
community
and
that
we're
able
to
work
so
well
with
one
another.
I
have
not
seen
you
know
per
se,
I'm
lucky
I
haven't
seen
any
any
situations
that
have
been
crazy
or
poor
when
working
with
with
anyone
here
or
anyone
within
the
community
and
I'm.
B
So
announcements
is
pretty
much
green.
We
are
tracking
44
announcements
out
of
that,
14
are
in
alpha,
15
are
graduating
to
beta
and
32
stable.
Apart
from
that,
we
have
got
one
exception
request
today,
so
we
would
probably
be
taking
action
on
it
soon
other
than
that
I
don't
have
any
updates
as
such.
So
if
anyone
has
any
questions
or.
C
C
We
do
have
two
failing
tests
on
master
blocking,
which
is
never
a
good
thing,
but
they
are
the
two
kind
tests
and
they
were
originally
failing
for
a
different
issue
where
they
were
having
issues
with
the
amount
of
nodes
in
the
proud
build
pool
which
I've
linked
API
very
bit
that
bumped
that
knit
those
nodes
up
and
they
were
passing
I'm
now
having
an
issue
with
some
parallel
being
both
ginko
tests
and
there's
already
a
fix
in
for
that.
So
hopefully,
we'll
see
those
resolved
shortly.
Outside
of
that,
most
else
looks
good.
C
We
do
have
some
flaky
tests,
particularly
in
informing
that
are
of
note.
The
cluster
API
tests
are
still
being
investigated
because
it's
basically
something
internal
to
how
a
cluster
API
works,
where
they're
using
the
GCP
project
named
for
how
they're
naming
basically
kubernetes
objects
and
they're
they're
running
out
of
space
and
the
amount
of
character
who
out
so
that
is
being
investigated.
C
There
are
some
four
eleven
flaky
tests.
There
are
some
misnomers
there,
because
the
scale
test,
for
instance,
run
once
a
day
and
they've
been
green
for
almost
a
week
now,
but
they're
still
showing
up
this
flaky,
I'm
so
not
too
many
worries
there
and
then
the
remainder
of
them
were
mostly
related
to
a
a
small
issue
with
Bacchus
last
night
that
has
resolved
itself
and
we're
looking
pretty
good
in
there.
We
do
still
have
the
to
failing
Windows
tests
per
usual.
I
will
continue
to.
C
Let
them
know
that
we
would
like
those
to
not
be
failing
uh-huh
and
we
will
try
to
move
the
needle
on
those
a
little
bit
outside
of
that
CI
signal.
Shadows
have
been
doing
a
lot
of
great
work
lately
documenting
the
tests
on
the
Maxtor
informing
and
blocking
boards.
So
hopefully
we
get
a
little
more
insight
to
those
I've
also
spoken
a
little
bit
about
how
we're
dividing
responsibility
there.
C
D
Happy
Monday
everyone,
so
we
are.
This
is
our
first
week
of
free
election,
we've
started
following
up
on
get
happens
like
chasing
people
giving
friendly
bumps.
We
are
a
solid
green.
We
are
seeing
overall
number
of
issues
declining
some
of
the
some
of
the
open
bull
requests
were
postponed
to
either
120
or
just
put
on
posting
differently,
but
yeah.
Overall,
we
are
green
thanks,
fantastic.
E
E
F
Having
some
issues
with
the
document,
formatting
avid
they're
not
fixed,
and
we
also
for
the
first
time
automatically
generated
the
box
release
notes
for
the
the
for
the
patch
releases
of
118,
which
were
missing,
but
this
is
the
first
time
that
we
managed
to
do
it
fully
automatic.
So
we're
very
happy
about
that
and
that's
it.
G
Max,
hey
everyone,
so
we
are
also
Queen
we're
on
a
good
track.
We
just
selected
some
potential
enhancements
for
some
future
blocks
and
comms
team
started
to
reach
out
to
the
enhancement,
owners
and
end
or
the
sigelei.
It's
basically
to
agree
whether
or
not
they
would
like
to
write
a
feature
blog
post
and
said
that
we
open
the
draft
for
the
release
block
and
why
did
the
release
lead
teams?
Team
leads
and
the
team's
itself
to
participate
in
it,
and
we
are
also
going
to
now
to
reach
out
to
the
scene.
G
Caf
also
need
to
start
already
to
communicate
about
the
potential
landing
zone
for
the
future
of
blocks
in
the
end,
because
there
will
be
a
somewhere
around
cube,
con
and
I,
or
the
the
rhetoric.
Yukon
and
I
expect
that
there
will
be
also
what
actually
a
lot
of
blog
posts,
whether
from
scenes
EF
as
well
as
from
on
the
kubernetes
block,
so
that
we
maybe
have
some
colliding
a
little
bit
with
our
future
blog
posts.
A
A
C
H
Just
a
reminder
to
the
shadows
that
the
doodle
had
gone
out
and
a
email
list
was
created,
it's
kubernetes
release,
team
shadows
and
all
the
shadows
are
on
it,
based
on
the
doodle
to
invites,
went
out
to
the
set
of
shadows
so
that
we
can
have
an
all
shadows.
Meeting
time
zones
are
hard,
so
I
guess
I'll,
just
say
these
in
my
local
one
on
June
3rd,
which
is
Wednesday
and
my
time
zone
Pacific
in
my
morning,
translate
to
your
time.
H
Zones
as
appropriate
will
be
one
of
the
meetings
and
then
the
next
one
will
be
about
36
hours
later
Thursday
evening.
June
4th
my
time,
which
is
going
to
be
June
5th
morning
for
most
of
the
people
for
whom
that
makes
a
better
time.
I
would
say
so.
Those
will
just
be
a
place
for
us
to
get
together
and
chat.
We've
been
going
through
things
a
bit
now
and
an
option
to
just
sort
of
ask
some
questions.
H
What
you've
been
seeing
in
these
meetings,
if
you
have
any
questions
or
concerns
or
thoughts,
bubble
up
ideas,
or
maybe
you'd
like
to
season
more
of
something,
just
a
an
open
forum
for
shadows?
Obviously,
in
this
meeting
so
far,
it's
been
a
lot
more
of
the
leads
talking,
but
a
space
for
for
all
the
shadows
to
chat
so
hopefully
we'll
we'll
have
some
good
conversation
in
a
couple
days
and
that's
it
for
me.
A
A
H
Can
do
a
half
hour
instead
of
a
full
hour
and
and
then
shift
over,
and
we
can
also
follow
up
asynchronously,
then
via
mailing
list
or
slacking
and
I
guess.
I
should
mention
that
too.
If
you
didn't
see
the
invite
to
check
your
email
for
the
kubernetes
release,
team
shadows,
incoming
email
or
poke
me,
tea,
pepper
on
slack
and
I
can
help
you
find
it
too.
A
Cool
I
think
it's
an
origin
yep
anyone
had
any
problems
with
that
time
zone
or
anything
or
it
it
just
doesn't
work.
Please
please
reach
out
to
me
where
your
leaves
and
we
can
definitely
get
a
doodle
out
and
figure
out
a
good
time
that
works
everyone
time
zones
are
hard.
I'll
definitely
add
on
to
that
one
always
fun.
So
my
update
some
of
the
upcoming
milestones
so
today
is
the
call
for
exceptions,
so
we'll
be
looking
at
those
kind
of
fielding.
Any
any
final
ones
coming
in
tomorrow
is
the
119.
A
Is
0
beta
1
release
very
excited
about
that,
and
we
heard
on
that
front
from
Dan
as
well,
and
then
the
next
big
update
after
that
is
race
yourself.
Code
freeze
is
coming,
which
is
going
to
be
on
June
8th,
also
very
excited
about
that,
and
it's
getting
hot
here
where
I
am
so
I'm
all
for
reducing
that
temperature
I
did
not
see
an
update
from
sick
scalability,
but
last
one
was
on
me.
She
did
make
that
lease
feel
build
jobs,
look
good
and
no
regressions
at
that
point
in
time.
A
I
A
I
Okay,
yes
right,
no
dad
I
had
my
backups,
so
I've
been
helping
out
kubernetes
for
the
last
two
months
and
my
gateway
was
looking
at
pull.
Request.
Velocity
and
I
also
was
looking
into
the
released
teens
processes,
because,
obviously
the
release
cycle
gives
all
the
SIG's
and
everyone
else
focus
points.
So
you're
shipping,
some
software,
and
so
this
tends
to
rally
people
together
and
so
I
kind
of
see.
The
full
request.
Velocity
topic
is
a
lot
of
organic.
I
If
that
makes
sense,
is
that
so
to
get
into
more
specifics
about
what
the
release
team's
doing?
What
I've
been
doing
around
your
backlog?
I
see
a
lot
of
process
improvements
and
github
issues.
Sub
project
boards,
Google
Docs
data,
just
how
many
things
are
hanging
around
these
different,
backlogs,
etc
and
I've
been
pulling
it
all
together
and
I.
Can
oh
the
hostess
disabled
attendee
screen
sharing?
You
can
just
pull
it
up
if
you
want
it's
a
stretch,
neat
that
a
lot
of
the
spreadsheet
that
a
lot
of
you
have
seen
already.
I
So
then
I
was
shared
and
it's
this
list
of
stuff.
So
basically
what
I
was
steering
this
a
lot
of
archaeology
going
through
issues,
pull
requests,
retro
of
notes,
comments,
etc
and
pulling
together
everything
that
I
could
find
that
was
open,
also
some
of
the
documentation
but
pulling
everything.
I
could
find.
That
was
pointing
toward
the
release
cycle
and
then
the
goal
here
is:
how
could
we
make
the
release?
Teens
a
happy
path
is
clear
and
flowing
as
possible,
so
you
already
have
a
lot
of
process
in
place.
I
A
lot
of
that
is
working
because
of
improvements
that
you've
made
over
to
the
past,
while
over
the
past
few
cycles.
But
you
still
have
a
lot
of
these
open
items,
and
so
then
there's
a
lot
of
them
right
so,
but
I've,
there's
probably
more
that
I've
missed,
because
there's
just
a
lot
of
things
going
on
at
any
given
time.
So
the
goal
here
was
to
well.
I
Could
we
do
an
exercise
to
first
of
all
understand
which
of
these
items
were
for
the
release
team
to
solve
primarily
and
then,
which
items
were
four
other
SIG's
or
other
governing
bodies
of
the
community
to
solve?
So
if
we
were
to
take
this
list
of
I
think
about
a
hundred
items
and
go
through
them,
the
first
time
to
kick
out
and
establish
that
boundary
of
release
team
and
everything
else?
I
How
could
you
condense
that
list
and
then
the
next
step
would
be
to
actually
look
at
the
stages
of
the
release
cycle,
where
these
items
are
supposed
to
take
place
and
to
create
Colome
I,
basically
took
your
release,
diagram
and
broke
it
down
into
the
four
primary
blocks
there.
So
there
was
these
urges
in
alphabetical
order,
but
feature
definition
feature
were
the
bugs
cycle,
fixing
my
iterating,
etc
and
then
the
release
and
then
I
also
included
a
fifth
title
for
overall
deaf
process,
which
would
be
which
would
encompass
everything.
I
So
then,
you
know
if
this
release
team
could
actually
divide
these
items
into
those
buckets
around
those
four
stages,
but
and
that's
another
way
to
organize
all
of
this
content
and
categorize
it
and
then
the
final
two
stages
would
be
where
the
team
would
actually
get
together
and
prioritize
this
work.
So
there's
all
kinds
of
prioritization
frameworks
out
there,
the
two
that
I
thought
would
be
most
useful
were
the
Moscow
method,
which
would
mean
what
is
a
must-do.
I
You
could
break
those
down
perhaps
into
smaller
chunks,
so
that
you
could
actually
achieve
part
of
the
goal
in
the
cycle
or
the
next
early
cycle,
and
then
maybe
there
would
be
more
work
to
do
longer
term,
but
at
least
you've
made
some
progress
on
that
work.
So
usually,
when
I
do
these
kinds
of
prioritization
sessions
everybody's
in
the
room
in
person,
but
this
is
obviously
a
lot
of
organizing
and
may
not
be
the
most
efficient,
effective
way
for
this
particular
group
to
do
it.
A
Absolutely
No,
thank
you
so
much
Laurie.
Does
anyone
have
any
questions?
I
think
that
the
biggest
points
around
this
are
really
to
improve
the
process
that
we
go
through
to
remove
all
you
know
as
much
toil
as
we
possibly
can,
and
just
you
know
it
make
it
easier
to
work
within
the
same
kubernetes.
I
think
that
I'm
definitely
excited
for
this
to
get
kicked
off.
I
know
that
Stephen
just
D
calmed
sig
p.m.
but
definitely
lives
on
in
spirit
with
this
project,
so
that
should
be
nice.
A
I
I
mean
I
I've
been
talking
to
folks
for
a
while,
so
I
think
when
when
could
we
possibly
actually
get
this?
Is
this
actually
something
that
the
group
would
want
to
do,
because
it
has
to
be
a
by
consensus
that
this
or
activity
that
people
have
time
to
do
it?
They
have
interest
so
I
mean
perhaps
it's
on
an
individual
basis.
Maybe
the
entire
team
doesn't
doesn't
participate.
So
there
are
there,
people
who
actually
want
supported.