►
From YouTube: Kubernetes Release Team Meeting for 20221202 (1.26)
Description
Kubernetes Release Team Meeting for 20221202 (1.26)
A
A
Please
be
aware:
this
is
a
community
meeting
kubernetes
community
meeting,
so
it
falls
under
cncf.
Code
of
conduct
can
be
summarized
to
be
just
excellent
to
each
other,
and
with
that
we're
ready
to
go,
we
don't
have
any
open
discussion
items,
maybe
one
thing
because
it
also
mentions
here
we
will
have
in
two
weeks
the
Retro
I'm
I'm,
mentioning
this
a
lot,
because
it's
always
a
good
time
to
give
feedback
and
work
on
the
program
in
general
and
mention
any
problems
or
concerns,
or
also
mention
what
what
went
well.
A
B
Yep
under
Mark
probably
was
not
able
to
make
it
to
the
meeting,
and
the
updates,
as
mentioned
in
the
dog
they
are
green,
like
current
status,
is
green
and
no
further
updates
in
terms
of
the
metrics
of
the
enhancements
and
yeah
pretty
much
it.
A
Awesome
sounds
good,
yeah
I,
just
updated
the
track
to
from
38
to
39,
because
I
think
the
last
update
was.
We
missed
one,
because
we
added
one
a
little
bit
late,
so
I
need
to
check
if
it's
or
we
can
check
it
out.
It's
an
alpha
feature
better
feature
or
a
stable
feature.
A
C
Hello:
everyone,
our
current
status,
is
green.
Everything
looks
good,
no
major,
update,
yeah.
A
Nice
awesome,
okay,
yeah,
I,
I,
think
probably
in
the
next
days.
I
don't
expect
I
I,
don't
know
if
we
have
like
anything
open
any
tour
picks
or
anything
else,
I
need
to
check,
but
probably
but
I
guess
it's
something
that
people
discuss
in
the
Branch
police
branch
manager
update
or
in
my
update
with
the
golang
updates,
probably
on
Wednesday.
We
would
have
like
a
closer
look
on
the
dashboard
if
everything
is
green,
but
until
then,
so
far
so
good.
D
A
If
not,
we
can
go
to
Docs
with
Carol
somebody
here
from
dogs,
I,
don't
think
so.
A
So
I
can
give
a
brief
update.
So
we
are
chasing
the
last
last
docs
I
think
they're,
just
a
few
left,
most
of
them
have
been
merged
and
the
other
ones
are
pretty
close
to
getting
merged
as
well.
So
I
guess
we
should
be,
should
be
fine,
probably
like
a
yellow,
update,
I
I
assume,
but
yeah
I'll
go
follow
up
on
that
later.
If
everything
is
all
right,
okay,
release,
notes,
I,
don't
believe
anybody
from
release
notes
is
here.
A
E
So
we
have
a
fortune
reporting
to
fit
a
black
blogs
ready
for
review,
one
that
didn't
made
it
we're
still,
however,
hoping
to
tag
it
near
the
ends.
That
part
is
is
fine.
E
We
have
the
publication
dates
and
ordering
ready
and
we're
just
I'm
just
waiting
for
some
initial
feedback
from
sick
docs
and
others,
so
that
I
can
push
it
into
the
to
the
individual
PRS,
and
so
that's
the
the
first
blog
will
start
in
the
first
Monday
after
the
release
date,
so
the
12th
of
December,
and
it
will
go
on
until
roughly
the
first
week
of
January,
so
the
the
release
date
changed
was
actually
also
tweeted
yesterday
and
to
increase
the
visibility
of
the
change
and
the
release.
E
E
The
only
thing
why
this
is
yellow
is
because
we
we
did
change
the
release
date
to
the
8th
of
December,
and
because
of
that,
we
need
to
wait
for
the
the
the
the
pr
announcement
support
from
the
cncf
I've.
As
the
information
came
in,
we
immediately
contacted
the
cncf
in
order
to
inform
them
of
that
change,
and
we
just
need
to
fight.
A
All
right
awesome,
thank
you
for
your
update
for
the
release
article
in
the
blog
post.
If
all
the
reviewers
have
been
reviewed,
the
DPR
their
their
sections
or
do
you
think
we
need
to
there.
E
I
think
that
so
I'm
still
getting
feedback
before
entering
the
meeting.
There
were
feedback
there.
So
I
guess
that
there
are
some
missing.
I
will
ping
them
during
the
day
and
because
we
still
have
a
week
until
the
the
release
date.
But
but
I
would
say
that
if
anything
happened,
it
would
be
good
it.
It
would
be
good
to
go,
as
is
no.
F
Management
side
rc1
went
successfully
after
a
little
bit
bumpy
ride,
but
we
managed
to
solve
all
the
issues
that
we
had
with
the
file
signing
and
that
is
now
working
as
pretty
well.
We
also
solved
some
of
the
issues
that
we
had
with
signing.
So
from
that
side
we
are
good
to
go.
The
only
thing
that
is
something
that
we
are
monitoring
and
paying
attention
to
is
the
go
update.
F
The
reason
why
we
move
they
released
for
two
days
and
we
will
be
working
on
getting
it
getting
go
updated
in
communities
in
release
tooling
and
everything
needed.
We
hope
to
finish
this
on
Wednesday,
so
that
we
have
one
day
to
get
the
CI
signal
properly
and
we
will
keep
you
all
updated
on
how
that
goes.
As
a
quick
note,
the
goal
releases
will
go
out
to
Tuesday
in
U.S
business
hours,
so
we
will
see
we
will
have
more
details.
Then.
A
F
A
E
E
A
It's
not
sharing
again,
but
I
mean
the
update
is
almost
over
because
okay
yeah,
the
the
golang
team,
push
push
new
update
on
Tuesday.
So
to
get
those
changes
in
those
minor
bumps,
we
need
to
postpone
our
our
release
cut.
So
hopefully
everything
goes
smooth
in
the
two
days
and
yeah.
That's
that's
it
for
my
side,
any
questions.