►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20221005
Description
Kubernetes Release Team Bi-Weekly Meeting for 20221005
A
Hello:
everyone
welcome
to
the
kubernetes
1.26
release
meeting,
just
a
reminder
that
this
meeting
is
under
the
cncf
code
of
conduct,
which
will
down
to
being
kind
and
respectful
to
each
other
I'm
going
to
share
my
screen
now
and
we
can
go
through
it.
A
All
right,
only
one
open
discussion
item
is,
please
add
your
notes
about
the
release
process
to
the
1.26
Retro
doc
and
then
we'll
jump
right
into
enhancement
with
dialer.
B
Yep,
hey
everybody
hope
you're
doing
well.
Enhancements
is
green.
B
Call
out
that
we
have
enhancements
freeze
tomorrow,
I
think
it's
nine
o'clock,
us
Eastern
Time
and
then
the
other
thing
the
enhancements
team
will
start
to
focus
on
is
some
changes
to
continue
to
support
the
shift
to
use
GitHub
project
boards
and
so
there's
quite
a
bit
of
docs
to
go
through
and
clean
up,
especially
around
the
role
handbook.
B
We
want
to
finish
out
getting
some
changes
to
the
sync
job
in
place
and
there's
submission
links
to
clean
up
stuff
that
we
want
to
tackle,
and
so
we
have
some
downtime,
basically
between
enhancements,
freeze
and
code
freeze,
and
so
we
want
to
try
to
focus
on
those
things
when
we
have
time
as
far
as
metrics,
we
have
76
enhancements
so
far,
it's
up
by
31
since
last
week,
so
quite
a
few
over
the
last
week,
and
we
have
17
tracks
51
at
risk,
seven
are
removed
from
Milestone
and
one
we're
not
getting
a
response
on
so
far.
B
A
C
A
D
Thanks
to
the
team,
we
are
tracking
all
the
issues
we
have
right
now
on
the
Giza
project
board,
but
the
previous
team
leader
Uma.
She
was
working
on
a
shell
script
and
she
donated
that
shell
script
to
the
the
release
team,
so
we're
gonna
use
this
Shelly
script
in
a
GitHub
pipeline.
So
we
can
sync
the
the
issues:
pull
requests
created
in
the
GitHub
automatically
to
the
GitHub
project
board.
So
thanks
to
this
process
is
going
to
be
automated
and
soon
we're
gonna
have
it
so
yeah.
D
We
are
fully
shifted
to
GitHub
project
board
and
yeah
I,
just
posted
the
the
link
in
the
chat
in
the
documents.
So
everyone
can
see
it.
That's
all
from
our
side.
A
All
right,
thank
you.
Docs
with
Carol
I
see
you
there.
E
F
Yeah,
it's
got
like
my
name
is
Lakshmi
and
I'm
working
at
the
Village
teams
Shadow
this
time,
so
current
state
status
is
green,
so
first
work
we
did
like
merch.
We
are
like
updating.
We
leave
notes
handbook,
which
we
added
for
a
recent
1.25
examples.
Second,
we
create
a
couple
of
draft
PR's
for
real
life
notes,
which
is
for
Alpha
One
Cut
and
also
like
we
started
the
GitHub
discussion,
which
will
start
collecting
the
major
streams.
So
these
are
the
status
for
the
eighth
notes.
Any
questions,
let
us
know.
G
Hello,
everyone
yeah
this
week
we
started
Distributing,
the
six
we'll
be
we
will
be
approaching
in
order
to
confirm
which
one
of
the
enhancements
will
be
opted
in
for
the
feature
blog
post.
This
distribution
can
be
found
in
the
comes
view
of
the
tracking
board.
Also,
we
started
a
threat
on
the
regarding
the
mid-cycle
deprecations
block.
G
We
will
continue
a
conversation
this
week
to
determine
based
on
the
data
we've
collected
so
far.
What
should
be
the
focus
of
these
mid-cycle
blog
post
and
we
have
our
eyes
open
for
the
major
teams
discussion
Study
last
week,
so
we
can
work
on
the
mid
cycle
and
final
release.
Article.
A
All
right,
thank
you
for
that.
Oh
no
Jeremy's
here
today,
if
not
I'll,
be
moving
on
to
EA
with
Melbourne.
A
Okay,
Leo's
out
of
office
and
if
now
maroon
is
not
here,
I'm
just
gonna
read
his
updates.
That
is
two
Shadow
orientations
were
conducted
and
feel
free
to
reach
out.
If
anyone
missed
it
all
right,
Leo
is
not
here
today.
So
I'll
just
read
out
his
notes.
Here
enhancement
freeze
is
tomorrow
and
reminder
everyone
has.
Some
free
has
been
sent
out
last
Friday
and
then
we
are
trying
to
find
a
Friday
APAC
friendly
time.
A
So,
if
you
are
in
that
time
zone,
please
look
out
for
the
doodle
and
then
kubecon
is
the
week
of
October
23rd
24th.
So
we
might
cancel
our
Wednesday
and
Friday
meetings.
If
anyone
has
thoughts
about
that,
please
send
it
in
the
slack
threat
or
slash
travel
and
everything
else
is
good.
All
right,
I
will
stop
sharing.