►
From YouTube: Kubernetes Release Team Bi-Weekly Meeting for 20200113
Description
Kubernetes Release Team Bi-Weekly Meeting for 20200113
A
All
right,
everybody,
hello
and
welcome.
I
am
your
host
james
laverack,
I
am
the
one
queued
is
124
release
team
lead
and
this
is
a
release
team
weekly
meeting.
It
is
week.
One
of
it
is
wednesday,
the
12th
of
january
2022..
A
If
you
are
attending
this
meeting,
please
add
yourself
to
the
attendees
list,
which
is
on
the
document.
That's
been
shared
in
the
chat.
I
have
to
kick
us
off.
I
have
a
few
opening
discussion
points.
First
of
all,
as
I
said
on
my
message
in
slack,
if
you
have
not
already
see,
oh
people
seem
to
have
frozen
for
me.
Can
people
see
me
everything
going?
Okay,.
A
Okay,
good
sorry,
everyone
seemed
to
freeze.
Another
connection
is
your
mind.
Yes,
has,
I
said
on
slack,
everyone
can
please
make
sure
to
review
the
kubernetes
code
of
conduct
which
covers
all
of
our
conduct
in
all
kubernetes
meetings,
including
this
one
and
I'd
just
like
to
take
a
moment
to
welcome
all
of
our
new
and
returning
members.
I
know
for
some
of
you.
This
will
be
your
first
time,
interacting
with
the
kubernetes
community
or
open
source
in
general.
A
So
to
you
I
say:
welcome
if
you
are
returning
and
being
on
a
release
team
again
welcome
back,
and
hopefully
we
can
make
this
one
as
fun
as
previous
releases
has
been.
For
those
of
you
not
aware
of
a
general
outline
of
this
meeting
is
we
will
have
a
section
of
open
discussion
topics
and
if
anyone
has
ever
has
open
discussion,
topics
feel
free
to
insert
them
onto
the
end
of
this
list.
A
Then
we
will
go
through
a
series
of
like
sub
team
updates,
where
I
will
call
on
individual
members
to
give
that
then
updates
from
release
branch
management
from
joseph
and
from
myself
and
scalability
for
around
and
finally
we'll
go
through
the
project
board.
This
meeting
typically
lasts
about
45
minutes,
sometimes
a
little
bit
less.
They
will
do
a
hard
cutoff
at
quarter.
Two,
as
I
know,
people
have
a
place
to
be
all
right.
A
The
only
big
thing
I
have
to
say
this
time
ahead
of
my
update
further
down
is
that
this
meeting
is
at
this
time,
because
this
is
when
it
is
traditionally
been
at
this
time.
However,
with
a
new
team,
we
have
new
people
and
therefore
new
availabilities
and
time
zones,
so
I
would
like
people
to
take
a
look
at
this
doodle
poll.
This
is
to
try
to
see
if
there
is
a
better
time
that
can
be
good
for
people.
A
If
people
could
take
a
look
at
that
poll
and
give
a
vote
then,
probably
sometime
early
next
week,
I'll,
maybe
the
monday
we'll
see
if
there
is
consensus
for
a
different
time,
it
will
still
be
on
the
wednesday.
However,
being
said
lucas,
you
had
a
release,
notes
point
to
bring
up
an
open
discussion.
C
Yeah
we
got
some
feedback
that
the
major
themes
section
had
been
particularly
useful
in
1.23
and
then
a
suggestion
that
maybe
adding
more
release
enhancement
blog
links
to
the
major
themes
section
might
be
helpful
for
people.
So
I
was
going
to
try
and
go
ahead
with
that.
A
Yeah,
I'm
very
supportive.
Was
this:
the
feedback
post
on
twitter
that
got
posted
in
in
the
release
the
release
next
channel
is
that
right,
yeah,
yeah,
correct,
okay,
yeah,
I'm
I'm
very
supportive.
Anyone
else
had
any
particular
feedback
on
this
point.
No
comments.
A
That
is
a
good
question.
I
think
we
should.
I
think
we
have
quite
a
lot
of
shadows
here,
so
I
think
it
is
a
good
idea
to
do
shadow
introductions,
in
which
case
I
will
do
these
shadows.
When
I
do
my
update
after
everyone
else,
I
guess
if
we
go
into
enhancement
updates
and
then,
as
you
give
your
updates,
everyone
can
introduce
their
shadows.
E
All
right,
everyone,
enhancement
sheets,
just
started
opening
recently
two
days
ago,
so
our
current
status
is
green.
Our
shadows
just
began
working
on
it.
We
currently
have
23
tracked
for
alpha
13,
beta
and
6
stable.
Most
of
these
are
from
stick
storage,
which
is
fine,
I'm
expecting
obviously
a
lot
more
to
come
in
and
to
introduce.
My
awesome
shadows
is
priyanka
on
this
call.
F
G
Hello:
everyone,
my
name
is
hussein,
so
I
work
for
liquid
reply
from
germany.
I've
been
shadowing
ci
signal
for
release,
122
leading
ci
signal
for
release
123,
and
I'm
happy
to
be
back
for
next
release.
Yeah
great
to
be
here.
H
Hi,
this
is
your
jerry.
Can
you
help
me
okay,
so
I
worked
for
google
and
I've
been
working
with
sig
aka
machinery,
anything
called
cloud
fighter
for
quite
quite
a
few
cycles,
so
yeah
this
time.
I
would
really
want
to
try
out
secret
release
and-
and
you
have
my
shadow
thank
you
very
much.
A
Right,
thank
you
very
much
grace
and
welcome
to
all
of
the
enhancement
shadows.
Moving
on
ci
signal
with
leonard.
Am
I
saying
that
correctly?
I
am
aren't.
I.
I
That's
fine
yeah,
so
our
current
status
is
ghetto.
We
have
currently
one
failing
job,
but
it's
been
reported
on
master
blocking
and
also
one
failing
job
on
mass
informing.
They
are
both
actually
relate
to
the
same
issue,
so
they
have
been
reported
with
the
same
github
issue.
I
So
besides
that,
I
think
it
looks.
It
looks
fine
regarding
the
shadow
onboarding.
We
have
next
week
on
wednesday,
a
session
a
team
session,
so
to
see
a
signal.
The
new
shadows
get
basically
an
introduction
what
they
have
to
do,
and
so
on
and
after
that
I
plan
to
do
a
101
with
each
shadow
and
yeah.
I
The
org
membership
has
also
been
requested
today
and
we
start
using
the
new
ci
signal
project
board,
starting
with
this
release.
So,
if
you're
interested
in
basically
checking
the
current
status,
go,
go
to
that
board
and
also
feel
free
to
leave
any
response
or
whatever,
because
this
is
something
new
for
this
release
and
we
try
out
this
new
project
board
so
feel
free
to
leave
a
comment
and
yeah
this
week
we
also
posted
the
first
weekly
report
to
the
google
group
to
kdf
and
also
to
the
release
ci
signal
channel
and
yeah.
I
The
ci
signal
report
tool
is
also
work
in
progress,
so
also
feel
free
to
leave
any
response
to
that
yeah.
So,
regarding
the
shadows,
I
know
that
shuhei
is
unavailable
because
he's
in
japan
and
it's
3
am
in
the
morning
and
lara
is,
I
think,
also
unavailable.
J
Exactly
that's
me
christophed
here
hi,
I
joined
the
release
team
in
122
as
a
bug,
trial
shadow
was
bug,
triage
lead
in
123,
and
now
I'm
happy
to
support.
Is
this
ci
siebel's
shadow
yeah,
looking
really
forward
to
work
with
you
all
guys
and
yeah
see
you
soon.
I
Okay,
awesome,
so
that's
it!
I
think
next
next
week
the
other
shadows-
or
maybe
I
don't
know
about
shuhei
because,
as
I
said
he's
in
japan,
maybe
the
first
meeting
he
will
be
able
to
join
is
during
the
burnout
burnout
meeting
phase
so
yeah.
Okay,
thank
you.
A
All
right,
thank
you
very
much
and
welcome
to
their
ci
signal
shadows.
Moving
on,
we
have
book
triage
with
josie.
Is
that
how
apologies
I'm
association.
L
Yeah,
it's
perfect
hi.
My
name
is
jyoti,
I'm
the
buck
trash
shadow
for
124..
I
was
the
bug.
Trash
am
backed
shadow
in
123
earlier,
but
I'm
supporting
it
as
a
lead
this
time.
So
we
for
the
status
part
we
are
in
yellow
the
reason
we're
going
to
do
is
we
have
a
blocking
issue
already
before
the
docker
shim
issue.
L
So
there
has
been
conversations
on
that
issue
so
far,
so
I
have
been
tracking
it
and
for
other
things
we
have
a
few
important,
soon
issues,
but
nothing
out
of
the
blue
about
how
the
team
is
doing
so
we
got
bootstrapping
this
week,
so
the
members
are
joining
the
all
the
the
distribution
list
that
they
need
to.
We
are
talking
about
that
in
our
in
our
chat,
slide
chat.
L
So
that's
about
the
status
and
how
the
team
is
going.
The
team
is
geographically
distributed,
so
we
are
trying
to
make
it
as
synchronous
as
much
as
possible
through
slack,
we'll
see
how
that
goes
so
yeah
and
time
to
introduce
the
shadows.
So
I
know
that
deepto
is
with
us.
Do
you
want
to
talk.
M
Hi,
I'm
ditto,
I'm
currently
a
student
and
I'll
be
joining
cisco
as
a
intern.
This
is
my
first
time
being
part
of
the
shadow
team
and
I
look
forward
to
working
with
everyone.
L
Welcome-
and
I
think
we
have
with
us.
N
Hi
everyone-
this
is
ritu.
I
am
currently
working
at
linkedin,
ask
in
freissari,
and
this
is
my
third
time
with
the
release
team.
I
have
been
shadow
dog,
shadow
and
bhakta
shadow
and
I'm
again
joining
us,
but
because
I'm
very
excited
for
it.
Looking
forward
to
working
with
you
all.
Thank
you
happy
wednesday.
L
Okay,
welcome
ritu,
and
I
think
I
have
igor
with
us.
O
L
That
sounds
good,
welcoming
her
and
we
have
one
member
heba.
I
don't
see
her
on
zoom.
Maybe
it's
a
different
name.
Are
you
here.
P
A
Thank
you
so
much
and
welcome
to
all
of
your
shadows
as
well.
Moving
on,
we
have
docs
with
nate.
B
Hello,
everyone
current
status
is
green.
We
are
very
much
just
starting
up,
so
there's,
I
think
very
little
for
to
go
wrong
for
docs.
At
this
point,
we've
done
our
shadow
selection.
We
reached
out
to
everybody.
B
We
actually
had
our
first
onboarding
meeting
this
morning,
so
we've
met,
we've
all
met
each
other,
there's
still
a
couple
of
bits
here
and
there
that
we
need
to
make
sure
that
we've
all
got
access
for
and
all
that
sort
of
stuff,
but
things
seem
to
be
moving
along
quite
nicely
on
the
more
technical
side,
we
have
already
got
the
integration
branch
up
and
running
and
it
can't
help
but
be
healthy.
B
At
this
point,
I
think,
but
it's
there
if,
if
you
want
to
follow
along
and
as
for
the
doc's
shadows,
I
think
we
have
two
on
the
line
here.
Mayha
are
you?
Are
you
with
us
right
now.
Q
B
Thank
you
and
I
think
the
other
shadow
we
have
on
the
line
is
chris.
Are
you
still
are
you
still
with
us.
R
Yep,
I'm
here
yeah.
This
is
my
third
time
as
release
doc
shadow
and
I
work
for
aws
as
my
my
job
and
looking
forward
to
the
challenges
of
this
new
release.
Thanks.
Thank
you.
B
And
the
the
two
that
aren't
on
the
line
we
have
victor
pilate,
who
was
a
released
docs
lead,
I
believe,
for
one
two,
two
or
one
two
one,
but
was
fairly
recently
a
lead,
and
then
we
have
a
new
person.
B
A
sick
pool
and
she's
new
to
the
project,
but
we're
very
excited
to
have
her
and
show
her
how
how
things
are
done.
So
I
think
that's
the
docs
update.
C
Hello:
everyone,
I'm
luke,
destroyer,
currently
release
note
status
is
green.
The
shadows
have
been
selected
and
confirmed
the
1.24
alpha,
1
pr's
are
expected
to
be
done
this
coming
week
and
then
we're
I'm
still
setting
the
team
onboarding
meeting
and
one-on-ones,
and
then,
after
that,
I
just
have
to
confirm
that
they've
got
krell
set
up
correctly
and
that's
it
for
the
update
I'll,
introduce
my
shadows.
Parole.
Are
you
here.
O
S
Yeah
so
hello,
everyone.
I
was
a
part
of
the
release:
kubernetes
release
1.23
as
a
release,
no
shadow,
and
I
like
the
role
a
lot.
So
I'm
back
again
again
shadowing
for
release.
Note
sub
team
for
kubernetes
1.24
and
I'm
currently
in
my
junior
year
of
college.
C
Okay
and
then
next
also
returning,
we
have
our
sharma.
K
C
All
right,
and
then
we
have
carlos-
are
you
here.
U
Yes,
I'm
here,
can
you
hear
me
yeah,
oh
yeah,
carlos
antenna
and
new
to
the
sick
release?
Thank
you
so
much.
Whoever
accepted
me
to
this
run
great
group
of
folks
excited
to
to
join
and
learn
and
provide
value
so
looking
forward
to
meeting
everyone,
I'm
on
the
east
coast,
north
carolina
in
time
zone.
So
I
appreciate
the
trust.
C
All
right,
thank
you
and
that's
it
for
us.
A
All
right,
thank
you
very
much
and
welcome
to
all
of
you
and
then
comes
with
mickey.
V
Good
morning,
so
we
are
green
because
it's
it's
comms
and
it's
early
in
the
release
cycle,
so
I
am
cautiously
optimistic
that
we're
going
to
get
everything
out
on
time.
Our
shadow
selection
is
complete
and
everyone
is
confirmed.
In
fact,
we
have
a
quorum.
All
of
our
shadows
are
on
the
call
today
we're
doing
on
our
onboarding.
V
Tomorrow
morning
we
are
a
very
global
team,
so
we
you
know
we're
able
to
try
to
figure
out
a
perfect
time
for
us
to
all
connect
and
then
this
release,
in
addition
to
the
typical
comms
processes
that
we
need
to
keep
track
of.
We
also
have
the
shimmed
application
to
think
about.
So
we
have
a
few
sort
of
side
projects
that
add
on
to
our
normal
workload,
but
anyway,
nice
to
see
all
the
familiar
faces.
V
W
Hey
y'all,
my
name
is
kat.
This
is
my
cat.
I
work
at
palomi,
I'm
a
developer
advocate
there,
but
I'm
also
a
cncf
ambassador
and
am
unfortunately
was
at
fault
for
part
of
the
original,
dr
shem
disaster,
getting
so
completely
out
of
control
in
the
media.
So
I
am
returning
to
comms
to
hopefully
make
sure
that
that
does
not
happen
again.
V
Cool
thank
you
cat
and
also
another
cat,
and
then
I
see
that
saul
who's,
one
of
my
new
shadows,
can't
introduce
himself
verbally.
So
he
has
a
message
in
the
chat.
If
folks
want
to
read
that,
and
then
also
I
haven't
met
everyone
too
closely
yet
but
deborah,
I
know
we
met
on
the
contrabex
call.
Do
you
mind
introducing
yourself
next.
P
Yeah
hi
everyone
hi,
I'm
devrata.
I
am
a
presently
an
undergraduate
student
from
india.
This
is
my
first
time
in
release
team.
Apart
from
release
team,
I
work
closely
with
upstream
marketing.
Team.
Nc
contributes
I'm
one
of
the
folks
behind
the
most
of
the
tweets
you
see
in
kids,
contributor,
christian
yeah.
That's
all
about
me
excited
to
be
in
the
comms
team,
especially
during
docker
ship
replication.
V
Perfect,
thank
you
and
then
finally,
parthvi,
do
you
mind
introducing
yourself
as
well.
V
All
right
and
to
not
put
too
much
pressure
on
your
typing:
let's
we
can
segue
on
to
release
branch
management
and
then
come
back.
A
Sure,
well,
thank
you
for
the
update
and
and
welcome
everyone
all
right.
That's
all
of
the
kind
of
major
sub
teams
with
shadows.
We
do
some
other
people
to
hear
from,
however,
starting
off
with
release
branch
management-
and
this
is
by
nabaroon.
X
Yeah
welcome
everyone,
first
of
all
to
the
release
team,
all
returning
members
and
as
well
as
like
new
members
of
the
team
and
happy
time
of
the
day,
so
I'm
novaron.
This
is
me
doing
releases
for
the
seventh
time
three
times
in
the
announcements
team
two
times.
X
Lead
team
led
one
to
one
and
two
times
in
branch
management,
so
yeah
good
to
have
you
all
here
I
will
have
one
branch
manager,
shadow
and
hopefully
we
will
introduce
them
in
the
next
meeting
next
week.
So
and
status
is
green
on
our
site,
nothing
much
to
do
until
the
first
alpha
two
cut,
which
is
situated
in
first
week
of
february.
X
Other
than
that
we
are
good
to
go.
We
will
communicate
with
the
ci
signal
team
when
we
are
near
that
cut
time
frame.
A
Y
Y
I
had
to
serve
as
a
lead
last
time
with
the
last
release,
as
well
as
now
getting
to
serve
as
ea,
and
I'm
very
very
grateful
for
this
role
and
just
to
be
able
to
work
directly
with
all
of
you
is
is
a
real
privilege,
and
I
just
think
about
you
know
some
of
the
goals
I
set
for
myself
during
this
release
cycle
is
really
to
kind
of
like.
Y
I
want
to
make
sure
that
you
really
have
a
safe
space
to
be
able
to
do
your
best
work
and
to
have
a
great
experience
during
this
release
cycle
and
even
further.
I
hope
that,
even
with
this
release
team
there's
so
many
opportunities
within
the
kubernetes
community,
and
if
I
can
help
shepherd
and
guide
and
bring
you
whether
it's
through
the
release
team-
maybe
really
you
lead
a
release
one
day
or
jump
into
sig
release
or
all
these
other
sigs.
Y
Y
I
will
be
setting
up
some
time
so
that
we
can
do
a
shadow
orientation
for
those
of
you
that
are
new
others
who
have
been
here,
you're
welcome
as
well
and
then
as
well
as
just
trying
to
do
some
outreach
with
james
as
well
just
to
make
sure
that
all
the
things
that
you
need
to
be
effective
in
this
role
is
met
and
help
the
leads
as
well
as
they
also
groom
you
as
you
develop
into
maybe
possibly
becoming
a
lead
as
well.
But
so
far
this
release
has
gone
great.
Y
I'm
really
happy
to
have
all
these
shadows.
Selected
elites
did
a
great
job,
and
so
thanks
for
your
partnership
there
and
really
helping
us
reach
that
goal
of
a
criteria
of
making
sure
that
you
know
we
have
a
real,
diverse
team
that
is
really
representative
around
the
world.
So
I'm
really
excited.
Thank
you
all
for
letting
me
be
a
part
of
this,
and
I
just
look
forward
to
this
release.
A
Excellent,
thank
you
joseph
thank
you.
Thank
you
for
those
words
all
right
moving
on
me
so
there's
I
didn't
actually
introduce
myself
kind
of
properly
as
the
others.
So,
as
I
said,
my
name
is
james.
I,
in
my
day,
job
work
for
a
company
called
jet
stack
of
cert
manager
fame.
If
anyone's
heard
of
that,
I
work
as
a
senior
solutions
engineer
about
that.
So
I
work
with
kubernetes
during
my
day
job
and
then
in
every
other
time.
A
I
I
kind
of
bumble
around
and
see
release
more
than
anything
else.
This
is
also
my
seventh
release.
I
figured
out
the
other
day.
I
started
back
on
118
and
I've
been
part
of
every
release
team
since
then,
so
I've
been
doing
this
for
quite
a
while.
At
this
point,
comparatively
speaking,
I
was
a
release,
notes
lead
back
in
120
and
I
was
enhancements
leading
122.
A
so
now
just
doing
doing
this
is
a
fun
fun
experience,
so
yeah
welcome
to
all
the
familiar
faces
and
and
new
faces
as
well.
In
terms
of
me,
my
onboarding
is
ongoing.
I
have
a
very
long
list
of
tasks
involving
setting
permissions
and
rpr'ing
things.
One
of
the
things
I'm
making
a
conscious
effort
to
try
to
do
is
put
as
much
of
the
stuff
that
the
release
team
kind
of
leads
do
in
public
as
possible.
A
So
if
you
follow
sig
release
the
slack
channel,
there's
a
lot
of
spam
of
me
in
there
asking
random
questions
and
setting
things
up
and
opening
pr's.
So
if
you're
at
all
interested
in
the
maya
tale,
what
I'm
doing
it's
it's
in
there,
I
still
need
to
update
the
slack
and
github
permissions
for
everyone
that
is
is
coming,
I'm
working
on
that,
but
everyone
should
now
be
in
the
release
team
group.
There
is
one
note
on
that.
A
I
took
people's
emails
from
the
shadow
survey
so
for
some
members
this
is
not
the
email
that
they
wanted
to
use
for
this.
If
that's
the
case
either,
let
me
know
we'll
just
open
up
yourself
and
I'll
approve
it
to
get
that
fixed,
which
might
be
useful
for
like
permissions
to
access
this
document,
for
example.
So
you
know
I've
got
a
note
in
the
retro
doc
about
that.
The
other
thing
I've
been
doing
is
meeting
a
whole
bunch
of
sigs.
A
One
of
my
modding
tasks
is
to
meet
with
every
sig
and
there's
like
25
of
them,
so
I'm
going
to
be.
I've
spent
the
past
week
in
meetings
I'm
going
to
spend
the
next
week
in
meetings,
but
I
think
it's
quite
valuable
to
go
around
and
speak
to
everyone.
A
They
all
know
all
the
dates,
because
you
know
they're
out
everyone's
already
aware
of
that,
but
it's
just
nice
to
kind
of
touch
in
with
people
and
ask
if
they
have
questions
and
that
sort
of
thing
for
new
members,
you
should
be
able
to
get
org
membership.
If
you
need
a
plus
one,
just
just
ping
me
or
tag
me
you'll
assign
me
any
of
that
is
fine,
along
with
your
kind
of
role.
A
Lead
is
generally
a
thing
or,
if
I'm
unavailable,
for
whatever
reason
joseph
I'm
sure
would
also
be
quite
happy
to
you
know
or
be
failing
that
secretly,
these
technical
leaves
and
chairs
and
such
all
right
before
I
move
on
I'd
like
to
introduce
my
shadows.
Like
every
other
group,
I
also
have
shadows.
These
are
generally
experienced
contributors
to
the
release
team.
I
also
have
four
of
them.
I
think
they're
all
around,
maybe
we'll
see
start
out
with
max.
Z
AA
Yeah,
hey
everybody,
I'm
xander!
I
have
been
involved
in
the
release
since
1.20
across
coms
and
enhancements
teams
professionally
work
on
kubernetes
at
twitter
yeah.
I
think
joseph
alluded
to
this
earlier,
but
you
know
we
are.
We
are
shadows
for
james,
but
as
all
of
us
on
the
lead
shadow
team
have
been
involved
in
the
release
for
a
while.
I
think
we
are
all
here
to
support
all
of
you
as
well.
So
as
shadows,
please
feel
free
to
reach
out
to
any
of
us
anytime.
AA
I
think
across
the
group
of
lee's
shadows,
we've
shattered
across,
like
the
whole
release
team,
so
yeah
here
to
support
you
in
whatever
way
we
can.
A
I
don't
see
us,
you
might
not
be
able
to
make
this
one,
in
which
case
jessie
you
around.
AB
Hey,
as
happens
one
out
of
five
calls,
my
video
will
not
turn
on
so
you'll.
See
me
again:
sometime
yeah,
I'm
jesse
most
recently
led
ducks
for
123
and
comes
for
122
and,
like
xander,
said
yeah
just
reach
out.
We
are.
We
are
here
to
help.
AB
We
are
here
to
learn
from
you
partially
how
to
make
things
work
better
partially
how
to
make
it
work
better
for
you,
this
whole
release
team
revolves
around
you,
folks,
putting
in
the
hours
showing
up
so
super
happy
to
be
here
and
yeah.
That's
that's
me
what
else?
Oh
yeah!
I
work
at
aws
if
that
matters
right.
A
All
right,
thank
you.
So
much
I
don't
see
cc
on
the
member
list,
so
I'm
sure
you
can
introduce
yourself
next
time
in
which
you
guys,
I
think
that's
everything
from
me.
We
should
have
an
update
from
sixth
scalability,
but
this
is
my
bad.
I
forgot
to
ping
them.
Is
anyone
from
ski
giveability
just
happen
to
be
on
the
call
anyway.
A
Nope
doesn't
sound
like
it,
I
will,
I
will
remember,
to
chase
them
up
next
time.
This
is
that's
my
fault
all
right.
That's
the
end
of
a
major
part
of
the
update.
The
last
thing
I'd
like
to
do
is
take
a
quick
look
at
the
project
board,
but
before
I
do
that,
does
anyone
have
any
questions
or
or
updates
or
things
to
mention
before
we
move
on
to
that.
Z
I
just
want
to
quickly
introduce
myself
my
name's
domin.
I
was
on
the
release,
notes,
shadow
team
for
one
two,
two
and
one
two:
three,
I'm
not
officially
part
of
the
this
release
cycle,
but
I'm
still
sticking
around.
If
anyone
in
the
release
notes
team
has
any
questions
comes
up
with
any
problem
with
corel
or
anything
else
feel
free
to
ping
me
on
slack
or
even
tag
me
in
the
pull
requests
for
review
or
anything
that
you
need
I'll,
be
more
than
willing
to
help.
You
guys
folks.
A
Thank
you.
It's
lovely
to
have
you
around
and
see
your
face
again,
a
couple
of
notes.
Actually
that
has
reminded
me
for
those
that
might
not
be
aware
a
couple
of
terms
that
we've
used
krell
krell.
However,
I
want
to
say
it
is
a
release,
notes
tool,
the
source
code
that
is
available
on
on
github.
A
If
people
are
interested
and
also
the
docusign
thing,
I'm
not
sure
if
everyone
is
fully
aware,
but
docker
shim
is
a
feature
I'm
going
to
say
of
kubernetes
that
was
deprecated
a
few
releases
ago
and
is
being
removed
as
of
this
release,
and
this
has
some
wide-ranging
applications
for
cluster
administrators.
So
there
is
a
a
big
communications
effort
around
that
removal.
The
actual
removal
technically
has
already
happened.
If
you
pull
the
the
latest
kind
of
main
development
version
of
kubernetes
and
run
it,
you
can
run
it
without
it
there.
A
If
you
want
more
information
on
that,
there
are
innumerable
resources
that
is
going
to
be
a
big.
A
big
theme
of
this
release
is
communicating
correctly
around
around
darker
shims
you'll.
Probably
hear
that
coming
up
quite
a
bit
grace
you
raise
your
hand.
E
A
My
understanding
is
that
at
the
moment,
kept
ctl
another
kind
of
command
line
tool
into
the
community
is
used
promoter
by
the
prr
team.
I
don't
think
the
enhancements
project
team
is
intended
to
use
it.
Yet
there
was
talk
of
changing
that.
I
think
this
is
tied
up
in
the
various
attempts
to
overhaul
the
release
process.
Y
Y
Y
It's
kind
of
useful
in
that
sense,
if
you
don't
want
to
go
drill
through
the
github
ui
or
if
you
don't
want
to
like
grab
through
directories,
it
works
out
pretty
well
there.
It
has
some
abilities
to
like
scaffold
out
a
new,
a
new
kappa
stuff
as
well,
but
I
think
the
primary
use
case
for
right
now
is
doing
querying.
A
All
right,
thank
you,
jeremy.
Does
that
mostly
answer
your
question
chris
cool
all
right
guys,
we've
got
some
links
put
in
here
excellent!
Thank
you.
Okay.
Let's
take
a
very
brief
look
at
the
releasing
board,
so
this
is
a
board
on
github,
which
largely
describes
kind
of
wide
ranging
things.
A
lot
of
these
won't
be
directly
relevant
to
the
present
release
immediately,
but
might
come
up
kind
of
future
and
will
inform
the
release
process
in
general.
A
So
it's
useful
to
keep
an
eye
on
these
at
least
one
every
once
in
a
while
there
are.
I
haven't
actually
looked
at
this
in
any
great
detail,
so
there's
nothing
in
review
or
blocked
waiting
in
progress.
We
can
take
a
look
at
these.
We
are
refining
when
we
communicate
deprecations
and
wide
reaching
changes.
Oh
yeah,
so
this
is
a
big
when
it
comes
to
like
docker,
shim
and
other
things
like
this.
We
are
looking
to
basically
just
learn
how
to
communicate
this
a
little
bit
better.
AB
Hey
sorry,
I
was
muted
yeah.
I
made
a
comment
on
that,
like
I,
I
think
this
really
just
came
out
of
like
let's
put
this
into
the
release
cycle
intentionally
and
so
we've
we
discussed
it
in
the
123
retro
and
I
added
it
to
some
updates
to
the
comms
handbook,
which
that
pr
is
just
kind
of
out
there
right
now,
but
as
soon
as
that
merges,
I
I
think
it
goes
a
long
way
toward
resolving
what
we
need
here.
A
AB
So
that
was
in
desperate
need
of
an
overhaul
anyhow,
so
the
pr
is
a
little
bigger
than
just
that,
but
but
yeah
we
we've
we've
basically
added
in
an
intentional
part
of
the
of
the
comms
team
role
to
to
help
identify
whether
or
not
a
release
warrants.
AB
You
know
extra
communication
about
deprecations
and
removals
and
a
blog
to
to
do
just
that
and
facilitating
that
getting
out
the
door.
So
I'm
not
sure
it
fully
addresses
everything
that
came
up,
but
I
think
there
was
a
lot
of
brainstorming
in
there
too,
and
most
people
agreed
that
that
was
what
we
needed.
A
AB
AB
That's
what
I
was
hoping
for:
mickey's
team
to
basically
have
a
a
fresh
copy
of
this.
As
far
as
I
know
that
that
pr
is
in
good
shape,
I
just
rebased
it
this
morning.
I
just
added
some
stuff
from
karen.
So
if
anybody
has
approved
rights
there,
just.
AB
A
You
know,
I'm
just
gonna.
It's
probably
fine
that
should
just
get
emerged.
Maybe
okay
we're
going
back
to
that,
but
cool
okay.
So
this
needs
to
stay
here,
even
if
it
merges,
because
there's
a
few
other
bits
is
that
right.
AB
Y
Y
I
think,
let's,
let's
explicitly
drop
into
that
thread
and
ask
if
this
action
closes
it
and
we
can
maybe
maybe
discuss
with
drop
it
into
controb
controbex
to
say
like
to
get
their
input
as
well.
But
I
I'm
agreement
that
it
pretty
much
wraps
up
the
gist
of
what
that
issue
was
discussing.
It
gives
us
a
process,
and
I
think
it's
it's
pretty
straightforward.
A
O
A
There
we
go
cool,
okay,
we
gotta
watch
right,
yeah,
we'll
get
that
merch
and
we'll
we'll
circle
back.
Okay.
I
guess
we'll
touch
back
on
this
next
time.
We
are
at
43
minutes
past.
So
I'm
not
going
to
go
on
to
the
next
issue,
but
we
can
just
kind
of
slowly
plod
away
at
these
kind
of
like
one
or
two.
Each
meeting
just
get
an
idea.
A
What's
going
on
with
them
all
right
from
here,
I'm
going
to
end
the
recording
unless
anyone
else
had
any
particular
things
to
bring
up
at
this
time
on
the
recording.