►
From YouTube: Manage:Import 14.5 planning
Description
This is the sync planning session for the 14.5 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17397
A
So
welcome
to
the
14-5
planning
for
import
on
october
14th,
so
we
do
have
an
issue
that
I've
created,
which
looks
very
much
like
the
last
months,
given
that
we're
still
under
the
headcount
reset.
A
So
I
expect
this
to
be
a
fairly
quick
meeting
because
we'll
be
pretty
much
continuing
everything
that
we've
been
working
on
for
the
last
month.
A
A
And
the
standard
team,
which
is
the
two
back
engineers
for
import
one
front,
end
one
sct
and
we
share
a
security
engineer.
B
Yeah
it's
two
weeks:
okay.
I
think
it
will
be
exactly
two
weeks.
I've
put
there.
Fourth,
but
I'm
not
sure
if
I
will
be
back
so
most
likely
fifth
of
november,
which
will
make
it
two
weeks
exactly.
A
Okay
and
then
you
also
dedicate
some
of
your
time
to
the
initial
equality
team
yeah.
We
have
like.
B
Quite
a
lot
of
initiatives
in
quality
right
now,
since
it's
like
there
there's
a
big
push
on
quality,
especially
for
like
gitlab.gitlab.com.
A
That's
probably
the
most
important
thing
is
to
just
keep
up
with
with
the
new
things
and
then
we'll
you
know
we'll
slowly
be
catching
up
with
some
of
the
old
stuff,
so
team
velocity
does
not
you
know
every
time.
I
take
a
snapshot
here.
A
It's
like
a
week
before
the
end
of
the
milestone,
so
really
the
true
velocity
for
14.4
will
be
captured
in
the
week,
and
I
believe
that
will
be
a
spike
up,
continuing
kind
of
the
trend
from
14
two
to
fourteen
three,
given
that
we've
added
a
lot
of
people
to
the
team,
so
I
think
next
month
we'll
actually
see
what
the
14
for
spike
actually
was.
A
The
proposed
objectives,
I
forgot
to
remove
the
working
progress
because
it
is
pretty
much
set
at
this
point,
the
back
end
and
kind
of
the
majority
of
the
team
or
everybody
on
the
team
joining
in
on
that
is
continuing
on
the
headcount
reset
and
we'll
open
up
each
one
of
these
areas
to
sort
of
take
a
look
at
what
might
be
upcoming
next
in
14.5.
A
The
front
end
has
a
kind
of
a
continuation
as
well,
which
is
there's
a
potential
carryover,
for,
I
think,
there's
a
carryover
from
14.4.
That
will
happen.
I
think
ilia
will
chime
in
async
sort
of
as
far
as
exactly
what
issues
he
might
pick
up
after
that.
So
this
is
more
of
a
continuation
from
14-4
and
then
on
quality.
We
talked
about
just
keeping
up
with,
what's
being
delivered
for
the
group
creation
for
the
gitlab
migration
and
I
think
the
project
issues.
A
Migration
is
the
one
open
one
open
issue
in
the
area
and
given
that
usually
getting
as
much
time
100,
I
think
just
like
completing
that,
and
maybe
wrapping
up
this
if
possible,
would
be
great
goals
for
14.5
for
quality.
Does
that
make
sense.
B
B
Sense,
I'm
not
exactly
sure
what
to
do
about
that
importer
issue.
We
did
identify
quite
a
lot
of
problems
and
I'm
not
sure
if
we
still
need
to
keep
that
around
or
just
refer
to
whatever
we
have
open
for
the
github
part
or
not.
A
Yeah,
I
think
I
think,
probably
like
if
the
test
has
been
delivered,
we
can
close
up
the
issue
and
just
open
up
any
bugs
against
github
importer
that
we're
like
specific
problems
that
we're
seeing
with
the
test
as
separate
issues.
So
the
big
issue
can
be
closed
and
then
we'll
track.
You
know
things
we
need
to
fix
and
things
we
decide.
We
want
to
fix
separately
from
from
the
delivery
of
the
big
test.
B
A
Okay,
so
we
probably
should
have
an
epic
such
as
this
one.
I
think
we
actually
might
already
have
one
in
the
github
importer
area,
where
we
kind
of
keep
all
the
tests
all
the
test
issues
and
we
need
to
remember
to
park
an
issue
to
create
test
coverage
for
every
feature
we
add
in
github
import.
That's
a
very
good
point
class
you're
making,
because
I
don't
think
we
talked
about
this
or
we
actually
have
any
kind
of
process
in
our
heads
for
this.
But
that
should
be
the
case.
A
We
will
I'll
find
that
I'll
find
it
epic,
and
then
we
just
need
to
make
sure
that
whenever
we
create
a
feature,
we
also
create
an
issue
for
automating
tests.
For
that
particular
feature.
A
So
I
wonder
if
we
have
put
an
issue
there
for
the
github
importer
or
an
epic
in
there-
and
I
don't
see
one
here
so
we'll
create
one
for
the
tests
and
then
we
need
to
all
just
make
sure
that
we
don't
forget
to
put
an
issue
there
when
we
add
a
feature
that
should
be
automatically
tested
so
I'll.
A
Take
that
after
this
I'll
make
sure
that
the
epics
created
and
the
one
you
should
that
you
mentioned
cassio,
is
in
there,
but
then
also
kind
of
think
back
about
any
other
issues.
We've
closed
recently.
That
might
need
to
be
added.
A
A
We
are
about
a
month
and
a
week
or
so
into
the
headcount
reset,
which
means
we
still
have
more.
You
know
maybe
40
in
I
guess
so
we
still
have
just
as
much
time.
It's
not
even
more
to
go
so
not
even
halfway
through
the
time
kind
of
started.
A
You
know
it's
kind
of
taking
us
how
far
we've
gotten
this
seems
like
we
talked
about
this
on
monday,
and
I
know
if
there's
any
comments
as
far
as
sort
of
what
we're
focusing
on
focus
mode
doesn't
want
to
work
what
we're
focusing
on,
and
you
know
how
we're
using
kanban
I
have.
I
really
don't
have
anything
to
add
to
what
we
talked
about
on
monday,
but
if
the
team
has,
if
you
guys
have
something
to
add,
please
do.
A
So
we'll
just
continue
on,
there
is
actually
one
thing
that
I
just
did
remember
and
that
is
I
have
labeled
some
issues
as
a
stretch,
because
this
is
the
one
area
where
we're
definitely
not
going
to
get
to
the
bottom
of
the
of
the
backlog.
By
the
time
we
get
to
the
end
of
the
time,
so
the
headcount
reset
will
expire.
A
We
will
not
get
to
all
of
these,
and
the
way
where
I
drew
the
line
was
the
parity
with
the
existing
file
based
importers,
which
is
kind
of
a
similar
thing
that
we
did
for
the
group
import.
Our
first
milestone.
Our
first
like
train
station,
was
the
parity
with
the
previous
solutions
to
start
kind
of
phasing
out
the
previous
solution.
A
So
any
kind
of
feature
like
mr
approvers,
which
don't
exist
in
the
current
files
file
based
system.
I
have
marked
a
stretch
which
means
that
you
know
we're
going
to
deliver
that
last.
That
gives
us
a
different
cut
line
in
the
backlog
in
order
to
try
to
shoot
for
that.
So
I
will
triage
these
out
because
you
know
I
really
don't
want
us
to
even
see
these
here.
A
So
I
will
probably
take
these
out
in
the
next
couple
days
couple
weeks
whenever,
but
they
are
at
the
bottom
of
the
backlog
right
now
and
you
know
hopefully
we'll
have
a
more
focused
backlog,
given
that
you
know
there's
kind
of
a
first
first
station
to
to
arrive
at.
Does
that
make
sense?
To
do
I
mean
somebody
have
any
other
ideas
on
like
how
else
we
could
cut
the
scope.
A
I
felt
like
that
was
a
great
stopping
point
as
when
we
reached
the
parity
with
the
current
exporters
and
also
things
that
have
not
been
done
yet
are
always
going
to
be
harder
to
do
things
that
already
are
being
done.
The
current
importer
in
the
file
based
importer
and
exporter
are
going
to
be
easier
because
we're
actually
reusing
that
code,
so
it
feels
like
we
should
be
able
to
move
faster
toward
that
line
by
kind
of
pushing
these
below
the
below
the
cut
line.
A
I
know
everybody
everybody's
watching
the
other
stream,
so
you
can
just
put
me
on
mute.
A
Yeah,
all
right
so
cassio
and
doug.
A
So
this
one
has
started
moving.
I
know
it
had
a
kind
of
slow
start
because
it
was
dug
on
by
himself
in
the
beginning,
but
it
definitely
started
creating
some
velocity.
It
does
seem
like
we
have
nothing
in
refinement
and
ready
for
depth.
That
may
be
something
to
think
about.
C
A
Yeah,
it's
good
point
thanks
for
bringing
that
up,
because
there's
definitely
customer
escalations.
They
happen,
and
it
is
kind
of
on
this
group
to
keep
the
other
two
groups
focused
in
their
area,
so
yeah
that
that
may
not
be
readily
visible
or
easily
appreciated.
So
thanks
for
bringing
it
out
so
anyway.
If,
if
there's
any
questions
around
the
priority,
I
mean
these
are
all
sort
of
in
the
order
of
the
priority
originally
discussed.
A
But
if
there's
any
questions
around,
you
know
why
this
is
not
higher
or
why
why
something
is
as
high
as
it
is.
Please,
let
me
know.
Otherwise
you
can
probably
just
keep
getting
things
from
the
top
into
refinement,
ready
for
dev
and
I'd
recommend,
probably
getting
at
least
one
or
two
issues
or
one
each
in
refinement
so
that
there
is
work
ready
for
when
these
go
into
review.
B
C
Then
do
the
red
for
dev
and
it's
just
dog,
and
I
I
think
we
won't
do
this-
two
steps.
We're
probably
gonna,
just
get
the
issue
we
find
and
already
work
on
them.
So
that's
probably
why
there
is
nothing
on
refinement
already
for
that
now.
Okay,
probably
when
I
put
my
the
one
that
I'm
developing
right
now
on
review
I'll
get
the
other
one
and
put
in
development
already.
I.
A
Say,
oh
wow
makes
sense,
and
the
next
couple
are
really
important,
and
this
is
going
to
be
great
for
our
customers
and
should
help
with
the
escalations,
because
these
are
issues
that
were
identified
by
customers
in
a
recent
huge
escalation.
So
the
threading,
the
diff
nodes,
was
a
huge
escalation
and
it
is
bound
to
happen
again
unless
we
take
care
of
this
issue,
and
this
this
also,
this
feature
came
from
an
escalation,
but
now
it
seems
like
we
have
a
bug
there.
A
It's
not
marked,
as
a
bug
probably
should
be
but
yeah.
This
is
a
feature
that
we
thought
was
working,
but
it
seems
like
it
may
not
always
work.
So
these
are
great.
These
are
going
to
be
great
help
with
escalations.
A
So
yeah
we
discussed
this
on
monday
and
it
seems
like
the
issues
that
are
still
not
started
are
either
a
issue.
That's
blocked,
so
the
one
that's
kind
of
apparent
to
many
other
issues
that
showed
up
this
one:
that's
waiting
for
heat
to
just
update
documentation,
so
that
should
just
be
completed
and
then
a
feature
flag
that
we
want
to
flip
in
14-5.
A
So
it
seems
like
14.5
potentially
is
it
could
be
the
last
milestone
we
planned
for
this
and
then
the
next
planning
session.
There
may
be
nothing
for
this
team
they
can,
they
can
join.
We
can
talk
about
weather
and
things,
but
they
may
be
able
to
return
back
to
their
regular
programming
unless
they
decide
to
apply
for
the
backend
engineer
job
that
we're
going
to
open
at
like
an
import.
A
A
Any
more
thoughts
around
this
like
did.
I
represent
the
state
accurately.
A
All
right
cool,
so
I
know
we
all
have
a
more
important
thing
to
get
back
to.
So,
let's
see,
if
there's
anything
else
that
we
should
discuss,
feels
like
a
pretty
straightforward
milestone,
given
that
we're
like
midway
through
the
headcount
reset.