►
From YouTube: k8s 1.16 - Week 12 - Release Team Meeting 20190916
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
Hello
and
welcome
to
the
1/16
release
team.
A
weekly
meeting
today
is
September
16th.
It
is
a
Monday
and
we're
in
week
12
release
week
of
1/16.
Hurrah
just
a
reminder
that
this
is
being
recorded
and
it
will
be
posted
to
YouTube
and
all
conversations
are
subject
to
the
kubernetes
code
of
conduct,
which
states
please
be
excellent
to
each
other.
If
you're
here
and
you
have
the
agenda
up,
please
place
your
name
as
the
attendees
in
your
Associated
role.
A
A
B
A
C
So
we
are
green,
the
bright
green.
We
have
only
one
up
initially
to
the
release,
notes
normal
5
up
in
PRS,
which
is
all
relevant
to
161,
and
the
title
superiors
are
updated
to
mention
the
entities
targeting
that
risk
and
also
a
quick
update,
I
cam
nominated
jajaja
to
be
the
battery
of
lead
for
they'll,
come
on
17
release
cycle,
and
that
is
it
from
our
side.
For
now,.
A
D
A
A
A
F
F
E
A
H
A
I
I
The
to
make
sure
that
people
in
the
mentoring
they
need
and
that
people
know
how
to
mentor.
The
other
thing
is
I
want
to
remind
everybody
to
fill
out
the
retro.
We
are
going
to
be
doing
the
retro
on
Thursday
and
right
now
there
are
very
few
items
in
there
and
I
find
it
really
hard
to
believe
that
there's
nothing,
nothing
needs
improvement
and
nothing
went
wrong
and
nothing
went
well
either
this
release.
So
please
get
your
thoughts
on
there
as
soon
as
possible.
A
Thanks
emeritus
laids
release
lead
update,
I
am
going
to
set
the
status
to
green,
as
everything
is
green
in
the
list,
which
is
fantastic.
This
is
exactly
the
state
we
want
to
be
in
at
this
portion
of
the
release.
Upcoming
milestones.
This
Wednesday,
which
is
September
18th,
is
the
scheduled
one
16.0
release
day,
barring
any
critical
urgent
bugs
being
raised
in
the
next
24
to
48
hours.
That
should
not
change
919,
which
is
Thursday
during
the
kubernetes
community
call,
is
the
burndown
I.
A
Sorry
the
retro,
which
just
just
mentioned
please
go
in
set
aside
10
or
20
minutes
and
add
things
we
need
to
make
the
retro
as
fruitful
as
possible.
It
helps
people
process
what
happened
in
this
release
and
also
make
decisions
for
the
upcoming
releases
as
well,
so
extremely
beneficial
I
know
I'm
going
to
take
an
action
after
this
isn't
going
to
add
a
half
a
dozen
things
that
I've
been
taking
notes
on
over
the
release.
So
please
take
the
time
to
do
that.
There
is
no.
There
are.
A
No
other
upcoming
milestones
will
be
the
end
of
the
release.
This
Thursday
after
the
retro
and
pending,
however
long
the
retro
takes
because
we
have
split
them
before
across
a
week
or
two,
but
that
will
be
the
end
of
the
release,
which
is
fantastic.
Anything
we've
parked
for
later
nope,
anything,
that's
not
on
the
agenda.
A
Here's
the
release
team
board,
fantastic
I,
see
things
moving
as
they've
been
updated,
so
in
progress,
117
release,
team
I,
don't
think
I
need
to
go
in
there.
This
one
is
with
Jim
angel
as
Jim
on
the
callback
porting
and
defining.
There
was
a
PR
out
here
to
cover
this
12
days
ago.
Any
updates
here,
Jim
I,
will
ping
Jim
on
that
one
boilerplate
labels
to
improve
release,
notes
you
acts
with
Sasha
or
on
the
call
such
as
traveling
today,
so
he
could
make
it
no
worries.
It
looks
like
he's
done.
A
J
A
K
A
A
A
A
A
A
Ok,
so
I
guess
I
can
post
this
in
secret.
Lease
I
just
want
to
walk
through
what
the
timing
is
going
to
look
like
who's
doing
what
and
when
just
so
I
can
get
a
gauge
of
the
the
process
and
what
time
we
need
to
allocate
for
that.
So
let
me
follow
up
with
Steven
and
Jung
in
cig
release
and
see
if
they
can't
give
us
a
more
definitive
answer.
Ok,
cool!