►
From YouTube: Kubernetes Release Team BI-Weekly Meeting for 20221118
Description
Kubernetes Release Team BI-Weekly Meeting for 20221118
A
A
There
we
go
so
please
be
aware.
This
is
a
kubernetes
community
meeting,
so
This
falls
under
the
cncf
code
of
conduct,
which
can
be
summarized
to
be
just
excellent
to
each
other
and
be
kind
and
let's
get
started
so
you
can,
if
you
like,
you
can
add
yourself
to
the
attendees
list.
I
I
sent
a
link
in
the
chat
and
I
do
not
see
any
open
discussion
items.
A
B
A
C
So
yeah,
hello,
everyone,
our
current
status,
is
yellow
on
Master
blocking.
We
have
zero
feeling
and
nine
flakes
in
which
none
of
them
shown
pattern
and
on
Master,
informing
we
have
two
failing
folks
are
already
working
on
it.
We
did
a
follow-up
yesterday
and
on
and
we
have
five
flakes
in
which
two
of
them
shown
pattern.
So
after
this
meeting,
I
will
open
the
issue
for
them
so
yeah.
That's
it.
A
B
A
All
right,
moving
on
to
dogs,
there's
no
update,
I,
think
for
dogs,
it's
kind
of
green
and
so
there's
one
PR
which
we
have
to
solve.
If
there's
like
a
if
docs
are
needed,
the
author
said
there
are
no
docs
needed,
so
we
need
to.
We
need
to
double
check,
but
besides
that,
all
the
doc
PRS
are
either
merged
or
already
or
are
in
progress.
So
I
think
that's
good.
Let
me
quickly
check
yesterday's
docs
update
or
the
one
from
Wednesday
and
passed.
A
E
Yeah,
so
we're
back
to
green.
The
the
yellows
in
the
past
interactions
were
mostly
a
precaution,
just
in
case
something
would
drop
to
to
red,
but
that
wasn't
the
case,
so
the
mid-cycle
deprecations
and
removal
blocks
the
the
schedule
date
is
for
today.
I
don't
expect
this
to
be
a
problem,
because
we
have
had
already
a
very
ample
discussion
and
reviews
on
the
on
the
content.
It's
good
to
go
as
far
as
most
of
us
are
our
concerned.
E
The
major
teams
discussion,
I
I,
already-
has
a
good
summary
of
major
teams.
Obviously
it's
still
a
work
in
progress.
Things
can
be
added,
but
there's
more
than
enough
there
for
the
for
the
purpose
of
starting
the
initial
draft
of
the
release,
article,
speaking
of
which
that
initial
draft
was
shared
by
me
to
the
to
the
release,
lead
and
released,
not
least
and
unlock,
leads
yesterday,
I've
shared
a
link
there
for
the
hack,
MD
drafts.
E
I
I
will
add
this
to
the
in
a
work
in
progress
PR
as
well,
but
using
lock
and
hack
MD
initially
allows
for
more
direct
changes
to
to
happen
which
are
less
easy
to
do
in
in
GitHub.
So
that's
the
practice
that
we've
been
using
in
in
contracts
comps
and
in
other
places,
so
that
one
is
done
as
well
and
we
are,
on
top
of
the
15
tracked
fit
blocks
that
are
scheduled
and
no
well.
There
are
to
be
scheduled.
A
All
right
awesome,
thank
you,
yeah,
for
we
also
in
the
cncf
tech,
environment,
sustainability.
We
also
try
out
hack
MD,
if
that's,
if
that's
a
better
collaboration
tool,
but
we
haven't
got
what
was
it
like,
non-profit
sponsoring,
so
we
have.
We
need
that
to
have
like
all
the
collaboration
features,
not.
E
Sure
do
you
have
that
no,
no,
no
I'm
I'm,
just
using
the
whatever
you
get
when
you
sign
in
so
it's
not.
It's
essentially
just
to
be
able
to
have
people
comment
and
and
see
it
without
necessarily
expecting
them
to
know
the
ins
and
outs
of
of
GitHub
because
for
large
text
modifications
GitHub
is
not
it's.
A
A
A
A
D
D
Yeah
the
merge
restrictions
are
in
place,
so
what
I'm
guessing
is
this
may
mean
so
if
we
say
like
labeling,
usually
postcode
freeze,
we
need
that
we
need
issues
to
be
Milestone
and
not
have
certain
labels
to
get
like
merged
into
the
release.
But
probably
that
task
means
this
I.
Yes,
the
merge
restrictions
are
Set.
That's
for
sure.
I
know.
D
A
I
think
I
need
to
follow
up
with
this.
One
like
there
are
actually
also
two
comments
about
this.
That
I
should
ensure
that
this
has
been
done,
because
this
is
mentioned
after
code
free,
so
I
don't
know
if
it
makes
much
sense
if
it
should
happen
during
code
freeze,
but
I
will
follow
up
on
that.
But
besides
that
I
think
for
branch
management.
Everything
should
be
green.
A
A
So
besides
that
everything
looks,
looks
kind
of
good
I
would
say
so.
Maybe
a
little
bit
yellow
status
here
a
little
bit
some
questions
here
and
there,
but
this
is
to
be
expected
besides
that
nothing
major
that
I'm,
aware
of
which
buttons
anything
of
the
release.
So
that's
good
and
right.
The
last
one
already
mentioned
this
I
will
follow
up
with
Jeremy
and
CeCe,
probably
over
release
management
and
Slack
all
right
anything
else
from
your
site
and
your
questions
concerns.