►
From YouTube: Threat Insights - 16.4 planning issue review
Description
Monthly group discussion to review the planning issue for the upcoming milestone: https://gitlab.com/gitlab-org/gitlab/-/issues/420162.
B
This
has
been
a
complicated
meeting
so
far,
but
we
are
just
getting
started
all
right.
This
is
the
16-4
planning
issue,
so
we
were
we're
almost
done
with
16-3
and
exciting
beta
will
ship
we're
gonna,
be
doing
working
on
the
general
availability
for
explain
this
vulnerability
for
60
and
4
we're
gonna,
actually
try
and
Tackle
all
of
these
issues
that
are
remaining
so
that
way
we
can
have
a
milestone
to
really
fine-tune
and
test
the
prompt
before
we
go
to
GA,
and
then
this
is
actually
not
accurate.
B
A
A
Has
been
his,
we
kind
of
we
feel
like
we
made
a
a
little
bit
of
a
mistake
in
focusing
on
that,
while
we
still
had
tasks
to
do
on
the
on
the
group
permissions
and
and
as
a
result,
the
group
dependency
sorry
not
good
permission
group
dependency
as
well.
The
group,
the
dependency
is
kind
of
unlikely
to
make
16-3,
but
anyway,.
A
For
that
one
there's
a
lot
of
overlap
with
the
with
the
post,
MVC
or
the
for
group
dependency,
which
I
see
is
not
in
this
list.
So
another
thing
that
we,
we
have
to
add
they've,
been
working
with
the
zami
has
been
working
with
Mo
and
Dave,
who
are
the
dris
for
the
for
the
for
the
follow-up,
the
yeah
it's
taking
shape?
Okay,
we
have
some
issues
in
there
to
work.
B
A
B
A
B
B
A
A
Role,
it's
going
to
come
down
right
to
to
Dwight
on
this
one,
because
the
merge
request
has
been
there
for
a
while
and
there's
been
a
a
lot
of
back
and
forth,
and
in
the
process
of
doing
that,
they've
stumbled
stumbled
upon
a
bug.
There
was
latenting
there,
so
the
good
news
is
they
got
to
fix
this
part
of
it
anyway.
A
B
A
B
The
building
blocks,
and
then
in
doing
so
they
also
did
some
of
the
permissions
for
us
and
they
also
enabled
it
so
that
way.
The
permissions
are
available
at
the
group
level,
not
just
the
project
level,
but
it
will
Encompass
these.
We
cut.
We
cut
this
one,
but
then
we'll
in
these
four
different
permissions
I
think
it's
important
to
note
here
that
we
are
going
to
we're
going
to
have
a
breaking
change
in
170,
which
will
remove.
B
B
Definitely
that
brings
us
to
number
five,
so
additional
activity
filters
on
the
vulnerability
report
and
vulnerability
report
grouping
are
things
that
are
just
on
our
roadmap
that
we're
chipping
away
at
I.
Think
the
initial
MVC
will
be
grouping
by
severity
and
Status.
It
seems
like
a
lot
of
that
is
front-end
work.
Only
so,
hopefully
Bala
can
do
some
things
on
the
back
end
to
get
us
ready
for
the
next
couple
iterations
and
then
this
is.
A
No,
no,
not
that
one!
It's
in
the
it's
in
the
maintenance
of
16
3,
so
just
copy
that
across
there's
also
continuing
the
replacement
of
rest
with
the
graphql,
and
now
that's
on
the
on
the
pipeline
report.
So
that'll
that'll
roll
over
as
well.
So
it's
mostly
role
model
for
six
and
three.
It's
I,
don't
think,
there's
anything
new
that
that
is
worth
going
to
the
details
that
one
there
that
is
seen
there
that
may
go
in
there.
I
need
to
check
with
me.
A
B
A
A
A
It
kind
of
makes
sense
to
me,
but
I,
think
I
think
it
started
in
engineering,
because
there
was
a
discrepancy
on
between
what
the
what
the
menu
says
and
what
the
what
the
report
says-
and
you
know
a
whole
confusion
between
scanner
and
analyzer,
and
this
epic
is,
is
looking
to
resolve
that
I
I
did
a
fair
bit
of
working
there,
coordinating
where
we
want
to
be
with
it.
I'm
just
surprised
that
at
some
point
to
change
the
future,
but.