►
Description
Kubernetes 1.18 Release Team Meeting Burndown for 20200311
A
Okay,
hello,
everyone,
my
name
is
Bob
Dylan
or
mr.
Bobby
tables
I'm,
a
really
shadow
for
the
118
release
and
we're
going
to
kick
this
off.
This
is
the
March
11th
burn
down
meeting
and
before
we
can
actually
get
started,
there's
a
few
little
housekeeping
things
that
we
have
to
take
care
of
a
the
all
of
gray's
properties.
Abide
by
a
code
of
conduct
essentially
be
boiled
down
to
you
awesome
to
each
other.
Next,
if
there
is
a
note
taker
who'd
be
willing
to
toss
some
things
in
there.
A
B
B
A
C
Everyone
on
Wednesday,
so
our
participation
is
read,
I
can
say
in
master
blocking.
We
have
this
last
job
that
was
failing
a
fixed
course
open,
it's
merged,
but
now
we
had
up
in
the
original
error.
So
I
don't
know
if
anyone
is
taking
care
of
it
as
we
speak,
but
I
will
try
to
ping
the
CLI
guys
to
check
it
out
massive
informing
the
last
part.
We
have
the
two
leaders
jobs
at
this
fairly
and
originally
it
was
failing
because
of
of
six
a
liar
but
I
support.
C
We
have
two
big
puppets
party
steps
which
is
not
so
important
which
sends
they
are
the
priority
some
time
ago.
It's
filling
because
one
party
release
see
right
does
exist
yet
bill
packets
are
failing,
which
we
notice
that
I
opened
an
issue
and
it
seems
that
Sassa
is
working
on
it
and
he
found
the
issue.
So
we
expecting
the
fix
after
the
meeting
nozzle
yeah
release
misc
we
have
four
flaky
jobs
and
one
failing
job,
which
is
the
CI
equal.
C
It's
your
backup
with
which
there
are
actually
it's
a
flake,
but
at
some
point
in
its
it
could
you
know
flagging
your
every
time,
so
in
considering
as
a
failing
as
well,
I
have
a
list
for
it
and
it's
been
not
investigated
as
well.
One
pointed
blocking
the
Q
cluster
later
see
it's
the
same
job
with
the
massive
need
for
me,
and
there
are
other
two
jobs
that
they're
started.
Failing
recently,
I
have
been
issued
for
this
day,
no
respond
yet,
but
I
I
based
the
issue
in
their
channels.
C
D
E
C
D
D
Make
sure
I'm
actually
not
as
good
as
you
were
talking,
they
verified
1:18.
One
I
was
looking
at
the
logs
in
despite
laws
and
seems
to
be
seems
to
be
the
all
the
job,
all
the
tests,
the
are
mentaly
one
are
actually
what
we
are
actually
running
to
completion
and
running
successfully
and
put.
If
you
look
at
this
with
some,
some
bronze
for
survey,
for
some
scientists
are
missing,
so
probably
so,
probably
just
need
some
time
to
to
clear
up
and
on
the
old.
The
other
comments
are
about
a
thrombosed
makings.
D
C
B
F
Hey
everyone
I'm
Anna
here
for
bug
triage,
our
current
status
is
yellow
and
there
has
been
no
changes
to
open
non-test
flaky
issues.
We
still
have
three
open
and
one
for
on
prior
to
a
critical,
urgent
and
then
asked
for
the
PRS
we're
down
by
540
kprs.
So
we
have
nine
open
PRS
and
for
a
critical,
urgent,
we're
down
by
one.
We
still
have
one
open
and
we're
down
by
two
for
the
priority
importance.
Npr's
and
altogether.
A
G
So
our
current
status
is
yellow
one
1800
beta
two
got
cuts
a
slight
I
believe,
but
we
haven't
done
the
peons
for
it
yet
so
we
just
need
to
go
through
and
generate.
Those
should
be
relatively
straightforward.
I
think
is
that
I
think
impeding
us.
We
just
haven't
done
it
last
night,
I
think:
that's
it
let
alone
any
questions.
H
Hey
Karen
here,
I
put
us
at
yellow
we're,
probably
greenish,
but
I
just
wanted
to
maybe
put
it
out
there
that
I
am
just
a
little
concerned
with
our
timeline,
given
it
took
a
while
to
reach
out
to
the
SIG's
so
hope
you
were
here
hardest
to
get
everything
in
as
soon
as
possible.
But
following
up
on
Mondays
comments,
we
are
aiming
for
a
release
by
and
then
five
feature
blogs.
H
The
idea
is
that
we'll
publish
the
feature
blogs
the
week
after
the
release.
Blog
goes
out
so
we'll
do
one
a
day.
We're
aiming
for
five,
see
how
many
SIG's
get
our
Testament
content
and
then
yeah.
So
we've
reached
out
to
the
sig
co-chairs
for
content
and
then
I
sent
out
a
blog
draft
for
the
main
release,
blog
and
I'm,
working
with
the
leads
on
capturing
some
of
the
overall
teams
and
just
yeah
major
themes
and
concepts
for
this
release.
So
yeah
we
are
at
yellow
ish.