►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20220907
Description
Kubernetes Release Team Bi-Weekly Meeting for 20220907
A
Hello:
everyone
welcome
to
the
first
meeting
first
release
team
meeting
for
the
release
cycle.
1.26
today
is
wednesday,
the
7th
september
and
yeah.
This
is
a
kubernetes
meeting,
so
it
falls
under
the
cncf
code
of
conduct,
which
can
be
summarized
to
be
just
excellent
to
each
other
and
starting
with
the
open
discussions,
so
yeah
hello.
Everyone
welcome.
A
I
think
that
we
are
all
returners
kind
of
previously
served
on
release
team
because
we
haven't
selected
yet
the
shadows.
A
A
One
week
is
kubecon,
so
everything
should
be
should
be
all
right
from
a
time
perspective
and
yeah
moving
on
to
the
next
one.
So
if
there
are
like
any
ideas,
already
feedback
or
problems,
suggestions
which
already
came
up
or
or
maybe
will
come
up
during
the
release,
we
created
the
1.26
retrospective
doc.
A
B
Yeah,
maybe
I'll
move
this
under
enhancement
since
ryler's,
not
here,
but
essentially
the
enhancement
team
has
been
shifting
from
the
sheets
over
to
the
project
board
and
the
past
week
we've
been
working
on
the
label
and
communicating
that
with
the
community
and
the
sick
elites.
But
one
thing
that
is
not
fleshed
out
and
I
need
doc's
help
with
is
what
this
will
look
like
for
the
docs
team.
B
So
we
were
thinking
to
out
of
view,
but
like
everything's
not
fleshed
out
and
in
past
releases,
the
docs
team
have
a
page
on
the
enhancement
sheet,
so
would
love
to
figure
out
like
either
now
or
a
time
later,
where
we
can
kind
of
talk
through
what
that
looks
like
tomorrow,
at
1pm,
pt
ryler
and
I,
and
maybe
leo-
will
have
a
further
discussion
on
this.
The
meeting
link
is
in
the
release,
enhancement,
channel
you'd,
like
to
join.
A
Awesome,
thank
you
yeah.
I
will
quickly
paste
the
link
in
the
in
in
the
chat
and
also
in
in
the
release
meeting
notes.
So
if
anybody
would
like
to
join,
I
think
tomorrow
would
be
a
good
time
to
discuss
further
things.
A
I
guess,
besides,
that,
the
enhancement
sheet
shift
is
kind
of
communicated
to
everybody
to
the
community
and
is
besides,
maybe
some
automation
parts
done.
I
think
right
or
is
there
any
like
bigger,
bigger
tasks?
Grace?
What
do
you
think.
B
No
yeah
the
sheet
will
be
triggered
manually
to
run
a
script
and
that's
gonna
be
run
twice
a
day
for
now,
but
there's
no
outstanding
task.
A
C
A
Okay,
are
there
any
other
open
discussion
points?
Otherwise
we
can
also
have
this
at
the
end
of
the
meeting.
If
not,
we
can
move
on
to
enhancements.
A
So
I
guess
we
already
had
this
update
any
any
other
comments
for
enhancements.
Grace.
B
No
comments,
really.
We
just
started
enhancement
collection.
I
don't
think
ryler's
here
so
there's
not
much
to
update.
A
All
right
looks
good,
sounds
good.
Moving
on
to
ci
signal
with
new
yeta.
C
So
yeah
so
hello,
everyone,
according
for
updates
on
the
our
test
grid,
looks
great
and
other
than
this.
I
have
selected
my
shadows,
but
I
will
try
to
reconsider
this
reconsider
my
selection
because
of
the
feedback,
so
I
will
try
to
make
my
team
more
diverse
and
I
will
notify
them
tomorrow
by
the
end
of
the
day.
C
D
Hello,
everyone,
so
the
selection
process
is
already
started,
so
I'm
going
through
the
list-
and
I
think
by
tomorrow,
midday
should
be
posted
in
channels,
so
yeah,
I
think,
get
all
the
feedback
from
you
fox.
That's
one
thing.
The
other
thing
is
what
we
discussed
like
shortly
in
pakistan
in
slack
with
leo
about
project
board
so
previous
release.
We
also
started
to
yeah
testing
the
project
board
for
bug
triage,
and
actually
it
worked
nicely.
D
So
if
there
is
no
objection
again
I
mean
there's
nothing
against
it.
I
will
continue
using
the
same
concept
because
it's
nice
regarding
automation.
We
have
used
to
have
yeah
manual
script,
to
pull
the
issues
and
prs
from
github,
so
that
part
will
be
still
the
same.
D
A
Awesome
awesome
sounds
great.
I
think
that,
like
last
cycle,
there
are
already
been
some
work
on
the
automation
part
right,
so
is
there
yeah
or
is
this
completely
new
no.
D
E
I
have
a
question
for
vacriej.
I
saw
the
board
to
be
private
right
now.
Do
we
want
to
make
it
public.
C
E
D
E
D
Well,
definitely,
I
totally
agree
with
you.
I
think
this
was
done
by
the
previous
lead
just
accessible
for
the
team
members.
Absolutely,
let's
make
it
public
and
yeah.
It
will
be
transparent
to
everyone.
A
Thank
you
and
good
catch
and
any
other
questions
or
otherwise,
let's
go
to
dogs.
C
C
C
A
Awesome
awesome:
are
there
any
by
the
way,
are
there
any
onboarding
sessions
recorded
or
just
in
general,
because
I
remember
for
ci
signal
we
had
like
some
recordings,
which
we
also
used
for
onboarding.
Would
this
also
be
something
for
release
notes
just
yeah.
A
F
Hello,
well
we're
we're
fine
at
this
stage.
It
would
be
hard
not
to
be,
but
especially
since
comms
is
a
bit
top-heavy
in
terms
of
schedule,
but
we're
we're
fine.
We
I've
I've
done
the
shadow
selection,
pretty
much
I've
shared
with
the
rest
of
the
team,
I'm
just
starting
to
contact
them
today
and
tomorrow.
F
A
E
Sure
so
we
closed
our
shadow
applications
on
september
2nd.
We
kept
it
open
until
anywhere
on
earth
time
this
time,
just
to
give
everyone
a
fair
chance
to
fill
in
the
application.
At
the
end
of
it,
we
got
144,
responsive
of
which
125
people
are
newcomers
to
the
release
team
they
had.
E
They
had
never
been
part
of
the
team,
maybe
they
have
applied
before
and
we
got
19
people
who
have
already
served
on
the
release,
team
and
applied
to
be
a
shadow
again,
that's
on
the
start
side
and
the
leads
have
been
forwarded,
report
of
who
has
applied
in
both
the
types
of
applications
and
they
are
currently
selecting
the
shadows
as
we
got
updates
from
everyone.
Previously,
that's
all
on
my
side,
I'll
just
wait
for
people
to
to
do
selections
and
then
we'll
start.
The
shadow
onboarding
process.
A
Awesome
all
right,
yeah,
also,
together
with
the
shadow
responses
we
we've
been
working
on
on
the
release
team
shadow
sets
project
to
generate
the
pdf
files
for
the
lead
selection,
also,
some
some
charts
and
diagrams
for
a
report,
and
we
are
currently
discussing
with
in
the
thread
I
can.
I
can
link
the
issue
about
also
publishing
a
report
to
the
community,
so
this
might
also
get
sent
out
sometime
this
release.
A
Hopefully
all
rights
then
moving
on
to
to
my
updates,
the
onboarding
for
the
release
team
leads
is
done,
so
all
the
yaml
files
and
everything
has
been
updated
for
all
the
shadows.
I
think
most
most
already
completed
the
cncf
inclusive
speaker
orientation
training,
if
not,
this
is
a.
This
is
a
good
training,
very
short,
also
for
any
any
anybody
else
who
is
interested.
A
That
would
be
great
if
you
could
comment
or
take
this
course
and
also
just
a
reminder
for
all
the
team
leads
if
you
selected
your
shadows
and
so
there's
also
under
the
sick
release
team,
the
markdown
file,
which
just
shows
the
entire
team.
So
you
can
also
update
the
team
afterwards
and
also
add,
add
your
shadows
to
it.
A
Right
and
then
also
just
a
general
comment
that
always
communicate
in
public.
I
think
this
works
really
great,
I'm
just
just
as
a
reminder
and
also
don't
don't
hesitate
to
reach
out.
I
think
yeah,
just
just
some
two
less
general
comments
and
that's
that's
it.
I
think
I'm
excited.
I
think
the
release
would
be
great.
A
We
have
great
leads
and
great
shadows
coming
in
I'm
sure
and
yeah.
Then
there's
an
update
from
sixth
scalability
looking
at
the
attendees
list.
I
cannot
see
jakub
or
is
he
here
not
sure
otherwise,
there's
apparently
a
single
flake,
this
one,
nothing
serious,
but
there
is
a
pending
or
cr
for
it.
A
I
will
reach
out
to
your
coupe
because
I'm
not
100
sure
what
this
means,
but
apparently
it
should
be.
It's
not
serious,
so
it
should
be
fine.
A
So
if
there's
like
anything
coming
up,
I
will
communicate
that
right.
Then
I
added
a
few
issues
to
the
project
board.
So
last
cycle
we
didn't
use
the
project
board
that
much.
Maybe
this
would
change
this
release
or
I
would
try
to
add
the
important
issues
to
it.
Maybe,
for
example,
I
think
cossin.
You
said
something
about
the
bug
triage
automation,
part.
Maybe
we
can.
We
can
just
collect
all
the
work
in
progress
tasks
here.
A
So,
for
example,
there's
the
blog
post,
which
we
are
working
on
grace,
is
working
on
mainly
and
also,
for
example,
the
onboarding
for
the
beats,
which
is
kind
of
done
and
so
on
and
so
forth.
So
that's
basically
it
I
think
we
are
in
in
a
good
shape
right
now
and
yeah
any
any
other
comments.
Before
closing,
I
see
grace
grace
end
up.
B
Yeah,
can
you
go
to
the
project
board
in
the
bag,
lock
at
the
very
bottom
of
the
backlog?
On
the
left
hand,
side
yeah,
I
just
added
a
new
issue
for
documentation
for
pr
freeze
risk.
B
So
I
looked
through
when
I
was
removing
the
word
soft
from
pr
soft
freeze
and
I
realized
that
there
wasn't
really
a
documentation
on
like
what
the
freeze
is
about
what
happens
when
you
miss
the
freeze
and
like
kind
of
the
risk
of
like
getting
your
cap
rejected
and
also
like,
if
you
miss
the
freezing,
you
can
find
an
exception,
etc,
but
I'm
not
sure
where
a
good
place
to
put
that
is
so
interested
for
feedback
here.
A
E
I
think
this
should
be
part
of
the
kubernetes
community.
Repo
production
readiness
review
is
a
sub
project
under
sig
architecture
and
usually
we
have
all
depth-facing
documentation
in
kubernetes
community
and
that
should
like
serve
as
source
of
growth.
So
we
can
explore
like
if
there
is
any
page,
so
I'm
pretty
sure
like
inside
contributor,
slash
devil.
There
would
be
a
cigar
kind
of
directory
where
we
can
add
this
information,
and
we
should
ideally
consult
with
the
prr
team
and
cigar
folks
as
well
to
get
a
sign
up
on
this.
A
G
Yeah,
so
we
also
have
a
doc
under
sig
release.
Slash
releases
called
release
phases,
it's
a
markdown
file
which
talks
about
the
enhancement,
sprees
burn
down
code,
freeze,
test,
freeze,
thaw
and,
and
even
the
feature
feature
blog
phrase
as
well
and
exceptions
so,
and
also
docs
as
well.
So
there's
so
we
might,
we
might
want
to
add
a
section
of
prr
to
the
to
the
release
phases.
G
Since
now
it's
part
of
the
timeline
and
and
then
we
could
go
into
about-
add
some
more
about
about
the
documentation
for
the
the
risk
of
missing
the
pr
as
well.
F
G
Or
it
could
be,
we
could
add
a
link
from
that
whaley's
phases
dog
to
the
the
to
the
doc
in
in
k
community
under
sig.
So
that's
right,
so
we
could
refer
to
that
montage.