►
From YouTube: k8s 1.16 - Week 11 - Release Team Meeting 20190909
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
A
The
kubernetes
community
has
a
code
of
conduct
which
can
be
summarized
by
please
be
kind
to
each
other
and
treat
each
other
with
excellent
excellence
and
without
further
ado,
I
will
drop
a
lazy
link
to
the
release
team
meeting
in
the
chat
and
we
can
go
ahead
and
get
started.
Please
put
your
name
on
the
attendance
list
for
the
in
the
meeting
notes.
A
Taking
notes
is
Bob
killing
today
and
where
am
I
here
over
here
over
here
very
good.
Okay,
let's
get
started
with
enhancements.
B
Everyone,
as
per
usual
and
hands
fonts,
are
green
right.
Now
we
don't
just
fake
this,
going
away
from
green
for
the
rest
of
the
burndown
and
filled
in
and
so
we'll
just
basically
wait
on,
see,
I
signal
and
Docs
in
case
something
needs
to
be
dropped,
but
until
that
we're
gonna
be
green,
fill
the
remainder.
So
all
I
got.
C
The
other
thing
is
a
must
in
1/16
blocking
in
mastering
forming.
We
have
the
master
default
master
slow,
they
are
actually
really
really
flaky
and
they've
been
really
they've,
been
really
flaky
for
a
couple
a
for
a
couple
weeks
now,
so
we
might
been
taking
off
the
molding
them
back
into
my
master
performing
a
well
tronic
will
throw
a
couple
PR
throughout
the
place,
so
you
all
can
a
so
everybody
can
jump
into
the
conversation
but
yeah
other
than
that
a
1/16
in
in
master.
They
are
both
passing.
C
A
Great
I
have
one
question:
those
flaky
jobs
when
you
say
put
them
back
into
a
master
informing.
It
sounds
like
there's
a
history
here
of
like
these
are
fairly
new
jobs
for
master
blocking.
They.
C
They
sew
the
edge
of
the
image
that
I
mentioned,
and
they
are
the
jobs
under
the
flaky
job
section
they
are,
they
are,
they
have
actually
been
relatively
flaky,
draw
a
drought
or
released
a
always
like
30
pay,
30%
of
their
points,
fail
and
hurt
the
police
blocking
criteria,
and
we
don't.
We
don't
want
flaky
jobs
on
my
own
master
working,
so
we're
thinking
of
just
moving
they're
moving
into
mastering
forming
technically.
No.
This
is
just
this
is
just
moving
taps
around
in
discreet.
A
Thanks
for
the
clarification,
great
all
right
doing
what
other
people
have
questions.
A
E
So
we
are
getting
more
and
more
green
from
each
meeting
this
time
we
have
only
two
open
issues
and
both
of
them
are
umbrellas.
One
is
related
to
the
release,
notes
and
another
one
is
related
to
suicide
apply.
That
is
probably
going
to
be
more
soon
at
some
point
and
therefore
we
don't
have
any
of
political
traditions
and
none
of
important
regarding
PRS.
They
are
no
open,
so
it
is
minus
4.
Then
we
had
on
the
last
meeting.
E
So
you
can
take
a
look
if
you're
interested,
so
this
is
supposed
to
eat
from
our
side.
I
would
like
just
to
do
a
quick
answer
update
this
week.
I
may
be
unavailable
because
we
have
a
company
off-site,
so
I
will
be
traveling
tomorrow
and
if
there
is
anything
needed
just
being
me
and
I'll
be
like
a
shed
of
snow
or
will
ready,
write
them
to
them.
A
Alright,
any
questions
from
anyone
else.
F
All
right,
I'm
kind
of
happy
about
today,
because
we
went
down
from
16
to
2
today
is
a
deadline
yeah
today's
the
deadline,
so
we
have
about
2
PR
lives.
Now
one
of
them
just
need
like
a
technical
like
you
know,
it
looks
good
to
me
and
and
the
order
I'm
having
I
like
a
hard
time.
You
know
getting
to
respond
but
I
reach
out
to
me
like
about
Friday
or
Saturday.
A
G
F
A
H
H
Sasha
has
been
very
busy
over
the
weekend,
making
improvements
to
the
release,
notes
tool.
We
have
T
PRS
ones,
a
work
in
progress
and
the
other
is
ready
for
review
and
I've
added
those
to
the
to
the
document.
One
is
to
preserve
the
order
of
the
markdown
output
and
the
other
is
to
actually
place
the
markdown
directly
into
the
release,
notes,
template
and
then
we
are
planning
to
add
finishing
touches
to
our
release.
Notes
document
starting
tomorrow
after
kotha
and
that's
all
I
have
for
our
update.
Do
you
have
any
questions.
I
K
K
A
Alright,
so
let's
see
actually.
A
K
J
A
Alright,
very
good,
so
the
next
one
is
release
updates.
Let's
see
is
Laughlin
in
a
position
to
talk
lucky
I.
A
A
A
A
I'm
going
to
try
my
very
best
to
have
that
they'll
have
those
two
docs
PRS
merged
by
end
of
day.
How
does
everyone
feel
about
just
kind
of
playing
it
by
ear?
I,
think
everything
is
in
a
really
good,
stable
position
and
the
docs
are
moving
forward.
So
I
think
it
would
make
sense
to
observe
what
happens
throughout
the
day
and
then
basically
make
the
call
and
sake
release
channel
whether
we
want
to
make
the
RC
cut
tomorrow.
A
A
Thank
you,
everyone
so
much
for
working
hard,
I!
Oh
there's,
a
couple
of
extra
upcoming
milestones
we
would
like
to
have
code
saw
B
at
the
same
time
as
the
RTC
cut,
and
we
have
the
cherry
pick
deadline
for
116,
scheduled
for
the
12th
of
September,
which
is
Thursday,
I,
believe
any
questions
for
the
lead
team.
A
Sometimes,
silence
feels
good
all
right,
let's
check
if
anybody
has
any
concerns,
anything
that
we
forgot
anything
that
should
be
on
the
agenda,
but
is
not.
This
is
the
free
for
all
speak
now.
A
All
right
because
we
are
making
excellent
time
I
will
very
very
briefly
share
my
screen
and
pull
up
the
board.
I
know
that's
always
kind
of
a
downer
after
a
successful
status
meeting,
or
at
least
it
is
for
me,
my
god
now
it's
the
board,
but
we
are
at
twenty
past
nine,
so
yay
good
job,
everyone.
Let's
look
at
what
issues
we
have
in
flight.
A
A
L
M
A
So
please
I
implore
everyone
to
take
a
look
at
both
of
these
issues
that
I
just
pulled
up
this
one
as
well
as
this
one
and
give
some
feedback.
This
is
especially
that
second,
one
is
not
necessarily
the
thing
that
we
want
to
encourage
lazy
consensus
for
so
any
and
all
discussion
is
going
to
be
helpful
and
then
add
information
about
what
qualifies
for
a
milestone.
A
I'll,
take
a
look
at
that
as
well.
Alright,
very
good.
We
have
a
few
dues
in
this
case
I'm
just
going
to
ask
people.
It
are
any
of
these
issues.
Document
kubernetes,
release
team
membership
criteria.
As
anyone
does,
anyone
have
been
working
on
this
I
see
Laughlin
as
assigned
we
have
some
assignees
I.
A
Will
be
working
on
creating
some
documentation
about
just
like
a
glossary
of
release
terms,
codes,
code,
freeze,
code,
slashes,
not
a
thing
more
enhancement
and
so
forth,
that
is
mine
at
Mackey's
issue.
I
have
definitely
been
thinking
about
it,
but
not
physically
updated
it
release
team
survey
improvements.
This
looks
like
Josh
and
Stephen
thing,
and
neither
of
them
are
here
shadow
halo
process.
Interesting,
very
good.
Perhaps
lucky
can
update
us
on
that
tomorrow
and
with
that,
unless
anyone
is
pinging
in
here
with
some
updates
on
whether
something
is
currently
in
progress
or
off
the
backlog.
B
A
Right,
you
are
definitely
getting
out
of
your
cab
at
that
point,
so
we
have
two
dogs
PRS
that
are
blocking,
and
my
hope
is
that
they
will
be
done
by
end
of
day
so
because,
with
everything
else
being
stable,
I
would
say
that
we
ping
insig
release
channel
one
slack
by
end
of
day.
If
those
PRS
have
been
merged.
A
Great,
how
do
I
sell
cash
soon?
Oh
no
thanks.
I
For
thanks
for
chairing
the
meeting,
Gwyn
yeah.