►
From YouTube: Kubernetes Release Team Meeting for 20220426
Description
Kubernetes Release Team Meeting for 20220426
A
A
This
is
week
16
tuesday,
the
26th
of
april
2022.,
and
if
you
are
here
with
us
today,
please
put
your
name
in
the
attendees
list.
Note
for
this
meeting,
as
with
all
of
our
meetings
is
covered
by
the
cncf
contributor
code
of
conduct.
So
please
refer
to
that
document
for
all
your
interactions
with
us
here
today
I
don't
have
any
particular
open
discussion
items
I
will
move
on
to
enhancements.
A
No,
I
don't
think
I
do.
I
don't
expect
any
particular
update
from
them.
So
let's
move
on
ci
signal
leonard
said
in
slack.
He
couldn't
make
it
but
updated
updated.
The
notes-
and
I
see
that
we
are
green
with
no
failings
which
is
fantastic.
A
So
I'm
pretty
happy
about
that.
Moving
on
book
triage
with.
B
A
Oh
yeah,
I
have
a
known
issues:
one
okay,
yeah
cool,
all
right,
looking
good.
Thank
you.
Any
questions
for
bugs
react.
A
Nope,
okay,
I
have
a
particularly
update
from
them.
I
need
to
talk
to
nate
because
there's
some
some
weird
issue
that
I
need
to
find
out
go
away
I'll,
get
to
that
in
a
moment.
Release
release
notes,
one
of
my
browsers,
finished
freaking
out.
A
Just
in
a
moment,
there
right
released
tonight's
notes.
A
No
okay,
comms.
C
Okay,
so
I've
marked
our
status
as
yellow,
because
we
are
tracking
feature
blocks
for
the
release.
We
are
tracking
them
to
get
them
in.
Our
plan
is
to
get
the
docker
ship
removal
and
the
a
few
other
blogs
about
graduating
to
stable
issues
out
first
and
out
in
the
first
three
days
of
of
the
release
and
then
we'll
they'll
be
followed
up
by
graduating
to
beta
and
graduating
to
alpha
feature
blogs,
so
we'll
be
working
on
them.
C
Priority
wise
and
I
think
we
are
deciding
on
the
dates
for
the
press-
release
yeah
james
here
in
the
loop
so
yeah,
that
is
it
from
comms.
A
No
all
right,
navaroon
also
couldn't
make
it,
but
for
the
update
here
set
for
us
who
won
today,
subject
to
cia
signal,
go
no
go,
and
there
was
a
speak
for
ci
signal,
but
it
looks
like
a
go
to
me.
So
that's
pretty
good
and
yes,
our
last
release
blocker
got
resolved,
which
is
that
windows
issue,
but
that's
been
fixed
now,
which
is
very
nice.
If
I
do
wonder
if
it
needs
to
be
cherry,
picked,
it's
124
release
branch.
You
need
to
follow
up
with
that
one.
A
I
don't
think
the
update
from
joseph
for
me.
What
have
I
been
doing?
I
have
given.
The
team
leads
a
copy
of
the
release,
theme
and
release
logo.
A
I
actually
need
to
go
through
and
write
up
some
some
verbage
to
just
explain
the
theme,
as
we
normally
do
in
the
release,
blogs,
which
is
going
to
get
added
to
the
release
blog
draft
in
due
time.
So
that's
coming
along
nicely.
We've
been
doing
a
little
bit
of
major
theme
discussion
and
that
looks
to
be
going
pretty
good.
So
I
think
of
the
github
discussion
at
this
point
is
largely
wrapped
up.
A
I
think
that
all
the
major
themes
are
going
to
be
proposed
have
been
proposed,
so
it's
just
got
a
bit
of
editorising
down
which
shouldn't
be
so
bad
yeah
in
general,
things
are
looking
pretty
good.
Does
anyone
have
any
questions
for
me.
A
All
right,
there
is
one
doc's
issue
which
someone's
saying
is
a
release
blocker,
but
I'm
not
entirely
clear.
What's
going
on
there,
so
I'm
going
to
go,
try
and
figure
that
out
and
talk
to
nate
about
it
other
than
that
yeah.
I
know
particularly
from
scalability.
C
A
Yeah,
I
think
so
I
think
for
our
last
one.
We
should,
I
think,
for
the
one
next
week,
the
last
one
I
will
move
it
to
a
a
later
time.
It
kind
of
ended
up
here.
I
think,
because
I
wanted
one
that
navaroon
could
make,
because
it's
largely
for
him,
if
you.