►
From YouTube: Kubernetes 1.13 Release Team Meeting 20181119
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
B
A
A
All
right,
let
me
go
ahead
and
start
recording.
Oh,
it
was
recording.
Okay,
hello,
everybody
welcome
to
our
1:13
bun
down.
So
from
this
week
we
go
on
to
daily
bun
downs,
I've
linked
the
minutes
in
the
chat
and
the
usual
disclaimer.
This
is
being
recorded
and
it'll
go
on
to
YouTube
shortly
after
so,
please
be
mindful
of
what
you
say:
cool
with
that.
A
Let's
get
started,
so
the
state
is
for
the
release,
I'm,
still
keeping
it
at
yellow,
mainly
because
there
are
a
few
test
failures
that
we
are
tracking
and
there
are
about
close
to
nine
to
ten
pr's
that
are
in
the
critical
urgent
list
that
are
waiting
to
get
merged,
so
tracking
those
two,
those
few
things
I'm
still
keeping
the
release
at
yellow.
So,
barring
any
major
surprises,
we
should
be
able
to
hit
the
deadline
of
December
3rd.
A
We
hit
code
freeze
on
Friday
and
we
built
our
first
beta
almost
at
midnight,
so
the
bits
have
been
been
given
for
testing
I
know.
Q
Backman
folks
are
using
the
chat
release
for
the
test
right
now
tide
drained
almost
late
Friday
night.
We
didn't
see
any
major
issues
there,
but
coal
could
give
an
update
in
his
section.
A
We
are
looking
to
cut
our
next
beta
beta
2,
this
Wednesday.
If
most
of
the
again,
this
is
dependent
on
the
test
failures
as
well.
I
would
like
to
get
those
fixed
so
that
our
beta
is
closer
to
our
C
as
much
as
possible.
So
I'll
track
this
and
depending
on
when
those
fixes
land,
we
could
do
the
beta,
maybe
early
in
the
day
Wednesday
or
maybe
around
5
p.m.
PST
I'll
also
follow
up
with
Doug
on
his
availability,
but
it's
targeted
for
Wednesday
level,
2.
Anyone
20
and.
A
Yeah
dogs
and
release
knows
and
calms
just
another
standing
call-out.
The
enhancement
sheet
is
now
stable,
although
all
the
113
ones
are
listed
there
and
items
that
didn't
make
been
moved
to
114,
so
just
a
call-out
to
update
your
corresponding
artifacts
and
CI
as
such
as
looking
good
but
I.
Let
Josh
do
the
update
in
section
with
that.
If
we
don't
have
any
other
questions,
we
can
quickly
move
on
to
individual
updates.
C
Oh
code
freeze
been
to
Africa
and
into
effect
on
Friday.
As
I
said,
there
was
no
issues
with
that
and
the
merge
pool
is
drained
so
testing
for
status
is
green,
I,
don't
think,
there's
anything
else
to
update.
A
D
She
had
a
conflict
today,
but
he
shared
his
update
with
me.
He
says
everything
is
green
on
there,
a
couple
outstanding
issues
in
coop
ADM,
but
since
it's
out
of
tree,
it's
being
tracked
outside
of
the
cake,
a
repo
I
think
he
put
a
link
there
to
those
two
yeah
I.
A
A
Next
CI
signal
today
welcome
back
hey.
E
Yeah
nice
to
be
in
a
compatible
time
zone
again,
so
CIE
signal
is
looking
better
than
it
was
last
week,
but
we're
not
completely
out
of
the
woods
yet.
So
a
bunch
of
things
have
been
resolved.
Other
things
are
close
to
resolved
and
really
the
only
reason
for
not
considering
the
main
reason
for
not
considering
CI
signal
completely
green
is
just
that.
E
We
have
a
lot
of
flaky
tests,
including
a
lot
of
tests
that
are
flakier
now
than
they
were
a
release
cycle
ago
and
I
would
still
judge
I
haven't
completed
the
chronic
clicks
chart,
so
I
don't
have
the
math
on
this
yet,
but
I
would
still
judge
that
we
have.
E
You
know
somewhere
around
a
50/50
chance
that
we
will
have
a
slate
of
flakes
on
the
decision
day
for
the
release,
which
is
my
main
worry
there
right,
because
you
know
until
you
see
a
couple
of
rerun
cycles,
you
can't
tell
the
difference
between
a
flake
in
an
actual
failure
and
if
that
happens
three
days
out
from
the
release,
not
good
the.
So
a
couple
of
the
chronic
flakes
have
PRS
in
progress
to
deflate
them.
The
majority
of
them,
I,
don't
think,
will
be
addressed
within
the
1:13
cycle.
E
E
It's
just
not
fully
populated,
okay,
the
yeah,
so
I
need
to
finish
populating
it
and
then
apply
some
math
to
it.
Just
you
know
see
how
frequently
we
can
expect
to
get.
You
know
a
red
test
grid
based
on
just
having
a
bunch
of
flakes
happen.
At
the
same
time,
mm-hmm.
E
Think
I
think
there's
something
wrong.
You
notice
I
put
that
under
blockers.
Okay,
given
that
the
scaleability
jobs
have
been
flaking
more
frequently
than
they
did
for
112
and
having
the
5k
no
job
flake
a
few
times,
I
think
there's
something
wrong:
I
have
not
had
a
chance
to
look
at
the
rest
of
six
scale
abilities
test
suite.
Yet,
okay,.
A
E
The
way,
one
of
the
other
things
that
we're
discussing
on
tests
infra
is
whether
we
want
to
swap
out
some
of
those
tests,
because
six
scalability
is
telling
us
that,
because
of
the
run
link,
the
5k
node
test
is
never
going
to
be
not
flaky
mm-hmm.
And,
if
that's
the
case,
then
it's
like
well,
we
shouldn't
be
using
that
as
the
blocking
test,
so
yeah.
E
E
E
E
E
That's
that
that's
pretty
much
it
the
rest
of
this
stuff
is
on
the
notes.
There
actually
aren't
there's
a
few
failing
test
issues
open,
but
most
of
those
are
non.
Blockers
are
either
in
non
blocking
test
test
that
we
know
are
problematic,
are
not
considered
blockers
or
there's
sort
of
long-term
cleanup
issues
that
just
are
not
conceivably
going
to
get
fixed
for
113
yeah.
A
Don
kinda
updated
that
the
cubelet
one
is
just
the
test.
It's
been
one
of
the
Joker
notes
is
run
is
running
out
of
space
that
kind
of
Lee
that
test.
So
she
said
that
it's
not
a
release.
Blocker
though
she's
looking
into
it.
The
only
other
question
was
the
entry
volumes
one
again:
it's
it's
a
failure
in
the
soap
job,
any
reason
you
put
it
in
the
non
blocker
Josh
misses.
Why?
Yes,.
E
E
Know
we
will
raise
issues
around
specific
failures,
but
we
won't
block
release
based
on
it.
Okay,
it's
if
you
notice
it's
in
sync
release,
113
all,
not
saving
these
130
blocking
the
and
and
that's
true
for
everything
in
all
or
in
the
future.
Informant
right
is
the
idea
that
difference
is.
We
won't
block
release,
sometimes
failures,
unless
we
have
some
other
reason
to
block
with
these
yeah.
Okay,.
A
E
I
think
it
I
think
it
indicates
something,
but
is,
is
that
something
that
indicates
an
actual
kubernetes
failure?
Is
it
a
problem
with
the
test.
F
E
You
know
the
idea
of
the
difference
between
blocking
and
non
blocking
is
the
stuff
that's
in
on
the
jobs
that
are
non
blocking
should
be
tests
where
the
probability
of
it
being
a
problem
with
the
test
is
relatively
high.
Mm-Hmm
I,
don't
know
that
that's
necessarily
a
hundred
percent
consistently
true,
but
it's
certainly
true
for
Soph
GCE,
okay,.
A
E
E
A
Awesome
then
we
can
want
to
buck
triage
Niccolo.
G
There
are
about
ten
or
so
hours,
plus
most
of
them
moved
out
on
Friday.
That
was
quite
a
busy
day
before
Godfrey's
lots
of
things
could
merged,
and
most
of
the
remaining
peers
are
not
really
critical,
though
I
have
around
four
or
five
I
I'd
like
to
discuss
continuing
from
CI.
This
one
is
seems
to
be
fixing
a
flake,
and
this
close
to
merging.
G
A
G
It's
it's
a
it's
a
small
comment
that
needs
to
be
addressed
by
the
C
gonna
salt
station
I.
A
I
see
children
on
the
call,
so
I
know
he
was
also
an
active
reviewer
there
Jordan,
we
are
talking
about
seven
zero,
nine
three
one,
there's
a
link
to
that
in
the
chat.
H
Think
it's
critical
for
113!
If
it's
fixing
a
flake,
then
I
would
take
it
for
that,
but
otherwise
I
don't
think
it's
critical!
Okay,
but
I,
don't
know
contacts
on
whether
it
was
taking
seconds
well.
Yeah.
G
A
A
A
A
G
I
Yeah,
sir
dogs
aren't
looking
too
good
right
now,
drop
the
ball
a
little
bit
last
week,
so
unfortunately,
not
doing
too
well.
Today
is
the
completed
PR
deadline,
so
you
want
one
of
all
the
PRS
to
be
ready
for
review
today,
but
only
about
half
of
them
already
for
review.
Okay,
so
there's
there's
kind
of
three
three
problems
with
this.
I
The
first
one
is:
it's
gonna,
be
tough
to
get
all
of
those
PRS
completed
and
by
the
PR
owners,
and
then
we
have
a
short
timeframe
in
order
to
review
them
and
have
them
ready
to
be
merged,
and
it's
also
over
Thanksgiving.
So
you
know,
first
of
all,
we've
got
the
technical
technical
reviews
which,
in
the
past,
have
been
tough
to
follow
up
following
up
to
get
people
to
do.
I
The
tank
overviews
has
taken
some
time
in
the
past
and
then
we
approval
from
some
of
the
sick,
doc
seminars
and
I
think
so
so
there's
a
lot
of
following
up.
It
needs
to
be
done
in
order
to
make
sure
that
everything
there
goes
quickly.
I
think
I'd
like
to
reach
out
to
like
the
potential
reviewers
and
approvers
before
pr's
are
even
ready
for
review
just
to
make
sure
they
know
hey
you're
down
to
review
this.
Will
you
be
ready
to
review
it
once
it's
complete,
so
hopefully.
E
I
A
bit
proactive
there
might
be
helpful,
but
you
have
anybody,
has
any
suggestions
or
is
able
to
help
me
other
way?
Then
we
definitely
with
the
help
yeah.
A
A
I
also
I
was
thinking
of
sending
like
announcement
on
Cuban
adhesive
later
this
week
to
say:
hey.
These
are
the
failing
tests.
If
we
didn't
get
attention-
and
these
are
the
pending
tasks,
if
you
think
it
might
help,
I
could
send
it
out
tomorrow
if
we
still
are
not
seeing
response
in
these
dots
just
to
say,
this
is
kind
of
becoming
critical.
At
this
point,
yeah.
I
And,
and
also
you
know,
while
asking
PR
owners
to
you
know
actually
complete
their
PRS,
asking
them
to
reach
out
to
the
people
who
will
be
reviewing
and
making
sure
that
they
are
ready
to
review
as
well
would
be
very
useful
because
you
know
I
think
we
can
get
the
PRS
completed,
but
getting
it
all
refuge
in
time
is
going
to
be
very
tough.
Okay,.
A
Let's
start
with
yeah
just
put
the
list
of
the
PRS,
and
then
we
can.
We
can
first
take
them
offline
and
then
see
how
to
escalate
it.
For
that.
I
Okay,
chilling
so
beyond
that
still
working
on
some
talk
generation
stuff
asking
talking
to
some
sick
dogs
people
about
how
to
do
that
properly,
fixing
things
there
and
then
Jordan
you
do
you
want
to
speak
about
your
PR
here
for
us
to
actually.
A
H
H
E
F
F
A
E
J
A
A
Okay,
the
main
one
was
so
this
Cal
State
Friday
is
the
u.s.
holiday
for
Thanksgiving,
so
I
don't
expect.
My
plan
was
to
cancel
the
burndown
for
Thursday
and
Friday,
considering
this
is
still
in
a
stable
shape
for
the
release
itself.
But
if
non-us
our
release
team
members-
if
you
rather
that
we
meet
at
least
one
of
those
days,
I'm
more
than
flexible-
to
have
yeah
I,
really
a
burn
down
on
Friday,
we
could
also
do
an
earlier
time.
So
I
just
wanted
to
hear
if
there's
consensus,
to
having
a
meeting
on
Friday.
A
Okay,
unless
there's
no
yeah,
unless
there's
no
consensus
or
like
resounding
need
to
have
one,
then
I
will
go
ahead
and
cancel
the
ones
for
Thursday
and
Friday.
If
something
bubbles
up
and
needs
needs
us
to
scramble,
then
probably
I'll
send
out
a
notice
for
the
non-us
folks,
if
not
I'll,
go
ahead
and
cancel
the
Thursday
and
Friday
1:00
and
github
issue
for
114
release
yeah.
It's
still
up,
they've
had
a
lot
of
traffic
there
I
brought
up
the
question
I
had
here
was
mainly
for
Josh
and
Steven.
A
A
A
Cool
yeah
we
had
the
nomination
itself
and
also
for
the
shadows.
We
wanted
to
discuss
about
the
informal
selection
process
and
the
nine
things
out
there
awesome
then
I
leave
it
on
the
agenda
for
tomorrow
and
then
the
113
retro
yeah,
the
doc
is
up
still
scheduled
for
December
6th,
so
feel
free
to
add
your
feedback
suggestions.