►
From YouTube: 2021-03-09 Rook Community Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
everyone
to
the
rook
community
meeting
for
march
9th
to
2021
we'll
get
this
kicked
off,
starting
with
the
milestone,
checkup,
so
1.4,
and
we're
really
not
planning
on
any
more
releases
there
patch
releases
for
1.4
for
1.5
we're
planning
on
a
release,
let's
see
next
later
next
week.
I
think
that'll
be
about
three
weeks
since
the
last
one
we're
just
starting
to
slow
down
there.
While
we
gear
up
for
a
ramp
up
for
1.6
yeah,
no
blocking
issues
really
that
that
I
can
think
of
for
1.5.
A
Okay,
as
far
as
1.6
goes,
we
are
coming
up
on
that
in
a
few
weeks
with
pacific
coming
out
by
the
end
of
the
month,
maybe
even
sooner,
I'm
not
sure
the
latest
proposal
on
that,
but
for
rook.
My
proposal
is
that
we
have
feature
freeze
on
march
30th
three
weeks
from
today,
and
that
would
give
us
about
a
week
to
get
ready
for
the
release
create
the
blog
around
april
7th.
B
B
So
hopefully
we
will
have
enough
time
yeah
it's
supposed
to
be
out
this
month,
so
yeah
exactly
it's
late.
A
B
C
C
A
C
B
A
A
A
Yep,
that's
just
a
quick
note
and
feel
free
to
stop
me.
If
there's
any
questions
moving
on
github
actions
were
officially
increased.
I
think
it
was
just
right
about
the
time
of
our
last
meeting,
so
not
much
else
to
report
there
other
than
yep
we're
working
on
getting
more
and
more
of
our
testing
through
the
github
actions.
A
Excited
about
that
and
another
note
on
testing.
The
next
item
is,
you
know
big
for
the
development
team.
So
until
now,
we've
had
our
crds
and
manifests
copied
into
the
test
code
for
purposes
of
upgrade
tests
and
yeah.
Just
all
the
integration
tests
had
that
copied
and
we've
been
talking
for
a
while
about
how
to
avoid
that
and
just
load
them
from
the
examples
folder.
So
we're
testing
the
same
thing
that
we're
telling
people
to
use.
A
Well.
Yesterday,
I
realized
there's
a
simple
way
to
do
that
so
got
the
first
step
of
that
merged,
where
the
crds
are
just
picked
up
from
from
the
examples
folder
and
for
the
upgrade
test.
It
actually
pulls
them
from
github
the
as
the
base
release
for
what
we're
testing
and
then
we
upgrade
to
master
for
the
upgrade
test
yeah.
So.
B
Yeah,
no,
no
yeah.
I
think
it's.
I
think
it's
also
really
good,
but
I
just
hope
that
at
the
same
time,
no
one
is
running
ours.
This
suite
on
environment
that
has
no
internet
access,
because
we
are
fetching
the
crvs
from
an
older
branch
from
github
straight
so
yeah,
that's
right.
Hopefully,.
B
Yeah
or
yeah
we
could
have
used
git,
I
guess
simply
to
to
fetch
a
file
from
a
particular
branch,
but
I
think
for
now
it's
good
enough.
A
B
To
do
this,
for
other
other
artifacts.
A
A
The
crs
right,
at
least
the
r
back,
but
I'll
do
our
back
first
and
then
see
if
it
makes
probably
doesn't
make
sense
for
the
crs,
because
we
customize
them
for
the
tests
more.
B
This
will
save
us
the
burden
of
manually
writing
animals
too,
and
it
will
also
benefit
from
other
projects
consuming
group.
I
suppose
that's
okay,.
A
Right
that'll
be
great,
and
do
you
think
there's
any
or
is
it
looking
good
to
have
it
done
in
the
1.6
time
frame?
I
hope
right
yeah.
I
know
you're
still
working
through
it,
but.
B
Yeah,
that's
now.
I
think
I
should
be
able
to
have
it
for
four
one.
Six
ci
is
already
running
on
it,
and
the
only
thing
I
need
to
to
take
care
of
is
the
upgrade
and
change
a
few
types
that
are
not
allowed
like
interfaces
types.
A
B
B
B
I
think
the
goal
is
really
to
once
you
land
on
the
issues
page
to
see.
Okay,
is
there
something
you
should
be
looking
into,
or
it's
just
like
almost
directions,
and
I
think
the
first
one
was
is
really
about
like.
If
you
have
a
question,
then
you
use.
Oh
sorry,
I
think
yeah.
I
need
to
admit
people.
B
If
you
have
issues
you
have
questions.
So
sorry
then
use
the
discussions
that
were
actually
recently
introduced
on
on
github.
They
it's
it's
almost
like
an
faq
and
or
like
a
support
messaging
or
you
ask
question
and
then
somebody
replies.
Then
you
can
select
the
best
answer
for
that
question.
So
it's
good
to
actually
have
a
question
and
get
a
quick
response.
B
So
that
was
the
first
issue
we
pointed
out.
The
second
one
is
just
this
volume
lvm
batch
problem
and
the
most
recent
one
was
the
was
the
helm
so
yeah.
I
guess
it's
probably
a
good
habit.
B
Hopefully,
it
will
bring
more
visibility
to
the
issues
and
and
for
end
users,
because
I
think
every
every
project
has
that
issue
is
like
how.
How
can
we
trim
down
the
number
of
issues?
How
can
we
improve
the
dog?
How
can
we
improve
processes
so
that
we
don't
get
issues
that
get
opened
and
then
get
closed
right
away,
because
they're
actually
just
questions?
What
can
we
do
to
improve
the
overall
experience
so
that
we
can
so
that
we
don't
get
issues
that
are
not
really
issues
where
what
the
focus
on
issues
should
really
be?
B
B
A
Yeah
and
I
think
we'd
like
so
since
we
only
get
three
issues
to
pin
at
a
time.
I
think
if
we,
those
should
always
be
the
three
highest
or
most
visible
features
or
bugs
that
we
want
people
to
be
aware
of.
So
if
we
want
to
update
those
or
if
there's
suggestions,
if
we
could
just
put
it
in
slack,
probably
the
maintainers
channel
to
say,
hey,
I'm
changing
this,
we've
got
this
bigger
issue,
or
maybe
even
the
general
channel
to
make
other
people
aware
of
it.
A
So
the
next
topic
really
wanted
to
talk
with
talk
with
jared
about,
but
he
wasn't
able
to
make
it
today
or
stay
in
the
meeting
as
far
as
pruning
inactive
members
from
from
our
github
groups,
we've
got
68
members
of
the
contributors
list,
for
example,
and
20
of
them
really
are
super
inactive,
so
and
so
I'll
follow
up
with
jared
on
clean
that
up.
A
A
B
Yeah,
I
guess
I
mean
if
it
builds
it's
already
a
good
step
forward,
so
that
all
of
our
extra
dependencies
can
also
build
on
116.
It
seems.
C
Yep,
so
no
offense
travis,
but
jared
asks
from
the
previous
meeting
that
an
update
on
the
pacific
release
so
who
better
to
explain
it
than
sage
himself,
so
conveniently
had
an
update
that
sage
gave
live
and
here's
the
recording
it
is
going
on
the
stuff
youtube
channel,
I'm
just
running
behind
on
various
things,
but
you
can
go
ahead
and
get
a
preview
of
it
right
here
should
allow
you
to
do
a
video
playback
now
that
it's
rendered
so
that's
it.
A
A
B
No
because
because
no,
I
think
you
said
the
rendering
was
complete
right,
it
is
completed
now.