►
From YouTube: Kubernetes Release Team Meeting 20211115
Description
For more info, see https://git.k8s.io/community/sig-release
A
Hello:
everyone
welcome
to
the
monday
november
3rd
november
15th
release
team
meeting
for
release
123..
This
is
week
13
of
the
release
cycle.
I
do
want
to
let
everyone
know
that
this
meeting
is
recorded
and
uploaded
to
youtube,
and
we
also
buy
to
the
cncf
code
of
conduct,
which
means
to
just
to
be
kind
and
to
be
excellent
to
each
other.
I'm
going
to
go
ahead
and
share
my
screen
in
the
first
thing
off
in
the
chats.
A
And
we'll
start
the
weekly
burnout,
so
this
is
the
first
week
of
monday
to
friday
daily
burn
down
meetings,
and
we
do
this
because,
since
the
as
we
we're
getting
really
close
three
weeks
into
the
release
date
of
123.,
so
we
have,
we
tend
to
have
a
lot
more
outstanding
issues
that
come
up
and
pull
requests
to
come
up
or
our
deadlines
that
come
up
so
we're
starting
tomorrow
is
the
first
major
main,
first
major
deadline
or
second
major
deadline,
so
we'll.
A
So
we
just
that
we
do
like
to
have
these
daily
burnout
meetings
to
to
address
those
issues.
I'm
going
to
start
off
with
the
open
discussion
as
usual.
The
big
thing
deadline
is
tomorrow:
it's
code
free
starts
tomorrow
at
6pm,
pacific
time
there
there
is
a
pull
request
to
k
test
infra,
which
actually
starts
code
for
use.
So
when
it's
already
made,
thank
you
now
bring
for
making
those
pull
requests
and
at
6
p.m.
Pacific.
Tomorrow
we
will
release
the
hold
on
this.
A
That
only
pull
requests
that
have
the
123
milestone
that
are
approved
and
have
the
approved
and
lgtm
labels
can
merge
into
into
into
the
into
the
kk
repo.
For
those
who
are
new,
if
you
are
not
familiar
with
the
code,
freeze
and
test
freeze
deadline
code
freeze
is
tomorrow.
A
Ten
test
freeze
is
next
week.
We
are
we're,
also
cutting
beta
the
first
and
only
beta
release
as
well,
so
starting
tomorrow
at
six
after
six
pm,
pacific
only
appears
with
the
approve
in
lg
tm,
and
they
have
the
appropriate
123.
Milestone
can
merge
into
into
kk
master.
A
Next
we
can
test
freeze
the
release.
Managers
is
they're,
going
to
cut
a
release,
dash
123
branch,
and
so,
if
any
any
exceptions
that
get
emerged
into,
kk
master
will
have
to
be
cherry
picked
into
the
release
dash
123
branch,
that's
a
little
but
more
background
info
on
that
any
comments
or
questions
about
code
freeze.
A
All
right
next
week,
once
you
once
you
release,
123
branches
created,
we'll
need
another
pull
request
to
enable
code.
Freeze
to
that
branch
now
put
an
example:
pull
request
from
120
on
there
all
right
next
topic
is.
We
had
an
exception
request
that
came
in
last
friday
afternoon
came
from
six
storage.
A
It
was
for
one
cap,
but
there
are
four
related
enhancements.
It
has
some
issues
with
that
cap
and
it's
the
csi
migration
cup.
They
don't
change
phases.
So
all
these
enhancement
issues
they
stay
in
beta.
They
just
change
the
default
behavior,
so
instead
of
default
off,
they'll
be
default
on
for
123.,
so
we'll
need
a
doc
change
just
to
update
the
feature
gates
dock
just
for
default
behavior
to
set
to
true
so
it's
4,
four
four
related
enhancements
issues
there.
A
Each
of
them
has
one
kk
pr,
which
is
the
code
related
a
pull
request.
One
of
them
is
merged,
so
hopefully
that
three
others
will
be
approved
by
6
p.m.
Tomorrow,
any.
A
All
right,
let's
move
on
to
the
updates
the
team
update
starting
off
with
enhancements
with
kevin.
C
Hey
yeah,
not
much
here,
we've
been
communicating
with
all
of
the
all
the
enhancement,
centers
and
we'll
kind
of
just
see
how
things
shake
out
tomorrow.
After
coach.
A
Okay,
cool
I
did
put
in
the
release
announcements
slack
channel,
so
I'm
gonna
send
an
email
out
right
after
this
meeting.
The
code
freeze
warning
notice
that
one
last
week,
but
it
never
hurts
to
over,
communicate
on
this.
So
in
this
I
also
want
to
add
in
some
numbers
associated
with
that,
if
you
could
take
a
look
at
the
release,
enhancement
slack
channel
just
to
confirm
the
at-risk
numbers
and
the
track
numbers
the
for
the
track
numbers.
A
A
All
right
there's
still
a
lot
of
enhancements
with
their
at-risk,
so
we
should
hopefully,
although
a
good
number
of
them
will
be
able
to
get
their
kkprs
in
all
right.
Next
is
ci
signal
with
regular.
D
Hi,
we're
still
yellow
so
in
the
master
blocking
we
have
no
failings.
This
is
just
no
changes
from
the
last
report:
six
flaky
and
twelve
passing
and
master
informing.
We
had
two
flaky
tests
that
don't
fail
today,
so
we
are
tracking
them
and
we
have
nine
flaky
and
then
passing.
D
We
also
have
a
new
project
board
where
we
are
tracking,
where
we
are
discussing
improvements
for
the
new
ci
signal,
ripper
tooling.
So
if
you
have
any
feedback,
please
put
your
suggestions.
There
thanks.
A
Yeah,
I
will
add
in
my
two
cents,
on
the
new
project
board.
Thank
you
very
much.
I
did
see
and
leo
did
put
in
the
chatted
on
the
slack
channel
that
there
was
one
job
failing
this
earlier
very
early
this
morning,
but
it
went
back
to
flaky.
A
So
hopefully
that
stays
not
failing
or
it's
flaky
all
right.
Any
comments
or
questions
for
ci
signal.
E
Sorry,
I'm
here
my
I
I
just
distracted,
so
things
are
good,
no
problems
there
I
see
there
are
like
six
important
soon
issues
and
three
emerson
prs
they're,
all
pretty
recent
in
age,
so
there's
action
there.
So
the
one
thing
I
have
to
figure
is
how
frequently
we
should
pursue
them,
because
they
are
tagged
as
important,
soon
I'll
be
talking
with
christoph
on
that
one.
But
apart
from
that,
we
are
all
good
all
right.
Thank
you
very.
F
With
chris
yeah
not
much
changed
since
previous
meeting
we're
tracking
56
enhancements,
48
need
docs,
you
can
see
nine
none
required.
Nine
drafts,
seven
ready
for
review
and
five
merged.
The
big
number
is
that
there
are
27
caps
that
are
still
listed
as
needing
docs,
but
for
which
there's
no
docs
placeholder,
and
that
has
to
be
done
by
the
18th,
which
is
three
days.
So
that's
why
we're
yellow
otherwise
integration
branch
is
healthy
and
we're
just
moving
along.
A
Thank
you
also
big.
Thank
you
to
jesse
the
docs
lead,
who
pointed
out
one
of
the
caps
might
need
an
acceptance
request,
so
that
was
from
friday.
Thank
you
dressing.
Thank
you,
chris,
for
the
update.
Thank
you
docs,
all
right.
Any
comments
or
questions
for
docs.
A
I
will
add
in
on
the
email
as
usual
as
we've
done
in
past
emails
about
the
doc's
placeholder
pr
deadline.
I
know
that's
coming
up
in
three
days,
so
hopefully
folks
will
we'll
start
creating
more
stocks
place
order.
Pr.
For
that
I
know
we
had
a
slow
increase
last
week.
So
we'll
get
quite
a
bit
more
this
week
and
do
you
want
to
make
a
note
too?
We
do
have
a
number
of
at-risk
enhancements,
so
that
might
be
associated
with
that
as
well.
G
Hello,
I've
issued
the
pull
request
for
alpha
4.
Some
commits
were
dropped
due
to
my
own
struggles
with
github's
secondary
rate
limit,
but
those
will
be
addressed
shortly
other
than
that
nothing
to
report.
A
Okay,
all
right,
thank
you
very
much
I'll.
Take
a
look
at
the
pull
request
for
alpha
4
beta0
is
coming
out
tomorrow,
so
we
get
to
get
this
approved
and
merged
as
soon
as
we
can,
after
appropriate
reviews,
all
right
any
comments
or
questions
for
release,
notes
or
lucas.
H
How
are
we
doing
with
major
themes.
H
The
I
know
we
were
kind
of
like
trying
to
get
more
feedback.
B
A
Yeah
all
right
and
let's
go
on
to
with
comms
and
mickey.
C
Hey
folks,
so
we're
waiting
on
blog
drafts
to
come
in
right
now
I
listed
the
ones
that
we
do
not
currently
have
drafts.
For
so
that's
pod
security,
admission
volume,
popular
data
source
always
on
our
pv
reclaimed,
policy,
object,
storage,
api
and
auto
delete
staples
pc
pvcs
we
reached
out
to
the
owners
from
each
team,
so
you
all
should
know
who
you
are
we're
trying
to
get
every
blog
in
by
a
week
from
tuesday.
That's
the
deadline,
which
is
november
23rd,
also
keep
in
mind
that
thanksgiving
week
is
next
week.
C
If
you're
looking
for
help
or
sort
of
guidance
on
creating
your
blog,
you
can
reference
the
two
of
those
there
we're
also
working
on
the
order
of
publishing
dates
right
now,
so
we're
ranking
the
blogs
to
figure
out
which
order
to
release
them
in
and
then
finally
we're
working
on
locking
down
a
webinar
date.
C
A
I'm
fine
with
any,
but
both
those
dates
I'll
talk
to
xander,
because
he
also
needs
to
be
free
on
that
one
of
those
dates
as
well,
so
I'll
I'll
leave
it
to
xander
on
what's
which,
which
day
works
the
best
for
alexander.
So.
A
All
right
cool,
thank
you
for
the
updates.
I
know
the
folks
who
who
raise
their
hands
and
volunteer
to
write
the
pod
security
mission,
blog
so
I'll
reach
out
to
them
and
make
sure
that
they
that
they
get
a
a
draft
prn.
So
we
can
start
with
that.
H
A
Yeah
we
actually
have
a
122
blog,
that
is
in
the
middle
of
being
reviewed,
that
we've
changed
into
just
a
regular
blog,
instead
of
being
a
feature
blog
because
it's
been
several
months
already
since
122
was
released.
Okay,
so
I
do
have
a
question
about
the
release
blog
itself.
I
know
I
know
we
tend
to
start
writing
that
draft
outs.
A
B
Yeah
good
question
we
and
roger
is
here
too.
We
started
this
kind
of
around
now,
actually,
as
as
the
themes
were
coming
together
as
we
had
an
idea
of
what
was
landing.
You
know
at
this
point.
If
things
change
they're
not
going
to
be
major
changes,
so
you
can
certainly
get
started
now,
especially
working
as
a
team.
It
can
help
just
to
have
you
know
a
week
or
so
just
to
kind
of
get
into
the
flow
of
stuff.
A
Okay-
and
I
know
that
things
kind
of
tend
to
lead
or
or
work
with
each
other
like
that,
like
the
feature
blogs
could
be
part
of
the
could
be
major
themes
or
major
themes
could
be
feature
blogs
and
vice
versa,
and
they
could
also
be
highlighted
in
the
release
blog
as
well
so
they'll
kind
of
work
together.
H
I
was
going
to
say
that's
kind
of
the
same.
I
started
probably
about
three
weeks
before
the
release,
because
everything
was
kind
of
pretty
solidified
and
then
the
only
thing
that
did
come
up,
which
I
think
now
we're
kind
of
in
front
of,
was
when
we
had
some
surprise
that
surprise,
but
a
deprecation
was
called
out
and
then
we
were
kind
of
like
oh
shoot.
We
gotta
like
address
this,
but
yeah.
I
think
you're
right
now.
It's
a
great
time
to
start
just
start
early
and
hack.
A
A
So
do
we
write
a
blog
one?
Oh,
but
there
is
actually
the
feature
blog
it's
going
to
be
about
the
migrations
of
the
csi
immigrations
as
well.
I
believe
I
thought
I
saw
something
about
that
off
too.
Oh
here
we
go
it
in-store
storage,
plug-in
to
csi
migration.
So
this
pretty
much
covers
the
the
the
flex,
volume,
deprecation
and
other
csi
and
store.
I
mean
sorry,
increased
csi
drivers
as
well
so
don't
know.
Do
we
need
a
deprecation
blog?
If
that
one
of
the
feature
bugs
kind
of
covers
it.
B
Was
just
gonna
say
I
don't
I
don't
think
so,
but
I
think
you
were
about
to
say
the
same
thing.
H
B
I
Hello,
well
we're
yellow
again
just
following
a
ci
signal
signal:
we're
cutting
a
better
release.
I
I
think
that
all
the
updates
that
I
have
for
you
today
have
been
mentioned
earlier
by
someone,
but
it's
worth
mentioning
them
again
in
case
you
have
any
questions
so
yeah
we're
cutting
our
better
release
on
november
17th,
so
we're
being
extra
careful
this
week
with
the
board
and
yep
what
else
there
are
two
failing
issues
in
muster
informing,
as
was
previously
informed
by
ci
signal,
but
they
are
being
dealt
with
currently
just
keeping
an
eye
on
them
and
also,
as
ray
mentioned,
nabarron
created
the
branch
restriction
pr
for
code
freeze
ready
for
tomorrow,
and
I
think
that's
it
for
now.
A
All
right
moving
on
no
updates
from
jeremy,
okay,
yeah,
it's
a
conflict
but,
as
jeremy
might
say,
please
add
in
any
retro
or
topics
for
the
retro.
That's
post
release
that'll
be
the
week
after
the
123
release.
So
please
add
that.
Well.
Can
we
we'll
continue
with
that
retro?
We
had
our
first
one
mid
cycle,
so
now
we
can
address
some
anything.
That's
come
up
since
then.
A
All
right,
then
my
updates.
We
will
send
out
to
code
freeze
morning,
email,
that's
going
to
go
out
within
the
next
hour
or
so
so
that
with
that,
we'll
just
warn
we'll
give
a
more
of
a
summary
of
how
many
enhancements
are
on
track.
How
many
are
at
risk
as
well,
then,
we'll
also
add
in
in
bold
the
docs
placeholder
pr
deadline.
A
That's
coming
in
two
days
after
code
freeze
and
we'll
also
mention
that
only
that
for
code
for
use
your
kk
or
your
code,
pr
has
to
be
approved
by
6
p.m.
Pacific
tomorrow
we
don't
say
merge
anymore,
because
sometimes
it
could
take
a
while
for
the
pr
team
to
merge,
and
so
we
say
approved
by
6
pm
tomorrow.
A
All
right
next
topic
is
the
major
themes
or
release
themes,
we're
still
kind
of
light
on
that,
and
I
think
we
just
need
to
start
pinging
folks
who
have
opt-in
for
feature
blogs
if
they
could
write
as
short,
two
or
three
two
three
cents
paragraph
about
their
about
the
feature,
and
they
will
make
it
into
one
of
the
major
themes.
A
They
will
also
have
a
better
outlook
after
code
freeze
as
well,
and
what
enhancements
have
made
code
for
use.
So
so
we'll
look
and
see
if,
if
any
enhancements
that
I
remember
the
leaked
shadows
and
myself,
we
had
a
little
exercise
and
we
kind
of
identified
what
the
what
we
thought,
what
the?
What
the?
What
would
make
good
major
themes-
and
we
could
see
if
those
have
made
code
for
use
and
we
could
reach
out
again
to
those
enhancement
owners.
So
all
right,
do
you
want
to
go
over
some
deadlines?
A
Some
milestones
code
free
starts
tomorrow.
It
starts
at
6pm
pacific,
as
I
mentioned.
The
next
day
is
the
123.0
beta
dot.
Zero
is
cut
and
that's
the
one
and
only
beta
release
for
for
123..
A
Then,
two
days
from
now
we
have
the
docs
placeholder
pr
deadline.
We're
still
pretty
light
on
that,
but
we
also
have
a
good
number
of
at-risk
enhancements,
so
that
will
probably
correlate
with
that.
The
next
tuesday,
which
is
a
holiday
week
for
a
lot
of
folks,
especially
here
in
the
us,
it's
u.s
thanksgiving.
A
So
we
have
quite
a
few
deadlines
on
that
tuesday.
Test
freeze
is
also
when
the
when
rc
0
is
cut
and
when
the
release
123
branch
is
cut
as
well,
and
the
release
123
jobs
are
created
as
well.
So
quite
a
few
things
on
that
day
also,
the
docs
should
be
ready
for
a
review
on
that
tuesday,
because
by
that
time
we
only
have
two
weeks
until
the
release
and
we
have
to
merge
those
docs
in
into
the
dev
123
branch
for
the
documentation
website.
A
Then
we
start
the
final
notes
to
be
released.
Final
draft
of
the
release
notes
as
well,
and
also
with
the
release
blog.
We
start
reviewing
the
release
blog
as
well,
then
the
thursday
of
next
week
is
us
thanksgiving,
which
is
a
pretty
big
holiday
for
us
folks
in
the
us.
So
I
I
will
cancel
that
thursday
meeting,
but
I'll
probably
keep
the
friday.
A
I
will
keep
the
friday
meeting
aft
after
u.s
thanksgiving
a
lot
of
folks
in
the
u.s
tend
to
have
that
day
off,
but
that
friday
meeting
is
also
the
eu
apac
friendly
meeting.
So
we'll
most
likely
cancel
this
meeting
on
thursday
november
25th
and
then
we'll
just
run
it
async.
You
could
just
add
in
your
any
if
any
issues
come
up,
just
bring
it
up
to
slack
channels
and
I'll
be
attentive
for
sure
all
right.
That's
it
for
me
any
comments
or
questions.