►
From YouTube: Manage:Import 14.0 planning
Description
This is the sync planning session for the 14.0 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17328
Notable epics mentioned:
Complete Epic migration - https://gitlab.com/groups/gitlab-org/-/epics/5189
A
We
have
an
attendance,
fewer
people
than
normal.
Some
people
couldn't
make
it
so
we'll
just
probably
be
a
short
call
or
maybe
we'll
just
discuss
things
and
I'll
go
on
we'll
see.
George
has
talked
to
oneself.
A
Let's
just
go
ahead
and
start
talking
about
what
14.0
will
look
like
for
us.
I
will
share
my
screen
to
show
the
planning
issue
for
illustration.
A
So
the
theme
has
not
changed
since
last
time
we
talked
we,
we
do
have
an
sct
which
is
kind
of
really
cool
and
he's
added
his
his
things
to
the
planning
and
we're
getting
some
test
coverage.
So
that's
really
a
welcome
change,
so
glad
would
we're
there
now.
As
far
as
the
capacity
goes,
I
know
about
casio's
10
days
of
pto
and
I
will
also
be
taking
you
know
about
two
weeks
worth
of
pto
over
the
next
month.
It
just
won't
be
a
consecutive
two
weeks.
A
It'll
be
you
know
two
days
here
and
three
days
there
type
thing
I'll,
let
you
know
I
have
the
time
and
most
of
the
time
I'll
be
reachable,
but
I'll
be
traveling
and
I'll
be
just
kind
of
on
and
off
anyone
else.
A
So
maybe
we
can
spend
a
little
bit
of
time
talking
about
kind
of
what
happened
in
1312,
because
it
you
know
it
didn't,
go
as
planned.
We
plan
to
attack
a
few
things
and
then
other
things
have
happened,
so
we
could
talk
about
like
what
happened?
Will
those
things
continue
to
happen?
Should
we
plan
differently
this
time
around?
Because
of
that,
or
should
we
plan
exactly
the
same?
Just
thinking
that
it
will,
it
will
be
okay,.
B
Well,
I
can
start,
I
guess.
Well,
since
1311
we
we
had
the
thing
where
we
did.
We
had
to
implement
nd
json
yeah
import
for
the
group
migration,
and
that
has
been
my
focus
for
for
for
the
milestone.
B
However,
that
means
not
a
significant
amount
of
changes,
like
the
export
side
took
a
few
weeks
now.
The
import
side
is
a
multi-mr
effort
as
well,
which
is
taking
a
week
already.
B
You
know
the
progress
has
been
made,
but
a
milestone
is
actually
not
that
it's
not
that
much
of
time
when
you
take
into
consideration
the
development
plus
the
review
cycles
and
all
that
yeah,
that's
my
main
priority.
A
So
how
much
into
140
do
you
expect
this
particular
thread
to
go.
B
It
will
definitely
go
into
14-0
because
there
is
a
number
of
merge
requests
that
I
was
working
on
for
ng,
json,
import
and
export
for
export
or
two
merge
requests
for
import.
There
have
been
three
merge
requests
already,
plus,
probably
two
more.
D
Yeah,
maybe,
although
that
the
work
was
very
well
broken
in
a
lot
of
different,
merge
requests,
we
didn't
broke
the
epic
and
very
different
issues,
and
this
is
maybe
being
a
problem
to
given
the
visibility
of
the
world
of
the
progress.
So
I
can
take
some
time
early
next
week
to
try
to
break
all
the
marriage
requests
that
george
already
did
and
create
the
issues,
and
I
think
this
will
bring
more
visibility
about
the
progress
that
what
was
done
and
what
to
still
have
to
do
to
complete
this.
This
effort
so.
A
What
do
they
roll
up
to
now
like
is
there?
Is
there
just
one
issue
that
those
roll
up.
D
A
B
D
If
you
expand
the
technical
improvements
yep,
there
is
yeah
so
yeah.
There
is
quite
a
few
issues
in
there,
but
some
of
them
are
well
actually
it's
kind
of
in
that
one
that's
weight.
S5
am.
A
A
If
we
need
to
or
not
to
break
this
onto
multiple
issues,
if
it
makes
sense
fine,
but
just
for
visibility,
I
think,
like
I
can
look
at
this
issue
and
see
where
things
are.
B
D
Yeah,
my
it's
just
an
opinion.
I
just
think
that
having
these
smaller
issues
helps
you
with
the
sense
of
progress
but
yeah,
we
can
do
whatever
it's
easier
for
everyone.
Yeah.
A
Yeah,
I
can
see
both
I
mean
I
see,
I
see
that
argument
as
well,
so
I'll
leave
it
up
to
you
whether
you'd
like
to
put
this
into
multiple
issues
or,
if
there's
some
kind
of
a
conclusion
to
where
we
are
now.
But
there
are
leftover
things,
maybe
spin
off
an
issue
to
follow
up
so
that
potentially
this
issue
can
be
closed
in
1312
or
14-0,
and
then
there
could
be
follow-up
issues
by
the
way.
What
should
be
the
milestone
for
this?
This
is
not
going
to
be
done
in
1312
right.
B
Well,
the
certain
12
was
the
goal.
Yeah
I
mean
you
can
put
the
certain
12
for
now.
Maybe
it
will
end
up
in
certain
valve
who
knows.
A
Yeah
I've
seen
I've
seen
actually
several
issues
that
made
it
all
the
way
to
production
that
had
like
a
next
one
to
three
milestones
on.
So
let's
just
be
diligent
about
when
things
go
into
development.
D
A
That
point
assigning
the
current
milestones.
Just
so
that
you
know
we
have
some
hygiene
and
then
our
metrics
actually
also
work
yeah
cool.
A
B
So
I
think
once
hopefully
I
don't
know
what's
going
to
come
next,
it
feels
like
whatever
we
plan
things
change
all
the
time,
but
hopefully,
once
I
finish,
the
epics
migration,
the
other
relations
are
going
to
be
easier
to
implement.
A
We
have
this
listed
as
a
maybe
shouldn't
be
under
technical
debt,
but
it's
under
I
don't
have
a
better
label.
I
could
move
it
up
to
gitlab
migration
potential.
B
B
C
Okay,
on
front-end
side,
actually
things
went
pretty
well.
I
was
able
to
fulfill
almost
everything
we've
had
planned
for
the
1312
and
this
one's
like.
C
I
was
so
basically
for
next
milestone.
What
I
would
like
propose
is
the
things
which,
like
basically,
we
have
on
the
refi
ready
for
developments.
They
were
a
free
issues,
or
so,
I
believe
on
board,
and
I
recently
added
one
which
is
a
bug,
but
it
is
pretty
important
and
I
would
like
to
get
it
ready
pretty
soon,
because
it
was
revealed
that
it
is
pretty
annoying
yeah,
and
this
is
one
very
weird
while
why
it
is
not
displaying
for
you
one
second,
I
I've
bet.
C
Yeah,
sorry,
I
believe
I
one
second,
I
might
be
missing
the
front
end
part.
So
basically
it
is
an
annoying
issue
that
our
validation
is
a
bit
wrong.
C
I
mean
when
I'm
checking
that,
for
if
group
name
is
available,
I
forgot
that
we
need
to
check
not
just
again
the
existing
group
name,
but
also
against
existing
project
name,
because
obviously,
group
and
project
names
can't
clutch
so
right
now,
sometimes
it
says
like
hey,
you
can
run
an
import
on
this
target,
but
actually
this
target
name
was
occupied
by
a
project
and
after
that
the
import
starts,
and
since
we
do
not
have
a
proper
reporting
it
is,
it
was
not
important.
C
C
Well,
basically,
everything
we
have
in
the
ready
for
development
is
the
list
of
what
I'm
scheduling
for
next
milestone,
because
all
other
issues
are
either
completed
or
are
currently
in
review.
A
Yeah,
I
agree
that
this
this
particular
thing
should
be
there,
because
we
just
recently
introduced
this
validation,
and
would
you
even
think
of
the
scenario
where
we
have
a
project
that
clashes.
C
Cool
yeah
as
a
side
note,
but
I
I
will
probably
raise
it
on
the
weekly
too,
but
just
to
letting
you
know
it's
feeling
a
bit
lonely
on
the
left
sections
for
the
front
end,
and
we
could.
We
should
probably
discuss
on
how
we
should
address
this
for
now,
because
if
nothing
changes
there
will
be
a
certain
lack
of
work.
I
mean
at
least.
A
You
know
ruby
for
beginners.
C
Yeah,
but
actually
so
just
letting
you
know,
and
we
should
probably
address
it
in
some
way
right
now.
I
do
not
have
a
good
solution.
I
will
go
through
the
design
section
and
to
make
sure
if
and
ping
you
if
we
could
proceed
and
move
it
somewhere
forward,
because
there
were
some
discussions
here
and
there
and
while
amanda
is
not
here,
which
we
will
take
a
look.
If
it
is
it
good
enough
to
proceed
even
if
it
is
not
perfect,
but
yes
and.
A
C
No
sorry,
sorry
for
jumping
it,
but
this
is
exactly
the
issue
when
I
requested
the
designer's
help.
It
is
like.
I
believe
that
only
on
this
list,
because
I
do
not
know
how
to
present
it
to
user
in
a
clean
and
sane
way
that
hey
this
is
the
previous
import
target
so
yeah,
but
for
other
issues
your
concern
is
pretty
valid.
Your
opinion
is
pretty
valid.
A
In
that
case,
I
can
actually
get
somebody
involved
like
I
can
probably
get
danielle
mora
or
someone
else.
Who's
been
involved
with
us
before
to
hand
us
to
telling
us
a
hand.
A
Yeah,
so
we'll
we'll
get
someone
else
to
to
help
out
with
that
and
get
it
unstuck.
That
said
in
the
planning
breakdown,
the
bottom
three
issues
have
already
passed,
design
and
they're
saying
here
they
were
just
kind
of
being
staged
for
refinement,
because
refinement
was
kind
of
full
and
didn't
want
to
load
that
up.
So
you
know
the
history
for
the
group
imports
the
history
for
all
the
projects
and
the
table.
Header
sorting,
yeah
for.
C
Yeah
for
table
header
headers.
I
believe
it
is
pure
front-end,
but
for
others
I
believe
it
will
involve
some
backhand
discussion.
A
Okay,
so
would
you
be
able
to
help
me?
Do
the
breakdown
then
and
and
kind
of
help
me
tease
out
front-end
versus
back-end
stories,
because
the
reason
why
they're
in
breakdown
is
because
I
believe
it
will
turn
into
more
than
one
issue?
There
will
be
a
front-end
issue
and
that
can
issue
maybe
multiple
front
and
multiple
backhand
issues.
So
if
you
could
help
me
sort
of
understand,
you
know
like
what
issues
I
may
need,
I
will
create
those
and
we
will
move
those
into
refinement
separately.
C
Okay!
Thank
you
I'll.
Take
a
note,
but
basically
this
is
on
my
side,
everything
nothing
to
add
more.
D
So
it's
hardy,
won't
you
start.
I've
been
busy
with
the
import
from
remote
object,
storage
thing,
although
the
code
change
wasn't
that
big
testing
it,
I
found
a
bug
and
I
was
just
testing
the
fix
of
the
bug
and
besides
that
professional
services.
D
Maybe
the
metrics
of
the
deliveries
there
are
low
because
I
probably
missed
some
labels
on
the
professional
services
issues
that
I
created
or
they
created
for
us.
So
I
can
try
to
help.
Try
aging
that
better
to
improve
the
visibility
of
what
was
done,
but.
A
A
Yeah
sure,
and
on
the
proposed
objectives
for
140
really,
I
have
not
changed
anything
because
I
feel
like
all
these
all
the
objectives
still
stand.
We
haven't
really
completed
the
things
we
talked
about
so
continuing
down
the
path
of
just
getting
to
that
parity
with
group
export
import
so
that
we
could,
you
know
at
least
turn
off
the
group
exports
and
imports
is
the
primary
goal.
A
There
is
still
that
one
issue
that
was
in
that
was
in
p1
that
I
know
cassie
said
you're
going
to
try
to
complete
in
1312,
but
if
it
doesn't
get
completed
in
1312
this
one
here,
the
instrumentation,
then
it
would
become.
You
know
very
important
to
get
it
done
in
the
14-0,
but
other
than
that,
like
the
board
hasn't
really
changed
much
since
the
last
we
planned
as
far
as
the
directional
items
go,
it's
still
going
to
be
the
same
direction.
We're
going
to
still
try
to
accomplish
the
same
directional
goals.
A
Andres
has
said,
has
put
in
the
direction
for
testing
for
14-0
and
he
is
going
to
continue
going
deeper
on
the
gitlab
group
migration.
A
So
he's
got
a
test
that
verifies
that
the
actual
group
is
migrated,
group
object,
but
he's
going
to
look
into
some
of
the
nested
objects
and
verify
that
you
know
the
epics
have
made
it
across
that
the
labels
have
made
it
across
to
get
a
deeper
automation,
automated
test
going
on
for
the
group
migrations
as
we
keep
going
deeper
into
you
know,
implementing
more
features
so
he's
going
to
try
to
follow
the
development
on
that
front,
which
is
really
good.
A
I
mean
that
is
where
the
code
is
most
volatile
and
that's
where
you
know
we
would
really
be
really
valuable
to
have
some
protection
against
regressions.
A
And
finally,
this
deprecation
note
the
fact
that
we
are
going
to
start
sunsetting
and
be
jason
in
140.
That
has
actually
you
know,
been
merged
into
the
documentation.
So
there's
a
note
now
in
documentation
that
starting
with
14.0,
we
will
no
longer
support
exports
in
nd,
jason,
four
groups-
jason,
sorry,
india,
you
are
correct,
yeah
the
exports
in
jason
or
groups.
A
That
said,
we
are
not
removing
any
of
the
codes.
Yet
it
is
just
that
you
know
we're
telling
people
to
stop
using
it
and
eventually
we'll
go
back
and
do
you
know,
do
the
cleanup
and
remove
all
the
code,
but
for
now
we're
leaving
it
in
because
we
still
want
to
allow
people
to
transition
over
and
be
able
to
export
from
an
older
version
in
json
and
then
still
be
able
to
import
it
into
14-0.
A
So
the
imports
using
json
and
14-0
still
work
because
you
may
have
an
older
version,
but
once
we
move
away
from
14-0,
we
no
longer
have
to
support
those
older
versions
and
at
that
point
we'll
be
able
to
remove,
remove
both
exports
and
imports
from
support
and
then
also
go
into
the
code
and
clean
that
up
as
well.
So
that's
that's
already
been
merged
in
and
that's
that's
happened
for
14
years.
So
the
only
thing
in
1400
we're
doing
is
telling
people
to
that.
We're
not
supporting
exports,
starting
in
140.
A
I
think
that's
pretty
much
it
as
far
as
the
objectives
going.
I
think
we
kind
of
looked
at
the
board
as
well
any
other
aspect
we
should
be
talking
about.
B
Well,
I'm
slightly
concerned
about
casio's
pto,
sorry
casio,
but
so
I'm
gonna
be
alone
right
and
is
the
is
the
ps
migration
going
to
is
coming
to
an
end
or
or
is
it
like
in
full
throttle
at
the
moment,
because
I
feel
like
the
moment
you
are
going
away.
Maybe
we
should
do
some
sort
of
a
brain
dump
or
something
because
100
they
will
say
something
else
is
broken,
and
I
need
to
jump
on
it
right.
D
That's
fair:
my
pto
is
by
the
end
of
this
month,
beginning
of
next
month
for
clarity.
So
we
have
a
few
weeks
in
there
kind
of
but
yeah
end
of
may
start
in
beginning
of
june
I'll
set
up
101
for
us
to
yeah.
A
Hopefully
we
get
some
clarity
before
then
like.
If
this
really
extends
through
june,
then
you
know
that
would
really
be
unfortunate.
That
said,
I.
A
B
Yeah
now
just
the
thing
is,
I
see
I
I
see
messages
since,
like
in
our
slack
channel
that
they,
the
14th
of
may
migration
deadline,
is
not
met
and
the
next
opportunity
to
complete
the
migration
will
be
august.
So
I
don't
know
if
that
means
there
will
be
nothing.
B
They
say
there
will
be
nothing
from
them
until
august
and
then
suddenly
they'll.
You
know
because
they
will.
You
know,
say
that
something's
broken.
A
My
expectation
is,
they
will
continue
right
now
to
try
to
get
it
done,
and
you
know
be
ready
as
soon
as
possible
for
august
yeah.
B
Yeah,
no
definitely
I
feel
like
if,
if
there
is
a
next
opportunity
to
complete
the
migration
in
august-
and
they
want
this
migration
to
be
successful,
then
I
don't
know,
then
it
makes
sense
to
make
sure
that
the
test
runs.
That
ps
is
performing
is
are
successful,
but
if
there's
any
fixes
that
need
to
be
done,
they
they
bring
that
up,
and
obviously
they
do.
I'm
just
saying
I'm
just
you
know
speaking
out
loud
and
yeah.
If
kaiser
is
on
pto.
B
That
means
I
will
have
to
I'll
have
to
jump
on
that.
Well,
potentially,.
A
Yeah,
if,
if
it's
really
august,
then
perhaps
10
days
is
not
going
to
be
a
critical
path,
all
right-
I
don't
know,
but
really
my
my
view
of
on
this-
is
that
I
would
like
to
get
a
more
clear
kind
of
set
of
requirements
right
now
from
professional
services,
so
that
we
can
be
of
help
to
them,
but
also
making
clear
that
you
know
we
do
not
own
this
migration.
A
A
A
Not
sure
if
there's
anything
else,
this
might
be
all
we
need
to
do.