►
From YouTube: k8s 1.16 - Week 7 - Release Team Meeting 20190812
Description
Release details: http://bit.ly/k8s116
A
Hello,
everyone
welcome
to
another
lovely
1/16
release
meeting.
It
is
August
12th
and
we
are
in
week
7.
So
I
believe
we
are
past.
The
halfway
mark.
I
am
Jeffrey
Sica
I
am
one
of
the
release,
lead
shadows
and
we
have
lots
going
on.
So,
let's,
let's
get
going
Kenny
enhancements.
Are
you
here?
I
am
here.
B
Awesome
how
it
goes
at
everyone
so
right
now,
everything's,
looking
pretty
good
I
just
go
ahead,
went
ahead
and
put
it
in
green,
because
at
this
point
nothing
is
really
outstanding.
Right
now,
that's
kind
of
crazy.
We
got
a
like
one
or
two
things
to
kind
of
cover
here,
but
at
the
moment
we've
got
40
enhancements
that
are
slated
so
19
for
alpha
11,
theta,
10,
stable
kudos
to
the
desert
team.
They
were
actually
already
closed
out,
two
of
whom
merged
and
complete
so
586
and
604.
So
that's
good
to
see.
B
1206
was
the
metrics
overhaul.
That
exception
was
approved
this
past
week
only
because
Bob
had
done
some
digging
and
kind
of
figuring
out
exactly
what's
happening
instead
of
lucky
as
well.
However,
one
thing
that's
still
kind
of
unclear
is
whether
this
is
still
just
an
alpha.
A
beta
or
a
stable
kind
of
enhancement.
So
I
put
that
on
the
issue
this
morning
waiting
back
her
response
there.
B
B
1206
is
1206
an
umbrella
for
all
this,
just
because
I
don't
want
to
keep
track
of
multiple
different
things
if
they
are
not
really
different
things
so
waiting
to
hear
back
on
some
some
of
those
pieces,
but
for
the
most
part,
everything
is
looking
pretty
good
going
into
code
freeze,
which
will
be
next
week,
I
would
say
on.
Monday
is
when
all
be
working
with
the
team
to
start
pounding
on
people
with
issues
to
figure
out
exactly
where
are
their
kkp
ours.
So
we
can
start
tracking
those
going
into
code.
Freeze.
A
Thank
You
Kenny,
two
things
quick
one
code
freeze
is
August
29th,
so
I'm
not
sure
if
it's
next
week,
I
think
it's
the
week
after
next.
That's
what
I
thought.
Yeah
I
know
it's,
but
it's
for
the
record
and
we
are
recorded
and
I
forgot
to
mention
that
we
all
abide
by
the
scene.
Cf
code
of
conduct,
which,
as
Claire
used
to
say,
boils
down
to
don't
be
a
jerk,
so
Thank
You
Kenny.
Next
up,
we
have
CI
signal
with
Veronica
hi.
C
C
We
have
nine
passing
as
well
one
flaking
and
three
failing
on
on
the
failing
side.
We
have
the
build
packages
for
Debian
and
for
rpms
are
failing
and
also
another
one
on
uncle
tests.
So
that's
basically
it
on
the
flaking
side.
Just
keep
an
eye
on
on
the
issue
that
it's
been
reported
right
there
then,
under
miscellaneous
we
have
seven
passing
and
well
an
orphaned
what
we
have
the
options
list.
So
so
far
everything
has
been
reported,
and/or
full
of
dog
so
far,
no
escalations
needed.
So
we're
we're
good.
A
D
D
E
E
Or
by
answering
it
there's
no
way,
so
we
are
currently
green
and
also
we
are
on
track
from
my
perspective
and
now
the
next
action
is
to
get
out
there
and
reach
out
some
more
please.
You
know
enactment
owners,
those
that
I
thought
implied.
That's
what
I'm
encouraging
my
shadows
to
do
now
and
give
up
get
more
updates
last
week.
That's
it.
F
A
G
Yeah
yeah,
so
yang
is
on
vacation
this
week
and
how
I
was
supposed
to
give
an
update,
but
I
just
heard
from
double-deck.
He
can't
make
it
today,
so
there
are
a
few
things
scheduled
for
tomorrow
for
branch
management.
So
the
first
thing
is
that
1.16
branch
will
be
created
tomorrow
and
the
1.16
pita
zero
will
be
released
as
well.
So
I
have
not
synced
with
yang
about
this,
but
Stephen
had
mentioned
that
he'll
be
doing
that
in
the
last
meeting.
G
I
just
sent
him
a
message
to
confirm
this,
so
I'm
waiting
for
his
confirmation,
but
I
am
guessing
he'll
be
doing
that
the
one
and
the
other
thing
is
that
one
at
12
jobs
will
be
removed
and
when
dot
16
jobs
will
be
created.
So
it's
a
new
part
PR,
so
I
like
both
I
and
Avila,
will
be
taking
care
of
it
depending
on
when
the
1.16
branches
are
created,
because
if
it's
too
late
then
you'd
be
taking
point
on
that
one
and
three
yeah
that's
pretty
much.
It.
A
H
I
think
my
understanding,
the
beta
zero
is
just
an
artifact
from
the
cutting
the
branch
process
less
than
an
actual
detestable
artifact,
although
it
can
be
used
I.
Think
of
those
two
issues
that
Veronica
had
called
out.
One
I
took
a
look
at
its
timing
out
and
has
been
over
the
past
several
weeks.
Sometimes
you
get
some
green
runs.
It's
almost
just
a
really
heavy
flake
at
this
point,
but
it
seems
to
be
continually
timing
out,
at
least
for
the
last
few
days.
H
A
A
H
I
think
we
could
probably
take
it.
Take
it
offline
I
think
we
can
continue
with
it,
but
we
might
just
see
if
we
can
finesse
or
at
least
get
some
folks
to
actually
come
in
and
take
a
look
at
this
one
so
that
we're
not
in
this
position
next
week,
because
I
think
beta
1,
I'm,
just
checking
the
calendar
goes
up
in
pretty
short
succession.
H
I
H
I
think
that
there's
a
both
good
points,
Josh,
let
me
follow
it
up.
It
looks
like
the
issues
were
raised
late
last
week
with
no
responses
at
this
point.
Let's
I'll
take
the
lead
team
and
see
if
we
can
rattle
some
cages
today
to
see
if
we
can,
if
I
figure
out,
if
somebody's
working
on
them
and
B,
if
they
can
project
when
they
may
get
a
fix,
and
then
we
can
post
in
the
sig
release
channel
whether
we
feel
it's
worth
holding
the
beta
zero
for
I.
H
I
Switch
so
just
a
reminder
to
all
the
leads
on
this
call,
and
for
that
matter,
all
the
shadows
in
this
call
is
that,
at
this
point,
even
shadows,
who
are
new
to
the
release
team
should
be
taking
on
I
doing
some
of
the
tasks
for
the
release
I,
yet
at
be.
One
of
the
things
to
think
about,
for
example,
is
having
one
of
the
shadows
present.
Your
role
report
in
the
weekly
in
the
weekly
release
meeting
as
Veronica
just
did
for
CI
signal.
I
It's
a
good
thing
for
shadows
to
do,
and
a
bunch
of
you
in,
for
example,
enhancements
and
see
a
signal
and
bug
tracking
have
the
opportunity
to,
for
example,
divide
out
following
up
with
the
SIG's
among
your
shadows.
So
you
know
please
make
sure
that
your
shadows
are
busy
and
learning
how
to
do
the
roles.
Thanks.
A
Thank
You
Josh.
Finally,
we
are
at
release,
lead
updates.
So
a
lot
of
these
we've
kind
of
already
gone
over,
so
this
is
gonna
be
more
of
a
recap,
but
tomorrow
we
are
creating
the
116
branch,
and
that
also
means
we
are
cutting
the
116
beta0
and
116
release
job-creation.
We
will
have
burned
down
starting
next
week,
but
they
are
Monday
Wednesday
Friday.
It's
not
the
everyday
burn
downs.
We
have
code
freeze
at
the
end
of
the
month,
August
29th,
since
the
last
meeting.
A
The
big
enhancement
exception
that
we've
reviewed
was
the
kubernetes
metrics
overhaul
and
we
did
approve
that
so
that
is
going
to
be
in
116
general
reminder
that
CI,
created
and
added
to
CI
is
added
and
created
to
test
grid.
Once
the
branches
cut,
we
were
kind
of
checkpointing
to
see
whether
we
were
actually
going
to
cut
the
beta
release
and
it
sounds
like
we're
probably
going
to,
but
let's
decide
tomorrow
and
as
Josh
said
start
thinking
about
succession.
All
the
leads
need
to
start
thinking
about
who
may
or
may
not
be
the
next
lead.
A
K
J
H
No
worse
him
around.
Just
one
thing
was
the
as
Jeff
mentioned,
the
addition
of
the
metrics
alcohol
just
make
sure
that
is
added
and
tracked
as
we
granted
that
exception
I
think
light
last
week,
Thursday
or
Friday
last
week,
so
that
be
it
looks
like
that's
a
big
stone
of
calms
work
that
may
need
to
happen.
It's
work
that's
been
going
on
many
releases,
but
we'll
be
ready
to
use
in
1/16.
So
if
you
have
any
questions
feel
free
to
reach
out
to
the
lead
team
thanks
so
much.
H
It's
under
sig
instrumentation
and
it's
year,
there's
an
overhaul
of
the
metrics
I.
Think
there's
some
links
there
that
Jeff
just
gave
in
his
update.
But
if
you
have
anything
specific
Kenny
or
Kenny
in
the
enhancements
team
or
the
lead
team,
can
it
can
get
you
there?
I
just
want
to
make
sure
that
one
doesn't
fall
through
the
cracks,
because
that's
been
a
multi
multi
release
piece
of
work.
That's
going
to
land
and
change
a
few
things,
so
we're
going
to
need
to
get
some
eyeballs
on
it
in
the
community
right.
A
A
L
B
I
Deagle
e
on
the
people
I've
tagged
for
reviewing
that,
in
addition
to
Aaron,
I
is
Lackey
and
the
CI
Sigma
lead,
because
a
lot
of
that
is
about
how
we
should
be
treating
master
blocking
and
master
informing.
So
please
do
review
that
material
and
I
offer
some
feedback
if
it
turns
out
to
not
be
how
you
are
currently
handling
things
or-
and
you
think
it
shouldn't
be,
how
you're
handling
things.
A
A
A
H
A
H
Feel
like
this
is
release
engineering
yeah.
It
is
tag
that
way
I'm
just
trying
to
think
so.
It
isn't.
It's
on
its
own.
Do
I
think
it
might
be
an
artifact
that
Steven
may
have
been
tracking
it
on
this
board
and
then
he's
made
the
release
engineering
board
could
see
it's
on
both
boards,
yeah
yeah
that
may
be
okay,
I'll
follow
up
with
Steven
there,
maybe
because
I,
don't
know
a
specific
role
that
is
on
the
release
team
that
needs
to
document
the
building
packaging
process
for
Siskiyou
Venezia.
Although
that
may
be
part
of.
A
I
A
A
N
N
This
question
was
internal.
We
wanted
to
push
with
a
with
a
community
I
think
there
was
some
what
about
lazy
consensus
that
was
not
documented
or
just
using
critical
for
anything
that
was
mastered,
blocking
and
then
longer
the
priority,
based
on
the
six
input
from
from
other
dashboards
or
just
need
to
document
that
for
the
ACA
Hamburg
awesome.