►
From YouTube: Kubernetes SIG Storage Meeting 2021-05-06
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 06 May 2021
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.sufi7vkkabhg
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Saad Ali (Google)
A
Okay,
so
today
is
may
6
2021.
This
is
the
meeting
of
the
kubernetes
storage
special
interest
group.
As
a
reminder,
this
meeting
is
public
recorded
and
posted
on
youtube.
So
today
we're
going
to
go
over
the
agenda
listed
here
specifically
last
meeting.
We
started
the
kubernetes
122
planning.
A
We
have
our
planning
spreadsheet,
we
started
going
through
it.
We
transferred
the
items
that
we
had
from
121
into
122
to
see
what
was
left
over
and
and
kind
of
going
through,
that
list
to
see
what
should
remain
in
122
and
what
should
be
eliminated,
and
if
you
have
any
items
that
you
want
to
add
please
speak
up,
we
can
add
them
to
the
spreadsheet,
for
the
sig
to
track
and
if
you're
looking
for
things
to
work
on.
A
This
is
a
good
time
to
speak
up
as
well
since,
when
we're
going
through
this
we're
gonna
assign
folks
as
primary
developers
and
reviewers.
So
if
you
want
to
participate,
that
could
be
an
opportunity
for
you
for
people
that
are
working
on
a
feature
delivered
for
122.
Please
keep
track
of
the
122
release
schedule
in
general.
A
The
release
schedule
is
a
little
bit
looser
than
it
used
to
be
because
we're
now
doing
three
releases
a
year
instead
of
four,
so
the
code
complete
is
out
in
july,
8th
and
the
release
isn't
going
to
happen
until
august
4th,
but
important
to
note
that
the
enhancement
freeze
is
coming
up
very
quickly,
may
13th,
which
is
about
a
week
away.
A
This
is
the
deadline
by
which
the
cap
for
any
of
the
features
that
are
going
into
122
must
be
approved
and
merged,
and
in
addition
to
that,
you
have
to
have
your
pr
review
completed
and
you
need
to
make
sure
that
the
122
release
team
they
have
their
own
spreadsheet,
that
your
feature
is
listed
on
that
spreadsheet
to
be
tracked,
so
that
deadline
is
coming
up
fast
if
you're
working
on
a
feature
for
122.
Please
be
aware
of
that,
and
so
with
that
we're
going
to
jump
back
into
the
spreadsheet.
A
In
the
last
meeting,
we
stopped
after
the
new
rwo
access
mode
item,
which
was
number
21
here
before
we
continue.
I
wanted
to
follow
up
on
number
14
and
15.
I
guess
in
for
122
we're
saying
we
don't
need
this
anymore.
Is
it
okay?
If
I
go
ahead
and
remove
it.
B
B
A
All
right,
so
then,
let's
continue
with
the
new
rwo
access
mode.
I
I
think
we
were
finished
here
now
it's
assigned
to
chris
and
we
are
going
to
go
to
alpha
this
quarter.
A
Next
item
is
update.
Topology
labels
from
beta
to
ga
leila
is
this
accurate
for
122.
A
Okay
and
it's
still
going
to
ga
yes
perfect,
thank
you
so
we'll
leave
that,
as
is-
and
I
guess,
if
you
have
an
enhancement
issue-
and
I
kept
please
add
a
comment
to
the
link
here
and
we'll
get
this
updated.
C
Just
just
an
update
to
this,
I
think
right
now
we're
only
waiting
for
the
way,
a
sphere
change
other
than
this.
All
the
other
changes
are
are
okay,
the
topology
one.
B
So
if
we
updated
that
in
1.2,
then
this
should
be
all
set
right.
Yes,
exactly.
B
C
A
C
I
think
there
are
a
couple
of
stuffs
we
need
to
do
in
122,
so
basically
we
need
to
deprecate
all
the
plugins
that
will
not
support
csm
migration
or
or
we're
planning
to
support
we're,
not
support
anymore.
So
eventually
we
will.
We
will
remove
all
the
plugins,
but
right
now
we're.
The
first
step
is
to
deprecate
some
unsupported
plugins.
C
This
is
the
first
stuff
and
also
we
have
we
need
to
remove
some
plugins.
That
is
already
been
deprecated
for
a
long
time,
for
example,
flocker
and
scale
ios.
C
So
those
those
some
of
the
pr's
are
already
out
and
for
the
core
migration.
There
are
also
a
couple
of
small
box
and
issues
that
we
need
to
fix
yeah.
So
that's
why
it's
still
pending
in
beta,
so
for
it
to
go
to
ga.
I
think
there
are
our
couple.
There
is
a
dependency
we
we
wanted
to
follow.
So
basically
we
wanted
to
wait
for
at
least
two
plugins
for
va,
and
then
we
announced
the
core
go.
Ga
got.
A
C
A
We're
gonna
call
it
bug,
fix
for
this
cycle
and
for
deprecation.
Deprecations
are
bug
level
or
do
they
need
a
cap.
A
Okay
sounds
good,
so
we
have
two
items.
One
is
the
core
bug
fixes.
The
second
is
deprecation
of
these
old
entry
drivers
and
removal
of
the
ones
that
have
already
been
deprecated
and
then
for
each
individual
cloud
provider.
What's
the
status.
C
So,
for
we
experiencing,
there
is
some
concerns
from
command.
Some
also,
some
facial
supports
is
hormone
here.
I
think
yeah
yeah.
E
I'm
here
I
I
was,
I
was
talking
to
deviant
and
we
were
talking
about
like
the
nfs
data
store
support
in
vsphere,
csr
driver
a
lot
of
users
use
nfs
data
stores
with
the
entry
driver
right
now.
E
If
you
don't
want
to
support
it
or
like,
if
we
yeah,
I
mean,
if
you
don't
want
to
support
it
further
or
if
you
want
a
future
version
of
easter
seaside
to
support
it,
then
we
need
to
think
through.
Also
devin
was
saying
that
it
might
only
be
available
from
certain
version
of
vsphere
like
so
I
don't
know
if
you
want
to
deprecate
nfc
or
sourcing
kubernetes.
A
That
seems
pretty
bad.
Is
it
just
a
vsphere
version
dependency
or
is
there
other
issues.
E
Sandeep
or
deepan,
are
you
guys
there
like?
If
you
want
to
give
more
background,
I
mean
I
saw
something,
but
I
think
he
dropped
off.
Okay,
so
davin
was
saying
the
view
he's
saying
that,
like
the.
A
E
E
Yeah,
so
this
means
basically
like,
for
example,
if
you're
using
netapp's
integration
with
vsphere,
then.
A
F
Sounds
so
the
this
lfs
data
store
entry
driver,
it
is
the
fs
driver
or
the
vsphere
driver.
E
So
you
can
have
your
data
stored
in
in
vsphere,
hosted
on
any
kind
of
backend
like
it
can
be
nfs,
it
can
be
local
disk,
it
could
be
a
vsan
and
the
entry
diver
supports
all
of
them.
Basically,.
E
A
Okay,
so
I
think
that's
something
we
can
follow
up
on
outside
of
that
are
we
moving
to
beta
this
cycle?
Have
we
already
gotten
to
beta?
What
are
we
doing
for
vsphere
csi
migration?
It's.
A
B
A
Got
it
so
keep
it
in
beta
and
add
these
missing
features:
okay
and
then
for
azure
azure
disk
azure
file?
Are
we
pushing
azure
disk
to
beta
as
well
this
quarter
or
still
holding
off
on
that.
C
It's
already
beta,
it's
just
right
now
off
by
default.
We're
trying
to
maybe
turn
this
on
by
default
through
this
release
got
it,
I
think,
from
either
disk
there's
no
like
outstanding
issues,
but
I
heard
amongst
that
he
had
did
some
testing
for
this
and
then
find
some
bugs.
C
E
Christian,
like
christian
fab,
you're
like
I,
I
was
just
traveling,
the
the
cs-
employment
migration
meeting,
we're
just
talking
about
the
e2e
failures
we
are
finding
in
these
drivers,
so
I
I
think,
like
most
of
our
failures,
were
related
to
snapshot
and
resizing
for
as
you
described
christian,
are
you
there?
I'm.
G
G
D
A
So
any
any
csi
migration,
specific
failures.
G
A
Okay,
so
I
think
we'll
keep,
I
guess,
we'll
target
a
beta
and
on
by
default,
this
cycle.
H
E
A
Right,
and
so
does
that
mean
we
have
to
wait
until
item
two
goes
to
beta.
I
E
A
I
got
it
okay,
that
makes
sense.
In
that
case,
I
think
we
would
have
to
hold
off
then
blocked
on
item
two.
A
On
this
got
it,
I'm
gonna
mark
this
as
crossed
out,
so
that
we're
not
tracking
it
for
this
cycle,
but
we'll
keep
an
eye
on
it
for
the
next
cycle,.
A
Okay
and
then
on
the
gce
side,
what's
the
plan
here.
I
So
I
think
we
want
to
go
to
ga
and
122..
I
The
only
reason
why
we
didn't
get
that
in
121
was
because
making
the
pcsi
on
by
default
for
like
the
tests
and
stuff
was
a
little
trickier.
We
didn't
give
ourselves
enough
time,
but
for
1.2
it
should
be
fine.
We're
still
on
track
to
launch
this
in
gke
and
121.
I
So
that
should
be
good
and
just
as
as
an
aside,
this
process
has
actually
revealed
a
couple
pre-existing
bugs
in
the
side
cars.
So
you
know
I,
I
guess
that's
good.
A
Nice
all
right
that
sounds
awesome,
so
hopefully
we'll
be
able
to
hit
that
and
get
the
first
driver
g8
for
csi
migration.
C
For
aws,
I
think
one
outstanding
issue
is
the
windows.
Support
got
it.
That
is
still
missing.
I
think
matt
said
he
already
has
a
prototype
or
something.
D
J
I
I'm
okay
with
that.
Actually
I
mean
I
I
think
for
me.
The
most
important
thing
is
to
have
it
on
by
on
my
aha
like
to
get
it
exercised
in
tests
and
stuff.
So
yeah,
that's
like
I,
I
guess
that's
the
the
difference
between
beta
and
ga
when
it's
on
by
default
is
not
as
clear
to
me.
So
yeah,
I'm
happy
to
discuss
that
further.
I
See
yeah,
that's
a
good
good
point.
A
Jo
any
concerns
with
keeping
in
beta
but
on
by
default.
C
Yeah,
I
think,
let's
keep
it
beta
this
release
and
then
we
can
go
gia
next.
Release
sounds
good
to
me.
Thank.
D
C
A
And
okay
so
sounds
like
that's:
we're
going
to
keep
it
in
beta
and
on
by
default
for
gc
for
aws
beta
and
we're
adding
support
for
windows
support.
I
wanted
to
double
check.
Is
this
going
to
be
on
by
default
or
not.
C
I
think
the
plan
is
to
by
default
this
release,
but
then
I
don't
know
if
the
windows
support
is
going
to
be
ready
by
the
time
so
yeah.
We
will
see
okay.
K
A
E
F
Right,
we
have
the
ga
plan,
but
we
got
a
good
review
from
michelle
about
api,
so
we
are
going
to
have
some
api
changes
and
all
the
drivers
who
are
using
beta
cesar.
L
F
Api
need
to
handle
the
difference
between
beta
api
and
the
weaver
api,
so
just
to
let
everyone
know
yeah.
I
F
There
will
be
api
changes,
so
all
the
drivers
who
using
cs
epoxy
need
to
be
aware
and
need
to.
F
Right
now
we
haven't
finished
like
updating
the
api.
Yet
so
we
have,
we
opened
a
number
of
issues
based
on
the
feedback
and
so
it's
under
css
proxy
repo,
and
you
will
see
all
the
proposing
api
changes
in
those
issues.
F
A
F
And
like
a
maurizio
like
a
group
of
people,
yeah.
F
Me
deep
michelle
and
mauricio
kalia
like
so
yeah
you
can.
A
Probably
put
you
in
deep
as
the
primaries
here.
Okay
sounds
good
and
maybe
what
would
be
useful
is
to
send
a
message
to
the
csi
announcement
mailing
list
which
a
bunch
of
developers,
csi
developers
are
on
to
say,
hey
heads
up
if
you
added
windows,
support
you're
going
to
need
to
update
before
ga
sure,
never
do
that
all
right
cool!
Thank
you.
So
we
just
discussed
aws.
What's
going
on
with
cinder.
C
So
cinder
has
been
turned
on
by
default
previous
release.
I
think
this
release.
J
A
Got
it
so,
let's
just
cross
it
out
for
this
release
means
we'll
watch
it
and
see
what
happens
and
then,
if
everything
goes
well,
then
ga
next
cycle
yep
sounds
good
and
then
seth.
C
Yeah,
I
don't
know
if
humble
is
here,
I
had
some
discussion
with
him.
It
seems
that
hey
it's
due
trying
to
decide
if
it
want
wants
to
support
the
csm
migration.
For
this
I
saw
he's
not
here,
so
I
guess
I'll
sync
up
with
him
offline
and
see
an
update
here.
A
Okay
sounds
good
and
then
updated
topology
labels
we
already
discussed
okay,
so
we've
got
a
good
idea
of
csi
migration.
Great
work
on
all
of
this,
for
everybody
who's
been
working
on
it.
This
is
a
massive
effort.
It's
thankless
work,
everybody
likes
to
work
on
fancy
new
features
and
not
really
on
any
of
the
tech
debt.
So
thank
you
for
all
your
hard
work
on
on
making
progress
on
this
next
up.
A
I
think
we
have
a
set
of
sig-
or
I
guess,
co-owned
items,
but
before
that
I'm
gonna
pull
these
other
items
up.
Let's
do
this.
B
This
is
it's
mainly
like
a
bug
fix,
but
because
we
need
to
deprecate
an
existing
behavior.
So
we
added
a
cap
here
yeah.
So
the
the
cap
is
already
out.
B
That's
the
basic
proposal
there
so
yeah.
I
assign
that
to
you.
Can
you
take
a
look
because
I
think
you
are
most
familiar
with?
Is
that
the
pvpc
controller.
B
So
the
issue
basically
is
the
depending
on
so
it's
about
pure
uvvc,
depending
on
whether
you
start
by
deleting
the
pvc
first
or
start
by
deleting
the
pv
first.
The
end
result
is
different.
If
you
start
by
deleting
pvc
first,
then
everything
will
be
deleted
from
the
storage
system,
but
you
start
by
dealing
tv
first
and
then,
even
if
you
go
ahead
and
delete
pvc
everything,
the
api
objects
are
all
deleted
from
kubernetes,
but
the
storage
on
the
source
side.
B
The
bottom
is
left
yeah,
so
the
change
is
just
to
always
honor
the
deletion
policy.
If
it
says
delete,
then
we
always
delete
it.
Doesn't
matter
whether
you
try
to
ddtv
or
pvc
first.
B
No,
so
so
right,
the
purpose
piece
right
now
in
the
cup
is
basically
just
know
that
we
have
a
check
for
a
time
stamp,
basically
in
the
if
the
p,
if
the
timestamp
dealing
timestamp
was
added
early,
when
you
try
delete
pv
first,
then
we
actually
skip
it.
We
don't
go
so
so.
The
proposal
right
now
is
just
remove
that,
but
I'd
like
yandere
to
take
a
look
and
see
if
that
has
any
consequences.
B
A
F
Oh
sorry,
if
it
goes
through
alpha
beta,
like
that
means
also
has
like
a
feature
gate.
B
Yeah
yeah,
so
we
we're
going
to
have
the
educate,
because
this
is
an
existing
behavior
that
we
don't
know
if
anyone
is
depending
on
this.
B
That's
what
I
thought
so
I
I
don't
know
if
you
know
I
think
you
know
this
is
really
something
that
we
should
keep.
Then
we
just
fix
it
easier.
What
do
you
guys
think.
B
B
But
if
someone
is
kind
of
relying
on
this
behavior,
then
you
know
we
need
to
have
this
deprecation
going
through
the
future
gate,
so
yeah
sure.
J
Yeah,
it
is
a
behavior
that
we
have
since
kubernetes
1.0.
Actually,
so
I
I
don't
think
anybody
is
like,
depending
on
the
behavior,
but
I
would
be.
I
would
prefer
to
be
on
the
safe
side
and
have
feature
gate
and
proper
deprecation
and
everything.
B
B
Oh
so
this
is
that
the
potential
safety
issue,
so
I
think,
we'll
just
need
to
work
on
the
design,
because
we
don't
have
a
good
solution.
Yet.
D
B
So
yeah,
so
we
well.
We
haven't
really
spent
my
time
on
this,
but
I
look
at
it
so
yeah.
So
I'll
start
with
some
proposal.
B
A
A
A
A
E
No,
actually
it's
because
the
this
the
cap
is
kind
of
incomplete
me
and
yan
reviewed
it
and,
unless
like
they
want
to
set
like
preserving
the
default
mode,
is
not
possible
unless
we
also
start
changing
the
volume
ownership
by
user
id,
which
we
currently
do
so
so
the
the
kept
must
be
modified
to
set
ownership
by
user,
and
that
opens
up
a
little
bit
more
discussion
about
like
currently
in
kubernetes.
We
don't
support
uid
based
ownership
of
volumes.
A
E
Yeah,
I
don't
know
if
I'm
sick
is
that
but
yeah
I
don't
know
if
his
I
point
there
was
a
projected
account
token,
a
cap
that
was
recently
merged
last
quarter
where
they
decided
to
use
fs
user
like
the
uid
of
the
container.
So
we
could
do
something
similar,
but
but
I
I
hate
doing
this,
like
wacom
mold
thing,
if
you're
going
to.
B
B
E
C
C
A
B
So
I
think
we're
trying
to
get
the
cap
merge
about
as
provisional,
because
because
I
think
it's
we
don't
have
much
time
to
get
emerged
because
as
alpha,
because,
basically
what
happens
is
I
think
team
actually
already
gave
look
good
to
me
a
while
back.
But
then,
after
that,
from
640
side
we
have
we
reviewed
it,
and
so
we
are
going
to
make
more
changes
than
what
was
there
previously.
So
we
need
some
time
to
actually
do
some
more
testing
make
sure
we
covered
everything.
B
Work
together
with
this,
so
we
need
to
test
the
yeah.
I
did
plc,
but
I
didn't
have
the
css
back
side
changes
at
that
time
and
also,
I
think
michelle
has
some
feedback
saying
that
the
reconstruct
reconstruction
should
be
done
for
the
node
stage
as
well,
so
that
we
also
need
to
add
yeah.
So
there
are
still
a
few
things
to
add
there,
but
we
want
to
yeah
make
some
progress.
So
hopefully
we
can
get
the
just
to
get
the
cap
merge
as
provision.
A
I
guess
design
is,
we
only
focus
on
getting
a
kept
merged
and
prototype
is
trying
to
get
some
sort
of
pre-alpha
level
code
written.
B
Oh
okay,
so
I
think
we
will
do
a
prototype,
so
prototype
is
like
one
step
more
than
design.
A
B
Yeah,
okay,
yeah.
I
think
we
want
to
do
that.
It's
just!
I
don't
think
we
can,
because
a
lot
of
those
changes
are
intrigued.
Well,
some
systems
back
yeah.
So
so
we
can't
really
merge
anything.
That's
what
I'm
saying,
because
we
don't
have
like
an
external
data
to
do
this.
B
No,
I
don't
think
this
is
the
change
will
be
either
entry
or
like
the
css
back
changes
got
it
well,
I
don't
think
we
need
a
new
ripple.
G
A
Okay,
so
then
we'll
target
prototype
for
this
release,
and
hopefully
the
cap
gets
merged
as
well.
B
E
Sorry
yeah,
no
I'm
here
I
I
this
kept
was,
did
not
merge
last
quarter,
so
I
don't
know
like
I
haven't
looked
at
it.
I
think
it
was
still
in
design
phase
and
a
lot
of
questions
being
raised,
but.
A
A
Next
up
is
address
issues.
Pvc
created
by
stateful
set
not
will
not
be
auto
removed,
so
we
were
targeting
alpha
and
it
missed.
The
code
freeze
sounds
like
we'll
keep
it
on
alpha
for
this
cycle.
I
Yep,
that's
right,
so
the
updates
to
the
kept
from
last
cycle
are
out
for
review
and
I'm
hopeful
that
I'll
get
the
implementation
done
on
time.
So
I
think
this
is
still
on
track
for
alpha
and
122.
A
Matt,
so
we'll
keep
that,
as
is-
and
the
next
item
is
cigaps
volume
expansions
for
stateful
sets.
This
was
targeted
as
design
last
quarter.
B
A
B
Yeah,
so
this
one
we're
actually
from
the
api
review
side,
we
are
getting
very
close.
Tim
says,
he's
very
close
to
being
happy
with
that:
oh
wow,
but
yeah,
but
yeah.
But
then
I
asked
just
signaled.
They
are
saying
they
think
we're
too
late.
They
already
got
like
20
20
caps.
Targeting
this
I
was
like
I
it
was
a
week
ago.
I
think
they
only
had
four
in
that
expression,
so
so
I'm
not
sure
if
they
can
take
it.
B
So
I
was
just
still
checking
with
them
and
checking
with
shenzhen
if
they
can't.
I
can
understand
that
because
it's
only
like
one
week,
so
what
we
can
do
is
to
try
to
get
the
cap
merged
early
for
the
next
release.
B
A
Cool,
thank
you
for
all
your
hard
work
on
that
next
item
is
kubernetes
utils
mount
split
into
new
repo,
so
there
was
some
leftover
work
here.
The
lid
was
in
staging
drivers
can
use
it
remaining.
Work
was
to
clean
up
existing
dependencies,
which
was
dependent
on
c
advisor.
We're
going
to
move
this
to
122..
I
don't
know
if
cerrini's
on
the
call
does
not
look
like
it.
A
Today,
it's
in
a
library
that
is
shared
with
a
bunch
of
other
components
and
sig
architecture
basically
said
move
it
into
its
own
repo
and
have
it
as
a
standalone
repo.
So
that
was
done,
and
so
it's
part
of
that
repo
is
part
of
staging,
and
so
everyone
can
consume
it.
We
just
need
to
update
all
the
depend,
all
the
consumers
to
start
using
the
new
dependency.
F
So
it's
already
in
the
staging
right.
Yes,
simple,
yeah.
H
E
F
A
Yeah,
that's
a
good
reminder.
So
if
you
have
a
csi
driver
that
uses
the
mount
utils,
please
make
sure
to
update
your
dependency.
All
the
new
changes
are
going
to
go
to
the
new
repo
effectively
and
yeah,
and
so
the
that's,
if
you
have
a
csi
driver,
please
update
and
then
the
remainder
work
here
is
to
update
the
internal
kubernetes
dependencies.
A
We
can
move
on
to
the
next
item,
prioritization
on
volume
capacity.
Anyone
want
to
give
an
update
on
this.
A
Looks
like
we
might
actually
be
done
with
alpha,
based
on
previous
update.
Oh
that.
A
A
Next
item
is
user
id
ownership
in
config
maps,
and
what
am
I
looking
at
here?
We
go
config
maps
and
secrets,
jawway.
A
C
Is
it
this?
Is
the
user.
A
C
I
mean
we
can
cross
out
35,
because
this
one
is
the
same
with
34.
yeah.
A
A
Sounds
good
okay,
so
I
think
that
wraps
up
planning
for
122.
were
there
any
other
items.
Anybody
on
the
call
wanted
to
add.
K
So
so
sad,
two
weeks
ago,
when
we
started
this
review,
we
didn't
have
sid
to
review
the
cozy
item.
Yeah.
I
A
A
Doing
well
so
I
think
we
were
putting
cozy
down
as
targeting
alpha
this
cycle.
Is
that
still
accurate.
L
Yeah,
so
we're
planning
to
go
alpha
this
cycle,
we
have
our
cap
ready.
We've
reached
the
consensus
on
the
design
and
architecture,
we're
waiting
for
the
api
reviewer
to
take
a
look
and
give
us
the
green
light.
Yeah.
That's
if
you
know,
if
you
can
reach
out
to
tim,
tim
hawkin
is
the
reviewer
and
I
believe
the
deadline
is
coming
up
really
soon.
If,
if
there
is
anything
we
can
do
to
reach
out
to
them
and
and
help
move
this
along
faster,
that
would
be
great.
A
Yep
that
sounds
good
I'll
see
if
I
can
poke
them
offline.
Thank
you.
Hopefully
we
can
get
cozy
move
to
alpha.
I
marked
it
as
a
p1
for
this
cycle
as
well
as
data
populators.
B
Mine,
do
you
want
to
update
on
the
voting
results
because
there's
some
update
right
still
there?
Oh,
I
think
he
dropped
okay.
B
It
into
this
yeah,
I
think,
the
okay,
so
I
think
the
beginning.
First
two
items:
let's
go
to
the
beginning,
yeah,
so
those
two
are
tracked.
There
is
another
item,
I'm
not
sure.
If
there
is
it's
tracked
inside
something
or
there's
another,
oh
maybe
it
is
number
two.
Is
that
the
voting
expansion?
We
add
that
to
pv.
So
basically
we
copy
the
allowing
expansion
from
study
class
to
pv,
so
hermann
asked
seek
release
whether
we
need
another
enhancement
issue
or
just
track
it
as
the
original
voting
expansion.
B
So
it
sounds
like
the
release.
Team
is
okay
for
us
to
track
that
just
as
the
original
issue,
but
they
say
the
original
cap
is
too
old.
We
mean
we
need
to
update
that
to
the
new
format.
I.
A
See
and
that's
gonna
be
under
number
two
or
number
three.
B
It
seems
like
it's
number
two
number
three.
Is
it
not
yeah
row
row?
Four,
that's
a
different
cap,
so
it's
probably
three
rows:
yeah,
okay,.
A
Got
it
so
csi
online
offline
volume,
expansion
fix
issues
and
update.
D
Let's,
let's
do
update
cap
and
fix
issues.
Reformatting
at
cap
is
not
a
small
amount
of
work.
A
A
Okay,
so
switching
back
to
the
agenda
dock
reminder
that
kept
freeze
is
coming
up
on
may
13th.
You
have
to
have
your
item
tracked
by
the
122
release
team,
as
well
as
having
your
cap
merged,
which
requires
api
review
prr
review.
So
please
get
those
started
as
soon
as
possible
if
you're
working
on
a
122
item.
A
I
A
Feedback,
okay,
anything
else.
Anybody
wants
to
talk
about
today.
A
All
right,
I
guess
last
comment
is,
I
know
coronavirus
is
getting
better
kind
of
in
some
areas,
but
it's
also
getting
a
lot
worse
in
a
lot
of
other
areas.
So
a
lot
of
folks
may
have
family
or
friends
that
are
affected,
and
you
know
as
a
as
a
sig
we're
we're
kind
of
a
big
extended
family,
and
so
I
wanted
to
you
know,
put
my
thoughts
out
there
and
make
sure
everybody's
well
and
if
everyone
ever
feels
like
the
work
for
the
sig,
is
you
know
a
distraction
from
their
family
life?