►
From YouTube: Kubernetes 1.17 Release Team Meeting 20191209
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
Well,
ok,
alright
I
have
never
done
release
day
as
really
sleep
before
so
we
already
asked
us,
but
I
think
we
just
have
to
check
in
with
Doc's
release,
notes
yeah.
There
isn't
really
an
agenda
for
it
today
in
terms
of
the
other
meetings.
I
believe
we
are
going
to
we.
Actually
you
know
what
Steven,
why
don't
you
tell
the
team
what
you
did
over
the
weekend
with
the
mock
release
and
when
we
are
planning
to
cut
one
17.0.
C
So
over
the
weekend,
I
was
talking
to
him
and
on
Friday,
and
we
were
basically
talking
about
like.
Is
there
any
danger
in
pre-staging
or
release?
And
the
answer
is
not
really.
If
we
know
nothing
is
going
to
change
right
and
we
were
at
the
point
where
cherry-pick
deadlines
had
hit,
we
still
merged
some
things
in
post,
cherry-pick
deadlines,
but
they
were
urgent
things.
So
at
that
point
we
had
stopped.
We
stopped
adding
new
content
to
the
release.
C
So
it's
a
was
a
good
point
to
just
do
do
a
stage
and
make
sure
everything
was
was
clean.
So
if
you
want
to
check
out
that
issue
which
I
just
popped
in
the
chat,
that
is
the
release
cut
issue,
the
mock
stage
has
been
completed.
The
mock
release,
as
well
as
the
actual
stage,
so
we
are
ready
to
rock
in
terms
of
release
manager,
mechanics
I
just
need
to
click
the
button
that
actually
does
the
release.
C
A
A
F
We're
agreed
there
was
one
make
sure
those
like
that
was
like
keeping
me
a
little
bit
worried,
there's
like
ones
like
in
the
sick,
sick,
Network,
conformance
tests
that
like
started
to
be
a
little
that
appeared
like
several
days
ago,
and
it
started
to
be
a
little
bit
sad,
but
I
didn't
really
I
didn't
really
hone
down
anyone
from
scene
release.
Who
can
comment
on
that?
I
took
a
look.
It
sounds
to
me
more
like
a
test
in
fresher
than
like
a
real
issue.
So
I
would
say
it's
good,
but
yeah
yeah.
A
I
have
been
looking
at
the
test
over
the
weekend
as
well,
a
bug
actually
surfaced.
We
are
going
to
include
that
in
the
known
issues.
So
Chris
can
talk
about
that
and
it's
been
an
issue.
This
is
actually
a
steak
off
one,
it's
been
actually
I
did
an
issue
since
September.
So
basically
it's
not
really
really
locking,
but
we
should
look
into
that
and
make
it
a
priority
for
1:18.
Do.
G
C
F
C
A
C
Also
something
that
we
may
consider,
depending
on
the
disposition
after
a
while,
we
may
consider
removing
that
as
part
of
conformance.
So
that's
what
jordan
was
mentioning
if
you
scroll
fire,
the
channel
I
also
noticed
a
conformance
blip.
So
by
the
way
the
conformance
tests
are
triggered
to
alert
on
a
single
failure
as
opposed
to
the
standard
three
failures,
so
when
they
blip
and
they
hit
the
release
team
mailing
list.
C
That
is
something
that
we
need
to
check
out,
but
but
again
that
is
that
that's
a
flake
that
randomly
pops
up
that
is
suggests
an
actual
issue
that
only
hits
and
weird
conditions.
There
was
another
flake
on
master
blocking
for
the
conformance
test,
but
not
a
big
deal,
not
a
not
a,
not
a
deal
for
this
meeting,
yeah
it
passed
immediately
afterwards
at
9:48
or
648.
You
were
done.
A
So
again
we
have
captured
this
in
the
in
the
release,
notes
we
are
making
it
a
priority
for
118
and
we
may
consider
removing
that
test,
as
conformance
no
I.
Don't
think
this
is
release
blocking,
although
we
have
to
keep
an
eye
on
it
overall,
all
right,
let's
check
in
with
bugs
any
outstanding
bugs
in
the
117
milestone.
H
A
I
So
there
are
some
pre-release
Pia's
which
I
need
to
open,
which
will
not
take
more
than
half
and
also-
and
we
working
on
that
and
I
have
another
question:
saying:
should
I
wait
until
the
blog
PR
gets
merged?
To
start
the
dogs
release
work
or
should
I?
Do
it
first,
I
mean,
should
I
start
with
the
release,
work
first
and
then
get
the
block.
B
are
merged,
that's
actually
a
really.
A
A
A
A
C
F
C
A
J
Hey
sorry,
Chris,
isn't
it
Chris
isn't
on
I'm
covering
for
Chris
today,
so
right
now
that
it's
still
on
hold
for
the
the
sig
windows
team?
So
they
were,
they
were
sent
notification.
So
that's
the
only
reason
that
that
link
and
I
put
I
put
the
link
to
the
actual
PR
in
the
notes
there.
So
that's
the
only
thing
we're
waiting
on
on
that
hold
and
then
we'll
we'll
push
to
the
website
the
updates
and
be
released.
The
notes.
A
A
K
Know
just
waiting
for
them
to
acknowledge
if
they're
good
to
go
or
not,
they
had
a
they
started,
doing
it
on
Thursday
and
that's
for
a
couple
end
of
days
and
last
night
was
end
of
day
today.
So
we're
hoping
to
speed
them
up.
That's
the
everything
is
in
the
right
spot.
We
just
need
to
get
there.
Okay
or.
A
C
Tell
you
what
why
don't?
Why
don't
you
all
give
me
a
heads
up
when,
when
release
notes
are
done,
if
there
is
anything
pending
on
the
dock
side
to
do
before,
we
go
I'm,
sending
the
note
to
build
admins
right
now
to
get
a
time
for
for
them,
based
on
based
on
when
we
say
the
release,
notes
were
done
and
when
we
and
when
the
build
admins
are
actually
available
to
push
their
buttons,
we
can
maybe
reconvene
and
and
decide
that
we're
gonna
go
sooner.
A
It
would
be
really
fun
for
da
me
need
to
be
able
to
actually
be
awake
and
you
know
hit
the
merge
button,
so
that'd
be
cool
all
right.
Nonetheless,
I
do
want
you
to
get
sleep,
especially
on
a
weekday
night,
so
we
talked
to
in
case
things.
Do
get
later
from
your
team,
so
Dee
who,
from
your
who,
from
your
shadows,
should
we
talk
to
and
in
case
things
do
getting
it
I.
A
C
I
A
Yeah
awesome:
let's,
let's
sit
back
so
actually
we
kind
of
already
did
the
release
notes.
Update
Doc's
are
good
to
go
unless
you
tell
me
otherwise
dummy
me.
Yes,
it's
perfect
and
then
release
notes,
we're
waiting
on
sick
windows.
A
L
The
blog
post
is
good,
I
think
everyone
has
a
link
to
review
that
and
let
me
know
if
they're
happy
with
it.
We
got
a
lot
of
content
from
sex
storage
just
at
the
end
of
the
week,
so
I've
actually
split
out.
So
we
have
two
blog
posts:
go
in
life
today
to
talk
about
some
of
the
new
functionality
there
and
a
link
to
those
articles
from
the
released
which
the
CN
CF
of
Astor
we
hold
until
4:00
p.m.
eastern
North
Pacific
tomorrow
to
tie
in
with
their
media
conversations
every
surgeon
from
the
comm
site.
A
A
M
Those
third
parties
are
waiting
for
the
release
notification
from
us,
so
they
can
press
the
button
on
their
content
management
system
to
publish
their
stuff
and
it
just
it
makes
it
easier
if
you
can
forecast
to
them
like
it
should
be
around
this
particular
time
and
and
then
you
sort
of
get
a
splash
of
stuff
and
nobody
gets
a
particular
jump
on
on
things
and
the
first
on
Twitter
to
announce
type
of
stuff
that
it's
sort
of
neutral
and
it
everybody
can
publish
their
stuff
together,
sees
that
same
splash.
So.
C
L
K
A
question
on
that.
Just
to
make
sure
that
we're
you
don't
step
ahead
of
everyone.
You
talked
to
Dave
earlier
today
said:
is
okay
but
I,
just
kind
of
worried
about
the
release,
themes
that
we
have
on
top
of
the
release,
notes
if
just
to
make
sure
they're
not
covered
under
that
embargo,
I
don't
want
to
get
anyone
upset.
I
will
say
traditionally.
In
the
past,
we've
held
off
publishing,
release
notes
because
of
those
themes
until
the
blog
post
is
also
published.
Okay,.
A
That,
okay,
so
apparently,
last
time
we
pushed
it
out
right
before
the
release.
I
think
I
think
release
notes
are
slightly
different
than
a
blog
post,
because
they're
definitely
I
mean
I
feel
like
they're.
Just
part
of
the
package
really
just
like
this
is
a
feeling,
but
they're
notes
to
me
are
part
of
the
code
release.
C
A
I
think
we
can
stick
to
the
notes
and
bring
them
out
at
the
same
time.
You
know
as
soon
as
we
hit
as
soon
as
the
build
is
done.
We
hit
go
on
the
release,
notes
regard
a
blog
post
for
Eastern
tomorro
is
almost
an
entire
day
after
we
cut
the
release,
I
understand
that
people
were
being
careful
and
that
this
is
a
little
bit
of
an
unusual
situation
and
that
we're
actually
releasing
on
release
day.
A
L
F
A
this
all
sounds
like
we
should
keep.
We
should
keep
to
4:00
p.m.
as
pushing
the
buttons
honestly
just
so
people
don't
get
confused
being
like
hey
I
thought
there
was
gonna
go,
but
where
is
everything
where's
all
my
information?
So
let's
stick
to
4:00
p.m.
but
we
should
revisit
that
in
the
in
the
release.
Retrospective
I
hope
that
sounds
good
to
everybody.
L
N
Yeah,
just
a
just
a
comment
here
on
the
overall
release
process
for
the
documentation
side
of
the
things
the
past
couple
releases.
Besides
this
one
and
I'm
not
too
aware
of
the
docs
process
for
the
last
release,
but
going
back
a
few
releases,
the
blog
post
is
kind
of
like
the
first
release
for
Docs
and
kind
of
the
kickoff
of
the
release
per
se
from
a
visual
perspective.
N
But
more
so
from
the
sense
of
that
was
kind
of
our
kickoff
for
docs
is
like
we're
gonna
you're
gonna
branch
master
off
to
the
kind
of
older.
This
is
now
one.
Sixteen
going
you
know,
Sun
setting
into
the
past
we're
releasing
the
blog
as
like
the
official
kickoff
of
the
release,
we're
merging
and
the
dev
branch
and
all
the
different
features
and
changes
doesn't
matter
one
way
or
the
other
I'm
just
trying
to
get
some
general
understanding
moving
forward.
C
L
A
Have
everyone
else
come
out
tomorrow
a.m.
in
fact
that's
me
that
may
or
may
not
have
been
what
I
told
the
the
podcast
interviewers
for
the
kubernetes
podcast
I
was
like
yeah
a
Tuesday
morning
should
be
fine.
If
the
release
goes
out,
I
mean
obviously
get
in
touch
with
them,
because
clearly
I
told
them
the
wrong
thing,
but
I
would
really
prefer
that
blog
took
her
out
at
the
same
time
as
the
docs
took
like
as.
C
C
L
I
can
just
tell
them
we're
slightly
uncomfortable
delay
in
the
release
blog
by
so
long
and
that
we
want
to
push
it
out
and
if
that
may
mean
that
they
have
to
reach
out
to
you,
know
some
of
our
press
partners.
Maybe
that's
going
to
be
challenged
with
the
travel
or
commitments
or
whatever
is
happening
today.
Yes,
I
know,
Toby
asked
a
question.
Yes,.
O
A
C
We've
been
pretty
good
I
think
there
have
only
been
two
delays
in
the
recent
like
six
releases
or
so
so
I
I
challenge
all
of
you
to
one
update
your
handbooks
I'm
gonna,
be
opening
issues
for
all
of
that
stuff
prior
to
the
retrospective
and
to
really
again
challenge
the
content
of
your
handbooks
right.
Don't
assume
that
just
because
we
wrote
something
down
like
don't,
don't
stand
on
the
tradition
of
what
we
did
before
right.
These
are
we're
continually
improving
this
process,
every
release
cycle
and
it's
really
important.
C
C
Can
we
do
for
any
of
those
communications?
Can
you
include
all
of
the
release
team
leads
the
release,
team
lead
and
so
Gwen
and
her
shadows
and
then
all
of
the
cig
release
chairs
as
well.
Just
so
we
make
sure
we
have
some
continuity,
just
in
case
you
have
to
drop,
we
can
continue
the
conversation
with
them.
Yep.
C
A
C
A
Where
I'm
thinking,
though,
that,
if
we
build
at
like
12
noon
and
the
blog
post,
hits
the
shelves,
then
everyone
who
is
embargoed
on
that
is
gonna
be
like
holy
crap.
We
thought
we
had
until
tomorrow.
If
we
hit
it
at
between
4:00
and
5:00
Pacific,
everyone
else
will
already
have
gone
home
unless
you're
in
Hawaii
and
then
it
won't
feel
like.
Oh
wait,
wait.
What
is
happening.
Wait
I
just
want
to
rush
all
the
other
press.
Stop.
C
Your
yeah
I
mean
we're
already,
so
we're
already
kind
of
like
messing
them
up
right
because
they
usually
go
the
day
of
the
release
after
we
go
like
I
I
know,
because
I
I
prove
the
the
VMware
one
and
I've
drift
of
the
Red
Hat
and
chorus
ones
right.
So
like
we
go
day
of
right,
so
the
second
we
get
the
okay
from
the
release
team.
We
go
that.
C
Great,
that
is
still
true,
that
is
still
accurate
right,
because
what
we
have
done
is
release
all
of
that
stuff.
On
the
same
day,
I
believe
the
reason
that
4
p.m.
exists
is
that's
the
release
of
the
embargo
time
or
that's
close
to
the
release
of
the
embargo
time
on
the
same
day.
Now
that
we're
not
going
on
the
same
day
for
the
blog
post
that
changes
everyone's
timeline.
So,
like
our
time,
so
our
timeline
leading
up
to
the
point
where
we
release
the
blog
doesn't
matter
right
like
today,
doesn't
matter
almost
so.
C
A
C
A
B
C
That
I
haven't
been
privy
to
right,
but
this
is.
This
is
definitely
not
the
norm
right
and
it
throws
off.
It
throws
off
our
coordination
right
now,
but
as
a
result,
that
also
means
that,
when
we
push
buttons
today
does
not
matter
if
the
go
time
for
everyone
else
is
not
going
to
be
until
after
the
blog
post
gets
published.
So.
A
M
All
right,
but
really
so
I
mean
I,
think
I
agree,
partly
with
Steven's
assessment
from
the
branch
management
side,
but
I
think
this
should
the
final
column.
This
should
be
coming
from
comms
because
they
understand
who
all
they've
interacted
with
on
third-party
press
and
and
what
they've
agreed
to
for
embargoes.
G
N
M
L
So
I
doesn't
have
a
specific
answer
to
that.
When
I
spoke
to
Eli
on
Friday,
what
was
said
was:
can
we
publish
our
blog
at
4
p.m.
Eastern
on
a
tent
and
the
press
will
follow
and
I
naively
said
sure
that
shouldn't
be
a
problem
and
that
we
have
in
this
conversation,
so
I'm
gonna
have
to
reach
out
to
Eli,
see
if
I
can
get
some
time
with
them
just
now
and
see?
Can
we
just
bring
that
embargo
to
today
at
4:00
p.m.
Eastern,
I?
L
C
is
when
we
say
that
we're
going
to
push
the
buttons
right,
but
but
a
good
portion
of
those
buttons
have
already
been
pushed
right
now,
so
coordinating
with
the
with
the
build
admins
at
Google
and
seeing
when
they
are
going
to
be
available
to
push
their
buttons
will
determine
when
I
push
my
final
button
right
and
then
from
that
button
push
all
of
the
Doc's
stuff
goes
right.
So
it's
not
necessarily
gonna
be
at
4:00.
C
C
L
Ii,
like
that,
just
4
p.m.
on
Friday,
just
because
you
said
that
was
what
the
time
was
previously
I
think
that
it
was
just
a
guideline
of
roughly
at
this
time,
our
blog
of
life,
and
he
has
already
told
our
media
partners
and
such
to
keep
an
eye
on
it
around
that
time.
So
I
don't
think
it's
sentence,
doe
and
I
just
think.
It's
a
marker,
but
I'll
make
sure
that
we
can
push
that
Saturday.
Okay,.
C
A
A
Only
people
that
checked
with
me
on
communications
and
when
the
blog
post
would
go
up
where
people
that
interviewed
me
for
the
podcasts,
like
no
one
else
like
no
one
from
the
CN
CF,
like
it
said
hey.
When
should
we
do?
It
feels
weird
that
no
one
checked
in
with
the
timeline
I'm
just
curious
where
they
got
the
Tuesday
idea.
E
A
L
It's
ok,
so
I
think
that
just
been
miss,
maybe
I
just
got
my
words
wrong
there.
So
when
I
spoke
to
Eli
on
Friday
I
said
the
release
is
on
Monday
and
they
said:
ok
generally
the
release
Poseidon
4
p.m.
but
can
we
release
the
blog
on
Tuesday
at
4:00,
okay,
I'll
loop.
You
lie
under
the
email.
We
can
try
and
get
some
more
context
and
work
out
what
went
wrong.
Yes,.
C
It's
totally
understandable
for
him
to
say
4
p.m.
the
next
day,
because
that
has
been
the
standard
time.
If
it
was
release
day.
If
it's
after
the
release,
then
it
could
be
anytime
on
that
day.
Right,
so
so,
I
think
I
think
it's
just
confusion
because
it's
been
tradition,
but
the
tradition
has
only
held
for
the
release
day
right.
The
second.
A
C
C
A
C
A
C
C
A
All
right,
I
will
see
you
on
the
channels
all
day
today.
Please
ping
me,
send
me
dams,
I,
I,
don't
know
if
my
phone
numbers
on
the
contact
sheet,
but
you
know.
A
And
we
can
always
hop
on
a
zoom
chat
if
we
need
to
actually
just
talk
face-to-face,
so
this
is
going
to
be
great,
but
before
we
sign
off,
I
want
to
thank
each
and
every
one
of
you
for
all
your
hard
work.
This
release.
It's
been
a
ride,
I'm
just
so
honored
I
thought
such
a
fantastic
team.
Everyone
has
always
been
ready
to
jump
in
I
love.
The
way
that
the
shadow
process
is
just
been
super
great
for
everyone's
sanity
and
mental
health,
and
it's
it's.
A
It's
been
lovely
hearing
from
everyone
of
you
and
seeing
every
one
of
you
take,
turns
and
take
up
work
and
contribute,
and
it's
been
really
really
great
and
I'm
really
excited
for
Jorge
to
lead
118
for
the
next
release.
So
I'm
really
excited
for
the
next
cycle
to
be
in
such
good
hands.
So
thank
you
for
stepping
up
and
again
thanks
everyone.
It's
been
super
great
yay,
117.