►
From YouTube: Kubernetes Release Team Meeting for 20221102
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
B
Welcome
to
the
kubernetes
1.26
release
team
meeting
for
Wednesday
November
2nd.
This
is
an
official
kubernetes
meeting
and
as
such
falls
under
the
cncf
code
of
conduct,
which
can
be
boiled
down
to
please
be
kind
to
each
other.
B
Welcome
back
from
kubecon
all
those
who
went
and
went
virtually
and
welcome.
Even
if
you
didn't
go
to
kubecon,
it's
been,
it
was
been
a
week.
It
was
a
lot
of
fun
seeing
folks
and
now
now
we
have
to
catch
up
so
first
off
I
just
want
to
make
a
note
that
we
are
having
our
retrospective
part
one
immediately
following
this
meeting.
B
So
if
you've
got
anything
to
add
to
that
discussion,
you're
welcome
to
join
and
there's
also
a
link
in
the
meeting
minutes
doc
to
that
meeting,
so
that
you
can
add
things
to
that.
Add
things
to
that
discussion
if
you're
interested
in
participating
at
this
point
I'd
be
surprised
to
see
new
members
or
attendees.
But
if
there's
anybody
new
would
like
to
say
hi,
please
you're,
welcome
to
say
hello,
foreign.
B
Sometimes
we
catch
up
with
folks
or
we
We
Gather
new
Folks
at
kubecon
and
build
up
some
excitement.
So
I
was
maybe
hoping
that
there'd
be
some
some
new
folks
from
that,
but
it
doesn't
look
like
it.
So
we'll
continue.
B
B
C
So,
overall
enhancement
status
is
green
code
freezes
next
week
and
the
enhancements
team
has
been
busy
reaching
out
to
all
of
the
enhancements
that
are
in
this
release
to
make
sure
that
all
of
the
they
have
all
of
the
PRS
that
are
needed.
C
The
code
PR's
tracked
with
that
all
51
of
the
cups
that
are
promoting
features
have
been
kind
of
we've
reached
out
to
them,
and
nine
of
the
enhancements
so
far
have
all
of
the
code
peers
merged
and
are
good
to
go,
so
just
keep
on
top
of
that
until
it
goes
freezing.
B
Okay,
let's
move
on
to
CII
signal
is
bujuana
on.
D
E
Hello,
everyone,
so
our
current
status
is
brain
thanks
to
the
team's
great
work.
We
have
been
able
to
track
all
the
issues
and
PR's
yeah,
so
we
are
pinging
in
some
issues
or
PR
not
responding.
There
was
discussion
on
team.
How
we
can
reach
out
so
I
suggest
that
we
can
think
the
respective
six
in
the
slide
and
if
they
don't
respond,
so
we're
gonna,
remove
the
pr
or
the
issue
from
the
minus
one
of
126..
That's
all
from
our
side.
F
Hi,
hello,
I'm
from
docs,
so
our
status
overall
is
green.
We're
completing
Outreach
to
get
the
draft
PR
as
filed
this
week,
they're
due
for
one
week
from
today,
so
November
9th
in
terms
of
stats
you've
been
tracking
it
in
the
dashboard.
That's
linked.
F
We
have
three
merged
11
without
a
PR.
Six
with
draft
PR
is
already
open.
One
ready
to
review
44
was
still
no
doc
status,
we're
working
on
on
getting
responses
back,
and
then
we
added
a
tag
for
the
enhancements
that
didn't
make
the
the
cut
off.
So
that's
like
15
of
those
a
question
for
the
group:
can
we
remove
them
from
our
tracking
shoot,
or
do
we
want
to
keep
those
for
posterity
foreign.
B
My
sense
is
I,
don't
like
losing
information,
so
if
we
can,
if
we
can
somehow
tag
them
or
separate
them
out,
it
would
probably
be
good
to
keep
them
just
so
that
we've
got
the
the
information,
but
if
it
becomes
a
if
it
becomes
a
father
or
it
gets
in
the
way
of
continue
tracking,
then
then
potentially
get
rid
of
them.
Yeah.
F
No
problem:
we
can
keep
it
as
just
tagged
as
removed
from
from
release
for
now
yeah
overall
green.
Oh
sorry,
go
ahead!
No.
G
Yeah
just
saying
that,
as
a
user
of
that,
that's
what
we've
been
doing
in
in
our
viewing
comes,
we've
been
filtering
for
direct
and
in
risk,
and
by
that
we
we
get
a
view
of
what's
actually
on
the
table.
So
it's
it's
I,
think
keeping
the
information
makes
sense
because
it's
it's
relatively
easy
to
to
filter.
H
Hello,
Anthony
I
am
from
the
release,
notes,
section
hi,
so
for
the
release
notes
team,
our
overall
status
is
green
as
of
now,
and
we
have
completed
all
the
draft
Piers
for
Alpha
One
and
there
is
just
last
PR
left
a
last
draft.
We
are
left
for
Alpha
2
that
will
be
good
to
go
by
and
today
or
tomorrow
and
we
previous
previous
meeting.
H
We
had
an
issue
that
related
to
KRL
draft
PR,
which
was
which
was
throwing
errors
in
the
WSL
environment
and
we
have
found
a
solution
for
it,
so
that
is
solved,
but
there
is
a
problem
with
the
website
PR
in
the
WSL
environment
that
we
are
trying
to
get
through
and
I
think
yeah.
We
have
started
working
for
the
Alpha
3
from
today.
B
Awesome,
thank
you.
Is
there
any
questions
for
release,
notes.
B
G
Take
this
one
yeah
yeah
absolutely
so
we
had
the
feature
blog
opt-in
deadline
and
yesterday
today,
depending
on
where
you
are,
but
I
would
like
first
to
to
to
thank
all
the
Shadows
working
in
the
comms
team
for
the
steady
and
sometimes
insistent
work
that
I
had
to
do
to
to
get
information
out
of
everyone.
And
then
we
have
18
feature
blog
opt-ins
attract
at
the
moment,
which
I
think
it's
a
it's
an
interesting
number.
G
So
that
ends
one
of
the
one
of
the
stages
in
which
comes
is
more
active
now
on
to
really
follow
up
with
this
feature
blocks
and
on
the
on
on
the
second
track.
We,
the
next
deadline,
is
around
the
mid-cycle
deprecations
and
removals
blog.
We
had
some
previous
conversation
on
the
needs
to
have
it
or,
if
should
we,
should
we
replace
it
with
something
else?
B
G
B
Okay,
moving
on
to
release
Branch
management,
I
think
Xander
you're
up
for
this.
I
Yeah
so
let's
see
Cameron
hear
me:
okay,
yes,
okay,
good
I've
been
having
problems
the
past
few
days
with
that,
so
just
double
confirming
yeah.
So
we
cut
Alpha
three
yesterday
and
that
all
went
well
according
to
plan
and
then
I
have
the
dates
on
there
for
the
upcoming
releases
becoming
beta
one
next
Thursday,
which
is
November
10th,
and
then
we've
got
RC
zero.
B
Good
stuff,
thank
you
for
that.
Are
there
any
questions
for
Xander
and
the
relief
Branch
management
team.
B
Okay
and
I
think
I
just
saw
nabrin
pop
on
as
the
Emeritus
nabrin.
Do
you
would
you
like
to
say
anything.
A
Nothing
much
it's
been
a
weird
thing
for
me
to
join
in
different
time
zone,
but
we
will
meet
in
the
Retro
in
half
an
hour.
So
just.
C
A
C
B
Yeah
and
Leo
has
shared
the
release
docs,
rather
the
Retro
doc
Link
in
the
the
chat
here
and
again,
we're
probably
going
to
end
this
meeting
a
little
early,
so
I
really
I
earlier
said
that
it's
gonna
happen
right
after
this
meeting.
I
lied
it's
going
to
happen
at
about
in
about
a
half
hour
from
now.
Whenever
we
end
this
meeting,
it'll
start
at
the
45
past
the
hour.
Let's
move
on
to
Leo.
J
Hello,
everyone,
yeah
I,
think
it
makes
sense
to
our
to
keep
the
schedule.
Folks
are
probably
looking
at
the
calendar
and
so
all
right
so
to
the
updates.
J
J
If
you
are
unsure
about
meeting
times
or
just
drop
a
message
in
in
slack,
if
you're
not
not
sure,
but
the
calendar
should
be
up
to
date
and
right
moving
on
to
the
meeting
times
so
we're
looking
at
the
schedule.
We
plan
that
next
week
we
will
start
with
Monday
meetings
too
I
feel
like
we
can
maybe
shift
this
or
push
this
a
week
back,
because
at
the
moment
we
don't
have
too
much
things
to
discuss
and
probably
things
will
I
don't
know
increase
after
code
freeze,
but
this
is
the
week
after.
J
J
So
we
will
have
then
three
meetings
each
week
and
the
week
after
usually,
we
also
have
everyday
meetings
so
burned
on
meetings.
So
in
the
past,
Tuesday
and
Thursday
meetings
are
quite
light
on
attendees
and
also
on
news.
So
probably
we
are
good
to
go
with
just
updating
just
news
via
slack,
so
basically
what
we
did
during
kubecon
I
think
that
went
very
well
and
if
there's
like
any
specific
need,
we
can
also
schedule
meetings
but
I.
J
Think
if
this
I
I
don't
know
in
the
last
last
releases,
I
I
think
it
was
not
necessary
to
meet
also
on
Tuesday
and
Thursday.
So
we
can
try
to
skip
this
this
time
and
yeah.
That's
that's
it.
We
will
have
to
release
retro
coming
up,
there's
also
a
ratio
after
the
release.
So
if
they
are
like
any
more
feedback
questions
inputs
whatsoever,
you
don't
you
don't
need
to
feel
pressure
to
add
your
thoughts
in
the
next
half
an
hour.
You
also
have
time,
after
the
release.
B
Thanks
for
the
update,
Leo
and
there's
one
last
I
I'm
here
on
the
updates
agenda,
is
there
anybody
from
six
scalability
on
the
call
would
like
to
update
us.
B
Okay,
it
doesn't
look
like
it
do
we,
you
know
what
I
just
realized.
I
haven't
been
sharing
my
screen.
It
all
sorry
about
that
folks,
shall
we
do
the
walk
the
project
board
here,
let's
see
if
I
can
share
my
screen
for
at
least
this
part.
B
B
Is
there
any
so
I'm
actually
going
to
put
this
out
to
the
I
have
not
walked
this
board
in
a
while?
My
apologies
is
there.
Anybody
who
would
like
to
speak
to
any
specific
issue
open
here
in
our
board
or
is
everything
is:
are
things
in
their
ranked
place
that
you
can
see.
B
J
B
J
B
All
right,
in
that
case
Let's,
is
there
any
other?
Is
there
any
other
comments
anybody
would
like
to
make
on
camera
or
during.
B
I'll
turn
off
the
recording
and
give
it
a
couple
of
minutes
to
chat
at
the
at
the
end.
Here.