►
From YouTube: Kubernetes SIG Release Weekly Meeting for 20220913
Description
KCSNA 2022 Weekly Planning for 20220912
A
Hey
everyone
welcome
to
the
tuesday
september
13th
sig
release
weekly
meeting.
My
name
is
jeremy
and
I'll
be
the
host.
Today,
I'm
going
to
drop
the
agenda
into
the
chat.
If
you
want
to
add
yourself
as
an
attendee
or
if
you
have
anything
you
want
to
add
to
the
agenda,
you
can
feel
free
to
do
that.
This
meeting
is
covered
by
the
kubernetes
code
of
conduct.
So
please
be
sure
to
be
mindful
of
the
things
you
say
and
by
participating
in
the
meeting
you're
agreeing
to
abide
by
that
code
of
conduct.
A
A
Wants
to
I
I
don't
mind
doing
it
either
cool
you
can
be
the
the
main
notetaker
and
then
yeah.
Everybody
can
always
jump
and
swarm
it
as
needed
all
right
with
that.
We'll
go
ahead
and
kick
it
off
we're
gonna
be
pretty
short
on
other
sick
release
leads
today.
Stephen
and
adolfo
are
at
oss
summit
and
it's
late
in
europe,
so
sasha
is
not
available,
I'm
not
sure
if
carlos
will
join
either.
So
this
is.
A
A
Yeah,
hello,
everyone-
this
is
my
first
time
here-
welcome
dave
espejo.
I
support
open
source
projects
over
at
vmware
and
yeah
happy
to
be
here.
Awesome
welcome,
happy
to
have
you
here.
Is
there
any
particular
part
of
sick
release
that
you're
interested
in
contributing
to
yeah?
Well,
I'm
learning,
and
it
seems
like
I'll,
be
also
part
of
a
chat.
A
B
A
A
All
right,
well,
everybody
that's
new
happy
to
have
you
here.
Welcome
it's
always
great
to
see
new
faces.
I
just
have
one
more
person
tanisha!
Thank
you
for
it.
It's
in
the
notes.
Oh
yeah.
I
had
that
covering
screen
tanisha.
Do
you
want
to
introduce
yourself
totally
cool?
If
you
don't
want
to
go
off,
mute
or.
A
B
B
B
The
1.26
alpha
release
is
going
to
be
done
soon.
The
first
alpha,
I
guess-
and
this
week
we
are
also
doing
the
patch
releases
of
four
release:
branches,
one
dot,
two,
two
one
dot,
two,
three
one
dot,
two
four
and
one
dot,
two
five
one
for
one,
two:
five:
this
is
going
to
be
the
first
batch
release
and
thanks
to
arno
and
jim,
who
are
going
to
do
the
patch
releases
tomorrow.
A
A
A
A
B
A
A
A
A
A
B
I
know
we
are
like
one
day
like
past
the
deadline
to
inform
them,
but
we
had
to
just
be
sure,
with
the
availability
of
all
shadows
before
sending
out
the
rejection
emails,
and
there
have
been
pro
like
there
have
been
talks
on.
How
do
other
teams
automate
their
processes
and
move
out
of
the
spreadsheets
to
project
boards
and
the
latest
among
them
is
comps
and
release.
Communications
team
is
trying
to
explore
github
project
boards
right
now
to
see
like
if
they
can
practically
like
track.
B
The
feature
blog
requests
creation
and
then
basically
enter
a
lifecycle
of
feature
blocks
through
project
boards.
There
is
an
open
thread
on
the
release:
hyphen
comms
channel
on
slack.
So
if
you
would
like
to
pitch
in
with
your
thoughts
like
feel
free
to
do
so
and
tomorrow,
we
hope
to
have
all
the
shadows
in
the
release
team
meeting
and
do
a
round
of
introductions.
B
A
A
A
All
right
so
now
we
can
jump
into
our
open
discussion.
We
only
have
one
thing
on
the
agenda
so
far.
If
you
have
anything
else,
feel
free
to
add
it
right
now,
but
with
kubecon
coming
up
and
the
contributor
summit,
we
we
thought
it
would
be
cool
to
have
an
in-person
sig
release
meeting.
So
we
submitted
a
cfp
to
the
contributor
summit
cfp
form
just
as
a
general
sig
release
meeting.
A
If
anybody
has
any
other
topics
like
maybe
the
branch
rename
might
be
a
good
one
to
include
as
well
folks
can
feel
free
to
submit
if
you're
going
to,
if
you're
going
to
contribute
to
summit,
it's
going
to
be,
I
think,
only
in
person
this
year,
it'd
be
awesome
to
submit
other
other
topics
as
well.
Enhancements
collection
could
be
another
good
one
to
to
go
over
and
kind
of
give
folks
a
highlight
what
the
new
process
looks
like
ask
for
feedback.
A
Make
it
a
an
informal
or
a
bi-directional
kind
of
not
just
talk
but
like
getting
feedback
from
folks
would
be
useful
too.
I
think
in
the
so
we
have
requested
a
room
for
that.
I
think
we're
gonna
try
to
shoot
for
tuesday
to
get
the
most
coverage
of
folks
they're
available
on
tuesday
as
well
as
monday.
A
So
I'm
looking
for
something
right
now
to
try
to
figure
out
what
a
good
place
to
go
would
be.
If
anybody
has
suggestions
or
things,
they
would
like
to
see
feel
free
to
discuss
in
the
sig
release
slack
channel
and
if
tuesday
is
not
good
for
you
and
monday
would
be
better.
Also,
we
can
spin
up
a
thread
there
to
talk
about
like
what
days
would
be
better
for
folks.
A
A
Is
there
any
coordination
needed
from
anybody
here?
Last
time
we
did
valencia
a
little
bit
more
lower
key.
This
one's
gonna
be
a
little
bit
bigger
as
far
as
like
contributor
summit.
Is
there
any
call
for
action
from
anybody
or
support
needed
jeremy?
Not,
yet
I
think
we
when
we
get
closer.
Probably
it
would
be
good
to
help
facilitate
a
couple
of
things.
We
see
how
many
folks
are
going
to
go.
A
A
All
right
does
anybody
have
any
other
topics
for
the
agenda,
otherwise
we
can
end
a
little
bit
early
today
and
give
folks
back
some
time
next
week.
This
meeting
will
be
at
the
alternate
time,
so
it'll
be
a
little
earlier
for
people
in
the
u.s
and
a
little
bit
better
time
for
folks
in
europe
and
in
points
east.
A
All
right
hearing,
nothing
else,
we'll
we'll
call
it
a
day,
thanks
for
everybody,
for
attending.
Welcome
to
all
the
new
folks
happy
to
see
you
here
for
the
126
release
and
as
always,
if
you
have
any
questions
or
concerns
or
things
you
want
to
discuss
after
the
meeting
feel
free
to
start
a
thread
up
and
sig
release
or
use
the
mailing
list,
and
you
take
it
from
there.