►
From YouTube: Kubernetes 1.18 Release Team Meeting 20200120
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
C
It
going
mark
our
status
is
yellow
we're
about
one
week
from
tomorrow
out
from
enhancements,
freeze
we're
currently
tracking
41
total
items.
I
broke
them
down
into
total
tract,
so
these
are
things
that
are
like
great
to
go.
There
caps
are
in
a
good
state,
they're
ready
to
move
on
past
enhancements,
breeze,
we're
also
tracking
13
things
right
now.
One
of
them
is
probably
gonna
go
to
tracks
today,
13
things
that
don't
have
they're
kept
fully
merged.
C
C
We're
going
to
go
into
the
meetings,
a
finger,
ously
and
ask
if
we
can
get
attention
on
those
things
that
need
some
reviews
or
whatever
is
necessary
to
get
them
over
the
line
and
just
kind
of
get
a
feel
about
whether
they're
going
to
make
it
or
not.
And
then
lastly,
you'll
see
the
enhancements
freezes
January
28th.
So
we
would
really
want
to
get
these
things
to
a
point
where
they
can
be
not
exceptions
before
the
28th.
C
A
C
A
A
D
Hello,
everyone
so
yellow
again
this
week,
I
was
hoping
to
get
green
earth,
but
we
didn't
get
the
support
that
we
expected
so
master
blocking
all
jobs
are
green
one
flaky
job
as
well.
An
issue
two
over
here
masoom
informing
we
have
cost
master.
Sarah
would
like
to
put
this
on
flake
ghost.
It
fell
today,
so
I
open
an
issue,
but
I
will
good.
D
You
know
wondering
this
job
and
if
it's
like
a
flake
I'm
good
to
convert
this
to
do
a
flake
one
and
we'll
try
to
solve
the
flakiness,
so
master
reboot
that
one
okay,
that
one
is
failing
many
days,
I
tried
to
Bing
cloud,
provided
the
CP
there's
not
that
hard.
Maybe
I
didn't
gotten
any
response.
Yet
yeah
he's
been
fingered
many
times,
but
we'll
see.
D
Release
misc
all
green,
just
some
fake
zones,
one
perceives
everything
blocking
the
this
is
a
good
test
which
basically
the
same
like
the
master
reboot.
The
issues
opened
and
basically
wait
for
for
response
from
color
provider,
117,
informing
the
serial
one
and
the
other
one
pulse
ability.
It's
like
the
same
issue
with
the
master
reforming
once
and
DC
Windows
compulsive
18,
no
response,
yet.
Actually
they
I
opened
a
zoo
today,
so
I'm
expecting
any
response.
I
will
try
to
ping
them
on
again
later.
D
However,
we
in
this
release,
we
try
to
focus
more
on
flaky
jobs
as
well.
We
have
some
some
misses
for
already
opened
and
we
keep
tracking
them
and
we
try
to
remove
the
fragments
that,
by
the
end
of
the
release,
we
will
to
some
progress.
There
are
some
open
issues
about
the
serial
MD
boot,
which
is
also
failing
as
well,
but
it
seems
that
there
are
other
test
cases
that
are
really
flaky,
so
we
really
wants
to
prevent
them
from
playing
and
pretty
much
that
so
any
question
guys.
D
D
We
have
like
four
or
five
issues
I
can
just
set
here,
but
I
think
it's
not
important
right
now
for
to
keep
them
right
in
here
right.
So,
but
we
wish
we
are
trying
to
get
response
from
there
as
well.
You
know
to
remove
the
flakiness,
especially
for
the
personal
needs,
because
they
are
most
important
right.
Yeah.
A
D
D
D
It
certainly
sure
yeah
yeah,
actually
I
open,
at
least
yesterday,
because
actually
I
was
trying
to
get
everything
sorted
there.
It
seems
that
seven
is
working
on
on
the
fix,
but
I
I
really
want
to
have
an
issue
open
just
to
track
them
down,
and
let
me
try
actually
to
fight
it.
I
think
that
I
face
it,
and
actually
this
is
like
really
happy
to
hear
this
report
actually
yep.
D
We
don't
need
to
do
anything
right
now.
Actually
there
are
two
PR
serpent
and
those
jobs
are
going
to
be
changed
and
also
the
naming
and
some
of
them
will
be
removed
right
now,
we're
waiting
for
those
to
be
ours
to
be
merged
and
then
we'll
see
if
they're
putting
aside
okay,
but
they
have,
but
we
it's
really
nice
to
have
an
issue
just
to
shut
them
down,
because
there
are
so
many
jobs
there.
D
D
I
tried
to
ask
Sivan
about
the
job
that
you
asked,
because
the
other
dashboards,
which
is
on
job
configures,
that
are
like
from
1.12
and
1.13,
which
doesn't
make
any
sense,
because
we
just
recently
delete
all
the
one
points
14
right,
so
it
doesn't
make
an
assist
to
keep
the
tracking
with
the
previous
releases
as
well.
I
guess
series
is
not
online
today
because
of
the
purple
day.
I
would
be
waiting
for
him
to
just
confirm
if
we
need
those
jobs
or
not.
Otherwise,
we
are
going
to
remove
them
as
well.
Yeah.
A
D
Also
one
more
thing:
it's
worth
mentioning
that
there
are
some
jobs
that
were
failing
during
the
previous
week
and
it
was
a
big
cross
actually
I
reached
out
the
testing
team,
and
it
seems
that
there
were
some
issues
with
a
infrastructure.
Bosco's
was
having
some
bad
times,
so
we
have
like
a
really
big
break
down,
but
nothing
critical
happened.
Sick
testing
team
was
able
to
resolve
a
sue
in
a
period
of
some
hours,
so
everything
went
well.
So
what
mustard.
D
No
I
don't
think
so
that
there
is
an
issue.
Actually
everything
up
is
so
quick,
I
didn't
ask
for
inserts.
We
didn't
actually
before
I,
tried
to
open
some
issues
about
the
failing
jobs,
but
because
there
was
to
say
a
specific
pattern:
I
tried
to
ask
sick
testing
team
and
it
seems
that
they
were
working.
Maybe
there
is
an
initial
opening
testing
fra,
I
didn't
say,
but
after
the
meeting
I
will
try
to
take
it
out.
Maybe
it's
good
to
have
issue
in
our
history,
because
maybe
it
will
happen.
I
can
write.
A
B
So
this
is
you
for
triage,
giving
the
weekly
update,
and
so
once
again
our
current
status
is
green,
not
because
the
numbers
look
particularly
good,
but
because
we're
still
early
in
the
release.
So
we
are
currently
with
51,
open,
non
test
or
flake
issues
and
with
about
50
peers
and
overall
75
open
issues
for
118th.
B
So
in
this,
in
this
milestone
and
like
I,
said
we're
not
worried
with
these
numbers
at
this
stage
of
the
release,
we'll
start
pinging
open,
open
issues
and
PRS
towards
the
middle
of
the
release
about
you
know
at
about
week,
six!
So
right
now
we
are
having
setting
up
our
ways
of
working
and
we
will
have
the
shadow
orientation
session
tomorrow
yeah
and
we
will
try
to
come
up
with
ideas.
How
can
we
improve?
E
Everyone,
so
we
don't
have
any
major
update
at
this
point
of
the
release.
We
are
just
waiting
for
the
enhancements
please,
and
we
are
done
with
the
shadow
orientation
last
week
and
I'm
working
on
the
branch
sync
ups
like
a
released
1.17
and
master
and
their
1.18
branching
cups.
Yes,
we
are
right
now
our
current
status
is
cream.
That's
it
folks.
Thank
you.
Thank.
A
A
F
As
a
point
of
information,
there
was
a
pull
request,
which
is
emergent,
release,
notes,
tool
which
changes
how
we
group
the
release,
notes
from
grouping
via
sake
instead
of
grouping
via
kind,
so
API
change,
but
application,
etc.
Our
intention
at
this
moment
is
to
use
this
newer
version
of
a
tool
files,
starting
from
tomorrow
onwards,
from
4
to
1
words
in
esterday
particular
objections
to
us
doing,
certainly
which
cooking
scalable
version,
but
that's
it
for
me.
I
think.
G
A
I
A
G
I
just
want
cause
I
just
want
to
make
sure
that
tomorrow,
when
8.2
or
when
alpha
2
releases,
we're
gonna
be
using
new
version
of
released
notes,
so
that
there'll
be
a
fundamental
change
on
anybody
who's
reviewing
that,
instead
of
listening,
buy
a
cig,
it's
going
to
be
now
listing
by
by
kind
instead.
Based
on
that
on
that
goal,
was
that
so
we're
gonna,
the
PR
will
be
cut
with
that
new
way
of
doing
it,
but
we're
still
going
to
be
pulling
from
that.
G
I
G
A
G
H
A
J
A
I
A
Okay,
thank
you
very
much
for
that
clarification
and
moving
on
to
emeritus
lead.
Lucky
I.
Don't
think
it's
present.
So
let
me
go
to
the
Eliminator
the
update
some
role
late
to
hold
shallow
orientation
car
with
shadows
before
end
of
week.
This
week
it
seems
to
be
seems
to
be
the
case.
Shadow
orientation
has
already
happened
for
most
groups.
A
Next
topic
meet
release
cycle
shadow
survey.
A
survey
will
go
out
the
shadows
around
week.
Six
together
value
feedback
butter
will
feedback
on
their
shadow
experience.
Okay,
so
I!
Guess
that's!
Okay!
That's
a
big
thing!
If
there's
gonna
be
a
shadow
survey
survey
going
out
I'm,
what
is
it
three
to
eight
to
three
weeks
so
stay
tuned
for
that
and
anyone
has
any
questions
from
any
of
them
before
I
before
I.
Carry
on
with
my
update.
A
Okay
I
see
nothing.
So
let
me
move
on
so
R
at
least
lead
update,
yeah
big
thing
in
the
in
the
release
meeting
notes
under
my
updated
verb
at
the
very
first
topic.
Please
go
to
that
little
and
send
it
to
all
a
to
all
of
your
shadows
or
your
variously
orange
or
lead
if
he
or
she
is
the
present
or
they
the
doodle
is
connect.
A
So
please
look
at
the
total
as
a
passer,
a
passing
along
to
everyone
it
where
everybody
within
your
group
and
I
will
try
a
tentatively
I'll
close
that
the
rule
by
Wednesday
or
early
Thursday
morning
in
Santa,
and
if
there
is
a
new
time
that
works
better
for
everyone
I'll
a
a
lot
a
day.
We
immediately
the
meaning
time
for
for
next
week
and
moving
forward
other
than
that
all
the
important
things
other
way
have
already
been
mentioned,
so
they
released
a
release,
notes
craft,
it's
gonna,
that's
a
that's
a
way.
A
A
A
There
is
an
issue
for
close
to
a
cluster
swelling
a
remaster
rolling
during
the
master
wall
in
upgrade
and
I.
Believe
there
is
a
fake.
The
fix
is
a
pending
to
be
merged
for
for
118,
and
this
is
the
block.
This
is
a
blocking
issue.
There
is
another.
There
is
another
issue
related
a
related
to
the
burn
to
the
performance,
a
dashboard,
that's
color,
the
scalability
scalability
uses
both
a
as
they
mark
this
one
as
not
release
blocking,
which
kinda
make
sense.
A
If
it's
a
performance
aspiration
but
other
than
that,
I
don't
see
any
particular
details.
Should
we
mention
during
a
during
this
call
anyone
does
anyone
want
to
add
any,
how
many
more
have
any
more
information,
what
a
other
than
those
two
issues
or
how
many?
How
many
questions
about
those
two
issues.
A
A
And
I
guess
that's
it.
For
today,
last
week
I
mentioned
that
we
were
gonna
start
with
the
project
board,
put
a
it's
a
holiday
for
some
people,
a
for
some
people
in
the
world
and
we
might
not
have
a
definitely
a
lot
of
issues
are
assigned
to
a
scientist.
Ta
Steven
team
and
a
lot
of
people
are
not
here
so,
let's
hold
on
let's
hold
on
for
this
one
until
next
week.
A
I'll
try
to
do
this
synchronously
and
if
anybody,
if
anybody
wants
to
join
with
some
issue,
triaging,
you
are
more
than
welcome
to,
and
you
know
we
we
just.
We
just
need
to
keep
all
the
communication
within
the
sig
release
channel,
so
everyone
a
so
everyone
can
find
it
either
that
were
just
coming
on
the
issue
itself
and
being
whoever
is
assigned
or
not
assigned
to
it
and
yeah
whatever
than
that.
If
no
one
has
any
more
comments,
questions
for
this
meeting,
let's
call
it
Thank
You
param.