►
From YouTube: Manage:Import 13.11 planning
Description
This is the sync planning session for the 13.11 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17318
Notable epics mentioned:
Complete Epic migration - https://gitlab.com/groups/gitlab-org/-/epics/5189
B
A
Go
so
hopefully
the
sharing
issues
have
been
resolved,
I've
updated,
zoom
and
things.
So
let
me
know
if
it
freezes
or
breaks.
So
I
could
just
stop
talking.
A
All
right,
so
this
1310
was
a
little
slow,
so
1311
looks
like
an
exact
copy
of
13
10,
because
we
were
going
to
continue
on
with
the
same
themes
but
yeah.
We
also
weren't
able
to
complete
some
of
the
epics
that
we've
started,
that
were
larger,
which
were
kind
of
a
stretch
anyway,
and
we're
going
to
take
a
couple
awesome.
So
it's
going
to
be
very
familiar.
A
Hopefully,
as
far
as
what
we're
going
to
talk
about,
but
just
to
to
go
in
order,
the
team
we
do
have
a
software
engineer,
engineer
in
testing
half
hired,
so
my
understanding
is
that
we
may
have
extended
an
offer
and
the
person
should
be
joining
imminently
so
hopefully,
by
next
time
around
we'll
have
that
one
call
as
well.
A
So
that
will
be
a
welcome
edition.
So
team
may
change
any
pto
considerations
for
the
next
four
weeks.
A
This
is
not
decided
for
me,
but
we
do
have
spring
break
here
in
the
first
week
of
april,
so
I
may
travel
for
a
couple
of
days.
It
shouldn't
be
a
big
average
or
anything,
but
I
may
take
a
couple
days
off
to
take
the
kids
to
see
family
in
texas.
B
C
I
think,
as
far
as
fun,
I'm
concerned
outside
of
friends
and
family
day,
I
don't
say
anything
so.
A
I
think
it's
worth
noting.
If
it's
you
know
two
three
days
or
more
or
three
or
four
days
or
more
right,
all
right,
so
team
velocity
will
get
updated.
So
this
is
not
the
real
thing,
but
liam
did
you
say
that
it
was
already
updated
the
chart?
A
No,
there
was
a
second
issue
which
I've
just
found
as
well.
We'll
skim
over
that
yeah,
the
the
velocity
that's
non-milestone
related,
which
is
counts
last
30
days
should
be
accurate.
I
think-
and
this
is
the
first
time
it
actually
gives
us
a
breakdown
between
backhand
and
front
end.
A
So
thanks
for
that-
and
it
seems
that
the
last
30
days
was
not
were
not
as
unproductive
as
previously
thought,
so
it
did
feel
like
a
slower
month
and
it
may
be
that
our
productivity
was
just
in
in
a
different
area,
so
we
were
doing
some
spikes
and
take
care
of
some
bugs.
It
doesn't
mean
we're
not
productive,
we're
just
not
we're
just
not
working
exactly
on
the
directional
items,
but
it
seems
like
there
was
still
velocity
there.
A
So
the
proposed
objectives.
I
did
not
call
out
as
many
individual
issues
as
I
did
last
time,
because
I
was
not
as
sure
about
them
as
last
time.
Last
time
I
was
just
like
sure
about
all
these
other
things.
We're
gonna
work
on.
Interestingly
enough,
like
looking
at
what
we
did
last
time
it
we
were
actually
spot
on
as
far
as
the
things
that
we're
gonna
get
done
so
especially
front
end
where
we
actually
called
out
the
issues
that
we
will
not
get
done.
A
I
just
want
to
congratulate
ilya
on
so
this
is
the
1310
planning.
Congratulations
on
really
closing
each
one
of
these
that
were
called
out
last
time.
So
that's
pretty
good.
A
So
this
time
around
we're
gonna
stick
with
teams
we're
going
to
look
at
the
board,
so
the
board
has
things
in
order
and
has
thing
has
issues
that
we
should
work
on.
I
just
did
not
copy
them
here,
because
I
wasn't
quite
sure
about
the
order
of
things
and
how
how
much
we
get
done,
but
generally,
the
theme
is
we
need
to.
You
know
we're
going
to
continue
to
march
as
fast
as
possible
toward
the
parity
for
group
export
imports.
A
That
is
that
there
is
a
swell
of
bugs
and
security
and
all
kinds
of
problems
out
in
the
field
with
the
project
imports,
but
also,
you
know,
to
degrade
group
imports
as
well,
and
getting
to
this
will
allow
us
to
then
deprecate
the
group
export
import
and
sort
of
train
for
how
we're
going
to
deprecate
the
project,
export
import,
which
is
the
big
goal
and
then
hopefully,
we'll
be
able
to
close
a
lot
of
issues
in
one
milestone.
A
When
we
do
that,
so
hopefully
we
can
stay
ahead
of
the
swell
and
be
able
to
just
get
to
the
point
to
where
we
feel
like.
We
have
something,
that's
better
and
then
move
our
users
to
use
that
and
deprecate
the
the
features
that
are
causing
us
a
lot
of
support.
A
A
C
A
That
are
getting
refined,
there's
still
gonna
be
some
technical
debt.
That's
gonna
need
to
be
paid,
and
I
think,
there's
still
a
spike
that
kessia
has
in
progress
that
I
expect
to
just
be
played
in
this
milestone
as
well.
A
So
we'll
just
have
to
manage
that
time
and
sort
of
balance
it
well
against
actually
delivering
some
directional
things
so
can't
have
that
blow
up
in
a
way.
A
A
But
I
expect
for
us
to
be
to
have
to
probably
pay
attention
to
one
or
two
in
this
milestone
as
well,
we'll
see
which
ones
you
know
over
the
next
week
or
so
probably-
and
this
is
also
a
good
time
for
us
in
1311
to
start
thinking
about
deprecations
and
things
that
we
might
need
to
announce
for
14
0,
because
140
is
the
big.
You
know
it's
free
deprecations
for
everybody
and
we
can
introduce
breaking
changes
so
things
that
we're
going
to
think
about.
A
Is
the
group
export
import
it's
going
to
be
too
early
for
a
14-0,
so
this
is
something
that
I
sort
of
wrote
about
a
month
ago
and
I
didn't
know
how
this
milestone
was
going
to
go.
So
it's
too
soon
right.
But
I
think
this
is
something
that's
probably
right
for
this
point
and
we
could
stop
supporting
the
old
json
export
imports
for
projects
and
or
groups.
I
think
it's
being
used
for
groups
as
well.
B
And
sorry
good
question:
what
what
are
you
calling
deprecating?
Because
deprecating
can
be
the
process
of
saying
that
we're
gonna
disable
a
feature
or
it
can
be
the
process
of
disable
the
feature
itself
so
just
to
be
clear
like
if
we're
just
deprecating
as
a
saying
that
we're
going
to
disable.
Maybe
we
can
deprecate
the
groupie
vertex
part,
because
we
can
announce
that
we're
gonna
disable
it
and
we
could
already
disable
the
json
project
important
export
on
14.
I
suppose,
since
it's
a
one
year
old
now,
yeah
but.
A
Yeah,
the
good
question
I
mean:
there's
definitely
yeah.
There
are
levels
of
deprecation
there
that
we
can
talk
about
and
kind
of
the
order
of
things.
So
you
know
announcement
is
one
then
sort
of
stopping
maintenance
is
the
next
level
and
then
actually
just
removing.
It
is
the
final
stretch.
So
for
me,
probably
where
I
see
this
one
play
out,
is
sort
of
that.
We
just
need
to
say
that
this
is
no
longer
supported
as
a
14-0.
A
So
that
we
can
play
out
later,
but
definitely
we
can
make
the
big
announcement
in
14-0
and
just
tell
everybody
it's
not
supported
and
then
if
the
code
gets
fully
cleaned
up
and
deleted
in
14,
1
and
14
2
that'd
be
fine
with
me.
A
Yeah-
and
I
think
you
know,
in
kind
of
the
same
manner
that
we
would
not
be
able
to
say
this
say
that
for
the
groups,
because
we
do
not
have
a
replacement,
there's
really
nothing
that
we
can
tell
that
they
should
go
to
instead
of
using
the
export
imports,
and
this
will
also
so
in
my
mind,
I
mean
since
we're
talking
about
this.
This
is
definitely
going
to
be
a
stage
thing
to
where
I
think.
A
First,
we're
gonna
have
to
stop
exporting,
but
then
still
import
for
a
while,
so
that
people
can
migrate
from
older
versions
or
wait
the
other
way
around.
Whichever
way
we
need
to
yeah,
we
need
to
allow
people
to
migrate
from
older
versions
to
new
versions,
and
this
one
in
particular.
A
So
once
we
have
that
ability
you
know,
then
we
can
stop
exporting
and
then
require
the
users
to
use
the
migration
to
pull
the
data
across
so
that'll
be
kind
of
the
turning
point
is
once
we
have
all
the
graphql
things,
and
it's
it's
a
milestone
that
you
know
all
of
our
customers
have
taken,
or
that's
looking
at
probably
a
couple
miles
milestones
later
by
the
time
that
it's
been
upgraded
everywhere,
then
we
can
say
that
okay,
we're
no
longer
going
to
do
this
and
now
you're
going
to
have
to
use
the
group
migration.
B
Another
step
for
consideration
the
documentation
for
the
new
importers.
I
think
it's
coming
way
better
than
the
documentation.
We
are
trying
to
keep
updated
all
the
time
that
we
introduce
new
importers
and
which
version
we're
introducing
those
importers.
So
maybe
even
before
deprecating
the
the
old
importers
percy,
we
could
at
least
link
the
old
documentation
to
the
new
and
try
to
make
it
more
popular,
announce
it
more
because
the
documentation,
I
think,
will
be
better
and
will
institute
people
to
be
using
the
newest.
A
That's
a
great
point
so
update
documentation
to
explain
to
users
that
they'll
now
be
able
to
use
this
thing
and
then
point
them
in
direction
any
documentation.
I
like
that
so
I'll
create
a
couple
of
issues
so
I'll
create
an
issue
to
update
documentation,
also
create
issues
for
deprecating
each
one
of
these.
So
we
can
start
tracking.
You
know
the
to-do's
and
all
the
things
that
we
need
to
get
done.
A
Okay,
so
that's
that's
kind
of
the
objectives
of
the
of
the
milestone.
It's
not
hopefully
anything
new.
I
think
there's
a
need
to
go
back
to
the
road
map
because
we
will
be
the
last
time
and
it
really
hasn't
changed
much
probably
time
for
us
to
just
take
a
look
at
the
kanban
board
and
see
if
there's
any
questions
around
things
that
are
there
or
just
you
know,
doesn't
make
sense.
I've
confirmed
the
refinement
up
to
almost
what
my
limit
is,
so
we
can
talk
about.
A
If
that's
not
enough,
we
can
increase
the
limits,
but
I
feel
like
this
is
a
good
chunk
of
things
for
us
to
just
really
focus
on
in
a
milestone
and
having
more
things
would
probably
defocus
our
work.
So
I
think
that's
probably
the
right
right
thing
to
do
so.
The
things
that
are
in
ready
for
development
I
feel
like
we
should
try
to
push
those
across
prior
to
just
you
know,
going
and
getting
more
things
in
from
refinement.
A
I
mean
we
can
start
a
refinement
on
these,
but
even
if
something
is
a
p4,
I
feel
like
this
might
be
a
good
time
for
us
to
just
go
ahead
and
take
this
out,
and
so
that's
just
like
how
I
see
it
take
care
of
these
first
and
then
move
on
to
the
things
from
refinement
but
start
refining
early,
so
that
we
have
things
ready
so
so
that'd
be
good.
A
It'd,
be
really
good
to
get
to
the
bottom
of
this,
because
there's
been
some
things
here
been
sitting
for
for
months,
there's
always
something
more
important,
so
maybe
now's
the
time
to
do
that.
A
As
far
as
things
in
refinement
toward
the
very
top
you'll
see
all
directional
things
and,
at
the
very
very
top
you'll
see
the
things
related
to
graphql,
because
that
is
the
that
is
going
to
be
the
limiting
factor
for
us
to
be
able
to
do
the
deprecation.
So
the
sooner
we
identify
and
then
make
all
these
changes
like.
That
will
be
the
earliest
time
that
we'll
be
able
to
say.
Okay.
We
support
we'll
have
to
support
group
export
import
up
to
that
point
and
then
past
that
we
no
longer
have
to
so.
A
If
you
know
maybe
14-0
is
where
we
do.
That
that'd
be
a
great
point
to
then
be
able
to
come
back
to
later
and
say:
okay,
if
you
have
14-0,
you
not
have
to
use
migrations.
So
if
we
take
care
of
those
graphql
issues
and
identify
them
all
in
this,
and
the
next
milestone
then
we'll
be
able
to
see
that
in
the
future-
and
that
sounds
like
a
good
wrong
number
to
do
that
past-
that
we
have
the
board
migrations.
A
I
split
this
into
two,
so
there
was
boards
and
board
lists,
and
now
we
have
two
issues
for
that
that
are
in
refinement.
A
Migrating
avatars
is
something
endless
we're
just
not
doing.
I
did
not
catch
that
first
time
around.
We
did
not
plan
for
it,
but
it's
not
happening,
so
it
means
an
issue
and
another
backhand
thing.
So
this
is
one
of
those
that
I
know
why
this
is
a
backhand,
maybe
or
maybe
a
front
end
you'd.
Look
into
that,
but.
B
The
series
that
I
can't
elia
did
a
comment
in
there.
It's
something
that's
not
being
updated
on
the
right
hand,
side.
A
Oh
okay,
yeah,
because
I
thought
this
started
as
a
there.
We
go
so
it
started
as
a
front.
End
turned
out
to
be
back
in,
got
it
yeah,
so
we'll
need
to
look
into
that,
because
this
is
definitely
one
of
those
that
we,
like
github
importer
is
not
going
to
deprecate
or
anything
it's
actually
going
to
become
more
important.
A
A
This
is
a
so
as
far
as
the
front
end
goes
we'll
just
yeah
we'll
just
have
to
filter
the
front
end.
So
take
a
look
at
that.
A
That
all
right,
so
the
two
issues
isn't
ready
for
dev
and
then
there's
two
issues
in
refinement.
This
probably
won't
be
enough.
So
I'll
take
a
look
at
some
of
these
things
that
are
actually
almost
ready
for
refinement,
which
you
need
to
figure
out
if
we
need
to
split
them
into
multiple
issues.
So
the
view
history
for
groups
and
projects
have
passed
have
been
just
completed
by
ux
and
we
just
need
to
break
this
down
into
multiple
engineering
issues
and
then
move
each
one
of
those
into
refinement.
C
Okay,
I
mean,
I
think,
based
on
our
average
weight,
we're
probably
good
in
the
refinement
rarity
for
development
and
there's
plenty
of
planning
breakdown
that
we
can
start
to
move
forward
along,
but
yeah
yeah.
A
Yeah,
like
with
breakdown,
I
think,
we're
safe,
but
it
just
tells
me
that
I
don't
want
to
wait
a
month
to
take
a
look
at
a
breakdown
to
move
things
into
refinement.
As
soon
as
some
things
got
moved
out
of
the
refinement,
there
should
be
things
backfilling
there
and
our
front-end
last
30-day
velocity
was
25
and
the
average
was
17.
A
So
it
does
feel
light
as
far
as
what's
available
to
pick
from,
but
but
we
have
plenty
here
in
refine
and
breakdown
where
we're
going
to
tease
out
several
issues
out
of
that
and
should
be
able
to
back
the
refinement
easily.
So
that's
that's
front
and
I
think
beckon
is
in
a
different
boat
or
I
think
there's
enough
things
in
refinement
and
there's
no
need
to
specifically
go.
A
C
Yeah,
if
we
look
at
the
three
month
average
it's
a
little
bit
lower
than
that,
I
don't
think
we
should.
I
think
last
month
was
particularly
productive,
because
there's
a
lot
of
usability
improvements
that
were
smaller
and
things
like
that.
I
mean
we'll
continue
to
refine
and
things
like
that,
but
yeah
yeah.
A
A
Likely
to
just
end
up
here
anyway,
so
with
that
said,
you
know
feel
like
the
backhand
backlog
is
good
enough
and
the
next
step
for
me
to
really
break
down
and
refine
it
a
little
bit
from
some
of
the
front
and
stuff
and.
A
Questions
all
right:
well,
that's
quick,
awesome
I'll,
give
everybody
back
25
minutes
or
so
thank
you
for
attending
and
have
a
great
week.