►
From YouTube: Kubernetes Release Team Meeting 20211110
Description
For more info, see https://git.k8s.io/community/sig-release
A
It
start
that
recording
okay,
so
I
want
to
welcome
everybody
to
the
november
10th
2021
meeting
of
the
release
team
and
just
we're
going
to
go
through
today,
agenda
and
we'll
start
with
the
open
discussion,
as
we
know
we're
getting
now
really
to
the
kind
of
meat
of
the
release.
This
is
when
things
really
start
to
get
busy
for
a
lot
of
a
lot
of
the
teams.
Now
I
know
early
on,
it's
always
like
enhancements
and
a
few
other
things.
A
I
get
a
lot
of
the
action,
but
now
this
is
where
it
all
kind
of
comes
together.
So
just
a
reminder
that
code
freed
is
coming
up
really
shortly
and
so
just
expect
things
to
really
start
to
pick
up
and
as
a
way
to
kind
of
optimize
things.
Rey
has
reached
out
to
all
the
release:
shadows
myself
and
everybody
else
who
are
shadowing
this
cycle.
A
few
of
us
all
have
different
backgrounds
across
different
parts
of
the
release
team.
The
great
thing
is
we.
A
We
have
a
really
strong
team
this
time
around
and
we're
just
getting
great
feedback
that
you
know.
Release
feeds,
feel
really
supported
by
the
teams
and
that's
awesome
to
hear,
but
as
it
does,
as
things
get
go,
get
a
little
bit
more
hectic
things
come
up.
You
know
we'll
start
seeing
exceptions,
we'll
see
all
these
other
things
so
we'll
be
really
trying
to
step
in
and
just
trying
to
help
facilitate
and
be
able
to
make
things
as
smooth
as
possible.
B
Hi,
this
is
laura,
I'm
a
enhancements
shadow,
I'm
speaking
for
the
team
today,
because
xander
has
a
conflict.
B
B
For
enhancement
screens,
we
started
reaching
out
to
enhancement
owners
to
remind
them
of
the
upcoming
code
freeze
on
github,
and
then
we
have
our
tracking
sheet,
which
is
also
where
we're
tracking,
whether
any
caps
are
not
code,
priest
ready
if
they're
at
risk-
and
we
expect
that
to
keep
keep
pinging
about
that
and
updating
that
tracking
sheet
over
this
week.
So
these
numbers,
these
metric
numbers,
might
change
a
bit
as
time
goes
on,
but
yeah.
So
that's
that's.
The
update
from
us.
A
C
I'll
give
the
update
so
for
master
blocking.
We
have
one
more
job
passing
since
the
last
report
and
one
less
flaky
job
and
out
of
all
the
flaky
tests.
One
was
consistent,
so
we
have
created
an
issue
for
that
a
couple
of
days
ago
and
I
have
again
also
today
pinged
in
the
signal
channel.
So
we
are,
we
should
expect
a
response
before
the
cut
next
week
and
for
master
informing.
C
Then,
thanks
to
everyone
who
helped
with
that
and
further
developments
on
the
tool
would
be
like
we
will
try
to
keep
most
of
the
discussions
in
the
release
engineering
meetings
which
happen
since
this
is
tool
related.
So,
if
folks
are
interested
in
contributing
it's
highly
encouraged
like
you
can
show
up
there.
C
A
Yeah,
I
know
it
was
great
to
see
quite
a
few
people
in
sig
release
meeting
yesterday.
Maybe
for
the
broader
team,
like
you
know,
can
you
ex
just
briefly
explain
like
what
what
this
means
for
everybody,
because
sometimes
I
think
other
teams
don't
have
context.
C
So
yeah
the
tool
is
used
to
generate
the
weekly
reports.
You
see
in
the
release,
ci
signal
channel
and
the
earlier.
The
tool
was
under
the
private
repository
of
a
contributor,
and
now
it
has
been
merged
in
the
k
release
repository
and
what
this
would
mean
for
us
is
like
now.
It
is
governed
by
the
kubernetes
code
of
conduct
and
it
will
go
through
all
the
processes
which
other
area
areas.
C
The
repositories
go
in
the
project,
and
this
means
that
we
can
we'll
now
have,
first
of
all,
like
reviews
from
k,
release
maintainers
and
we
can
iterate
and
improve
the
tool
better,
and
we
have
like
plans
in
progress
for
linking
it
to
automating,
slack
updates
and
stuff,
and
we'll
now
be
able
to
do
that.
A
Awesome
thanks
so
much
that's
really
a
great
work.
I
think
jeremy
just
linked
in
an
example
for
others
to
take
a
look
at
as
well.
I
always
found
like
these
are
always
great
when
you're
on
the
release
team
to
sometimes
you're
in
your
space,
but
always
taking
a
look
at
what's
happening
around
it's
really.
It's
really
helpful.
When
you
see
the
bigger
picture
so
great
work.
I
really
really
excited
to
see
all
this
work.
That's
happening
in
this
in
the
ci
signal
team.
D
Exactly
no,
this
is
christopher
from
the
for
the
update,
hello
and
welcome.
So
the
too
long
didn't
read
for
the
bactriash
team
is
that
our
current
status
is
green.
We
have
no
blocking
issues.
No
blocking
pr's
out
of
17
open
issues
assigned
to
123.
We
have
still
six
remaining
that
are
currently
considered
as
important.
D
We
have
currently
two
important
npr's
open,
nothing
critical
at
this
moment
and
therefore
yeah.
We
consider
this
as
we
are
kind
of
on
track,
we're
looking
for
the
yeah
for
the
for
the
code
freeze,
where
we
assume
that
a
couple
of
issues
will
be
either
moving
to
version
1.24
or
yeah,
hopefully,
also
our
about
to
be
resolved.
A
E
For
the
update,
hello,
yeah,
so
we're
remaining
yellow
but
we're
cautiously
optimistic.
We
had
a
bunch
of
pr's
come
in
and
not
just
placeholders.
We
have
like
six
ready
to
go
almost
stock
things
it's
very
exciting,
but
we
still
have
like
30
missing,
so
we're
still
yellow,
hopefully
with
some
of
the
communications
going
out
and
some
of
the
pinging
that
we're
doing
and
others
are
doing,
we'll
we'll
see
more
come
in.
We
are
like
I
don't
know:
what
is
it
eight
days
from
the
deadline?
E
Yeah,
okay,
so
and
again,
I
just
wanna
be
very
clear:
the
communication
is,
the
team
is
yellow
we're
feeling
a
little
like,
I
wouldn't
say
worried,
but
we
are
concerned
about
the
tight
turnaround,
so
getting
placeholder
prs
in
is
one
thing.
E
We
don't
have
a
whole
lot
of
time
until
the
ducks
have
to
be
done
and
reviewed.
So
you
might
hear
some
hollering
we'll
we'll
we'll
make
it
happen,
though.
I'm
feeling
good
all
right
with,
but
yellow.
A
Okay,
all
right!
Well,
I,
like
the
cautious
optimism,
that's
always
good
and
as
we
mentioned,
it's
probably
gonna
be
a
little
hectic.
Great
thing
is,
you
do
have
a
lot
of
people
who've
worked
along
with
docs.
Is
there
anything
that
broader
teams
can
do
to
signal
boost
or
to
to
help,
or
do
you
feel
like
going
into
the
next
eight
days?
A
team
feels
like
you've
got
a
point.
E
What's
been
going
on
is
is
good,
so
yeah
and
the
team's
awesome
too.
All
the
shadows
are
super
engaged,
so
we're
we're
ready
for
it.
We
just
we
just
want
to
be
really
transparent.
All.
F
Questions
or
comments
from
anybody
for
the
docs
team
yeah,
just
one
we're
gonna,
send
out
another
email
to
the
community
next
week
and
I'll
talk
about
this
a
little
bit
and
we
will
include
a
you
know.
The
bolt
headline
get
your
talk's
placeholder.
Maybe.
G
Cool
I'm
just
curious
about
the
deadline.
I'm
talking
about
eight
days
deadline.
I
thought
the
dog
freeze
deadline
is
like
a
week
after
code
phrase.
It's
my
memory
role.
F
Well,
the
placeholder
pr
deadline
is
two
days
after
code
freeze,
but
you're
right.
I
think
the
docs
ready
to
review
is
about
eight
days
after.
E
A
G
Oh
sure,
so
I
put
it
as
yellow
because
one
of
our
shadows
is
you're
working
on
generating
a
release.
Note
for
offer
fall,
but
we'll
be
expecting
the
pr
to
be
coming
out
anytime
soon.
So
yeah.
A
H
Hello,
our
current
status
is
green.
We
have
several
feature
blogs
in
progress
and
the
shadows
are
working
to
coordinate
those
and
make
sure
that
they're
coming
along
smoothly.
We
asked
and
confirmed
a
pushback
of
the
release.
Webinar
to
january,
though,
we
need
to
wait
for
the
q1
webinar
signups
to
open
up
in
december,
and
the
team
still
needs
to
discuss
at
the
order
and
timeline
for
those
feature
blogs
to
be
published,
but
they're
in
progress.
A
Okay,
I
love
seeing
the
green
and
I
did
take
a
look
and
looks
like
you
have.
You
know
quite
a
few
feature
blogs
so
excited
to
see
how
that
shapes
up.
I
know
myself
and
max
as
well
have
worked
in
that
space.
So
if
there's
any
additional
eyes
needed,
you
know,
like
any
feedback,
we're
always
eager
to
assist,
so
don't
hesitate
to
reach
out
any
questions
for
the
comms
team.
F
One
tomorrow,
just
just
give
me
some
context:
the
initial
date
for
the
release
webinar
was
actually
the
day
after
the
schedule
release,
but
most
of
the
time
it's
usually
the
month
after
case
you
know
we
never
know.
So
we
did
ask
for
that
that
little
delay
for
that
webinar.
A
I
Hello,
well,
we
don't
have
a
lot
of
new
things
to
to
report
for
today
there
are
a
lot
of
things
happening
in
the
background
we
recently
got
the
cherry
cherry
picks
that
I
mentioned
last
meeting
approved.
I
Let
us
know
if
you
need
any
help
with
anything,
especially
since
all
the
code
freeze
and
all
these
deadlines
are
are
coming
and
just
keeping
an
eye
on
the
on
the
issue
that
ci
signal
opened
and
yeah
we're
yellow,
but
just
because
we're
very
close
to
cutting
our
first
beta
for
for
this
release
and
yeah,
but
very,
very,
very
happy
that
there
are
non
blocking
jobs
for
now
knocking
on
wood,
very
that
it
tastes
like
that.
But
yeah
should
anything
happen.
A
I
J
Hey
everybody,
I
hope,
everybody's
having
a
good
wednesday,
we're
getting
towards
the
end
of
the
release.
Like
obviously
code
freeze
is
coming
up
and
all
of
the
other
deadlines
that
kind
of
stack
after
that,
so
it
gets
to
be
a
little
stressful.
You
need
any
help
reach
out
the
the
release
leads
and
sig
release
leads
are
here
to
help
you
be
successful.
J
If
you
need
anything,
let
us
know
as
we
get
towards
the
end
of
the
release
like
one
of
the
fun
things,
maybe
not
fun
things
depending
on
your
perspective,
is
giving
the
update
in
one
of
these
meetings
for
your
sub
team.
If
you
haven't
done
that
yet
as
a
shadow,
it's
a
great
opportunity
to
do
that
in
the
upcoming
weeks,
just
to
get
comfortable
with
it.
J
If
you
step
up
to
be
a
lead,
you'll
obviously
have
to
do
that,
so
it's
like
just
good
practice
and
a
good
way
to
get
get
some
time
on
camera.
With
that
in
mind,
also
start
thinking
about
the
next
release.
If
you're,
currently
a
shadow
and
you're
interested
in
leading
your
sub
team,
it's
good
to
start
having
conversations
with
them
to
say:
hey,
I'm
interested
in
this
if
you're
not
but
you're
interested
in
another
team
do
that
as
well.
J
People
can
come
back
to
shadow,
same
teams
as
well,
so
just
kind
of
think
about
what
you
want
to
do
same
thing
for
the
release
leads
if
you're
interested
think
about
what
you
think
secession
looks
like
for
the
next
release,
just
so
that
we
can
ensure
that
we
have
a
smooth
transition
to
124
at
the
start
of
the
year,
and
and
just
I
guess,
any
questions
or
concerns
feel
free
to
reach
out
I'm
on
slack
all
the
time
the
sig
release
leads
are
also
available.
J
If
you
don't
feel
uncomfortable
coming
to
me,
steven
or
adolfo
or
carlos
or
sasha,
everybody
is
willing
to
help
out
and
listen
so
feel
free
to
reach
out.
If
you
have
any
questions
or
concerns
helpful
comments
or
whatever
happy
to
listen
to
them
all,
but
yeah
like
as
we
get
up
to
those
those
milestones,
don't
stress
too
much.
A
Thanks
for
that
update
jeremy
and
appreciate
how
you
are
continually
trying
to
make
this
a
safe
space
for
everybody
to
feel
comfortable,
especially
as
we
get
into
this
little
bit
stressful
time,
hey
just
one
follow-up
from
monday.
I
brought
this
up.
Is
any
any
comments
about
the
mid-cycle
retrospective
that
you
wanted
to
bring
up
or
anything
post
and
as
well
as
like
getting
ready
for
our
final
retrospective,
whether
this
release
cycle
any
any
comments
or
feedback.
J
Yeah,
I
think
that
the
mid
cycle
thing
was
cool.
It
was
the
first
time
we've
done
it
and
I
think
it
was
really
cool
for
two
reasons.
One
like
one
of
the
problems
that
I
think
we
have
with
the
retros
is
they
always
happen
at
the
end,
and
people
are
kind
of
burned
out
or
are
tired
from
the
release,
and
they
may
not
come
back.
They
may
come
back
depending
on
what
they
want
to
do.
J
So
we
come
up
with
all
these
action
items
of
things
that
like
didn't,
go
so
well
that
we
want
to
do
differently
next
time
and
sometimes
those
things
fall
out
and
get
forgotten,
and
I
think
that
having
the
retro
in
the
middle
was
a
good
opportunity
to
kind
of
force.
Some
of
those
things
back
to
the
surface.
J
I
think
we
had
some
good
discussions.
Hopefully
it
sets
the
tone
for
people,
so
I
don't
know
if
the
meeting
was
posted.
Yet
we
have
been
having
tons
of
problems
with.
F
J
Is
the
recordings
for
the
meetings
going
to
youtube
like
you
would
think
in
the
year
2021?
That
would
be
a
pretty
solved
thing,
but
we
have
this
really
great
integration
with
this
tool
called
splain
and
it
breaks
all
the
time
and
getting
it.
Reinstalled
is
like
a
huge
hassle
but
taylor
anybody's
familiar
with
taylor.
The
119
release
lead
one
of
the
great
release
associates.
J
He
has
just
gotten
it
working
again,
so
hopefully,
starting
with
this
meeting
it'll
be
posted
up
and
we're
burning
through
the
backlog
of
all
the
old
meetings
to
get
them
up.
So
if
you
didn't
get
a
chance
to
join
the
retro,
definitely
when
it's
posted
go
back
and
take
a
look
at
it,
I
think
it'll
give
you
a
good
idea
for
what
like
what
we
should
talk
about
at
the
post
release
retro.
J
A
Awesome
thanks
for
that
really
appreciate
that,
and
I
I
believe
in
taylor.
I
worked
on
that
release
team
and
I
know
he
does
quality
work,
so
I'm
looking
forward
to
that
recording
because
I
think
it'll
be
good
for
everybody
to
kind
of
get
a
feel
for
things.
Thank
you
appreciate
that
we'll
move
over
to
our
release
lead
ray.
F
Hello,
so
next
week
starts
our
weekly
monday
to
friday
burn
down
meetings.
So
there's
it's
a
lot
of
meetings.
I
know
so
you
don't
have
to
go
to
all
of
them,
but
since
at
least
try
to
have
a
shadow
representative
on
the
call,
if
you
can
so
I
did
send
out
the
tuesday
and
thursday
invites
they're
a
little
tricky
this
time.
So
hopefully
people
got
them.
F
They
did
show
up
on
my
calendar,
but
it
took
me
a
while
to
get
the
third
to
get
the
thursday
invites
out
for
some
reason,
don't
know
why.
So
both
of
those
are
nine
a.m.
Pacific,
according
to
the
doodle,
so
check
appropriately
on
your
on
your
ti
with
your
time
zone
after
that
also
with
those
meetings
as
well.
It's
really
I
mean
it's
been
kind
of
quite
this
release
cycle
so
far,
but
we
we.
F
We
have
those
weekly
meetings
to
monday
to
friday,
meetings
to
really
troubleshoot
some
issues
and
they're
going
to
come
up
issues
just
come
up
for
every
single
release
and
those
are
the
times
to
to
bring
them
up.
So
we
could
get
them
triage
and
get
and
get
some
help
outs.
As
well
with
that,
we
do
have
code
freeze
next
week
on
tuesday,
so
we
we
do
send
another
email
the
day
before
code
breeze
just
to
warn
about
code
phrase.
F
We
did
that
last
week,
so
hopefully
this
will
really
I'm
thinking
about
sending
it
this
week.
Just
because
I
feel
like
the
day
before
is
a
little
bit
a
little
bit,
cutting
it
close,
so
think
about
sending
it
again.
On
thursday
last
time
we
sent
it
on
last
week
we
sent
an
email
on
friday.
So
with
that
we
have
code
freeze
next
week,
also
the
first
beta
first
and
only
beta
to
be
cut
the
day
after
code
freeze
on
wednesday,
then
the
docs
placeholder
pr
deadline
is
which
is
on
thursday.
F
Then
the
week
after
that,
we
have
a
bunch
of
deadlines
on
november
23rd,
because
that
is
also
the
week
of
u.s
thanksgiving.
So
it's
going
to
be
quite
a
bit.
We
have
test,
freeze,
docs,
ready
for
review.
Then
the
first
rc
is
cuts
and
some
branch
management
things
like
the
release
branches
is
created.
Jobs
are
created
for
the
release
branch
as
well,
and
then
we
start
the
final
draft
of
release,
notes
and
also
starts
on
them
on
the
blog
as
well,
or
have
the
blog
release
blog
kinda
almost
ready
to
review.
F
At
that
point
we
do
know
it
is
u.s
thanksgiving
holiday
week,
so
you
know
we'll
be
kind
of
a
little
bit
kinder
on
around
the
around
these
deadlines
of
milestones.
So
all
right,
so
that's
about
it
in
terms
of
milestones,
upcoming
losses
and
deadlines
feel
free
to
reach
out
to
myself
or
to
any
of
the
league
shadows.
F
Like
joseph
mentioned,
the
league
shadows
they've
all
had
lots
of
experience
in
the
past,
with
with
being
on
the
release,
team
all
have
been
role
leads
and
some
and
some
different
roles
as
well
so
feel
free
to
reach
out
to
them.
If
you
have
any
questions
all
right,
that's
it
for
me.
F
No,
they
they
fill
it
in.
Usually,
a
lot
of
the
scalability
folks
are
in
the
european
time
zone,
but
they
usually,
I
ping
them
to
updates
and
they
usually
updated.
Yesterday.
A
So
we'll
take
the
green
is
good
yep,
and
with
that
we
will
wrap
up
this
meeting
and
give
you
the
rest
of
your
time
back
thanks
everybody
for
for
attending,
and
I
will
stop
the
recording
and
if
anybody
else
wants
to
continue
on
the
conversation
or
have
any
questions
that
they
don't
want
on
the
recording
we
can
take
over
there.
So
have
a
great
great
wednesday
and
rest
of
your
week.