►
From YouTube: Verify:Testing 14.5 Milestone Refinement Kickoff
Description
Walkthrough of the team's 14.5 planning issue. https://gitlab.com/gitlab-org/ci-cd/testing-group/-/issues/70
The big focus of deliverables is on the theme of GitLab-hosted First: https://about.gitlab.com/direction/#gitlab-hosted-first
A
Hey
team
wanted
to
walk
through
our
14-byte
planning
issue
to
kick
off,
refinement
on
that
milestone,
so
starting
with
our
milestone
v.
So
we
try
to
align
all
of
our
milestones
with
one
of
our
investment
themes:
our
fiscal
year,
22
investment
themes
which
there's
a
link
here
to
those
just
a
reminder.
A
Those
are
application,
security,
testing
leadership,
adoption
through
usability
and
get
my
posted
first,
so
in
the
14-5
milestone
or
release
our
deliverables
are
going
to
be
focused
around
the
investment
in
gitlab
hosted
first
to
better
its
support
administrators
people
who
are
managing
groups
within
gitlab.
We're
going
to
be
working
on
several
of
the
build
artifact
category
related
issues
and
you
can
open
those
up
and
look
at
those.
A
We
have
several
things
here
included
many
of
those
are
also
performance
or
bugs
feature
maintenance
items
that
we'll
also
be
looking
at
or
listed
later
in
the
performance
issue.
The
big
one
is
really
the
api
to
bulk
to
the
artifacts
that
it
probably
requires
some
research
in
this
milestone
in
14-4.
I
just
make
sure
we
understand
all
of
the
things
that
can
happen
there,
so
we
should
take
a
look
into
that
start.
A
A
refinement
sooner
than
later,
even
though
it
is
marked
as
ready
for
development
want
to
make
sure
our
team
is
clear
on
what
we're
doing
there.
I've
called
that
out
as
one
of
our
top
priority
developers.
The
problem
is
that
today
you
can
delete
artifacts
job
artifacts
through
the
api
one
job
at
a
time.
So
if
you
have
hundreds
of
jobs
within
a
pipeline,
it
can
take
you
way
way
too
long
to
actually
make
some
space.
If
you
really
need
it
very
quickly.
So
this
endpoint
is
a
new
one.
A
The
other
big
deliverable
is
around
performance
and
it's
around
the
curvature
of
parser
the
sax
parser.
Not
only
is
this
performance
related,
but
is
performance
related
in
relation
to
our
current
application
limit.
We
limit
users
to
10
megabytes
on
that
file
so
that
when
they
upload
it
or
when
they
have
a
larger
coverage
report
coverage
turtle
report,
we
can
support
that.
We
have
several
customers
who
are
looking
at
being
able
to
support
that
use
case.
A
You
don't
have
anything
labeled,
back-end
or
front-end.
Currently,
so
there's
nothing
specifically
there.
That
does
need
refinement,
but
we
do
have
a
lot
of
things
that
still
need
some
refinement
on
our
planning
breakdown,
as
you
can
see
here,
and
that
is
just
the
build
artifact
ones.
If
we
get
rid
of
that
label
as
well,
it's
even
more
items.
We
have
10
issues
still
sitting
in
planning
breakdown,
even
though
we
just
did
kick
off
the
milestone,
no
design
issues
being
implemented.
A
No
problem
validation,
no
solution,
validation
happening
a
couple
of
bugs
these
are
related
to
performance
as
well,
not
being
able
to,
or
rather
build
artifacts
as
well.
Not
performance
can't
migrate
job
artifacts
to
object
storage
that
needs
an
investigation
in
the
milestone
and
then
keeping
latest
artifacts
keeps
artifacts
for
filled
pipelines
that
goes
back
to
our
gitlab,
hosted
first
and
having
a
more
build
artifacts
that
you
could
possibly
need,
causing
you
to
run
out
of
storage
space,
and
so
most
of
our
technical
debt
issues
are
also
deliverables.
A
You
can
see
those
up
above
and
we
haven't
established
okrs
yet
for
the
quarter
so
once
we
do
we'll
get
alignment
into
there.
So
this
is
open
and
ready
for
the
team.
You
can
go
ahead
and
update
the
holiday
section.
Make
sure
your
calendar
is
up
to
date
for
capacity
planning
purposes,
start
asking
questions
poking
around
seeing
how
this
aligns
with
what
we've
done
in
the
past
stress
test,
how
it's
aligning
with
those
investment
themes.
Ask
me
any
questions
and
looking
forward
to
them
and
getting
this
all
ready
to
go
thanks.