►
From YouTube: Manage:Import 14.6 planning
Description
This is the sync planning session for the 14.6 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17412
A
The
goals
of
headcount
reset
in
14.6.
This
is
where
we're
gonna
wrap
up
a
lot
of
that.
A
A
I
would
think
you
know
most
of
developers
in
us.
C
That
that's
a
good
point.
I
I
tend
to
just
assume
everyone
assumes
american
thanksgiving.
C
Is
off
so
I
I
should
speak
up
on
that
yeah
and
for
me
also
like
a
week
after
my.
B
Vacation,
I
will
be
working
on
a
shift
at
the
time
frame
more
more
closer
to
the
u.s
time.
B
Yeah,
my
like
my
winter
season,
winter
mountain
season
is,
is
starting
so.
A
Cool,
so
is
there
still
this
this
effort
going
on
that
impacts,
your
time.
B
B
B
At
least
in
the
the
dev
quality
department,
I
think
shares
some
of
the
tasks
the
the.
B
You
don't
make
sense,
okay,
so
the
like,
I
said,
headcount
resets,
still
going
on
until.
A
A
Off
a
little
sooner
than
that,
but
we'll
we'll
look
at
the
boards
and
see
where
everything
is.
A
A
Milestone
but
really
what's
accurate
is
just
kind
of
looking
at.
A
14
4
and
clearly,
given
that
we've
gotten
a
lot
more
people
on
it.
It's
looking
really
good.
A
Proposed
objectives,
I
haven't
changed
since
as
much
since
last.
We
spoke
a
month
ago
because.
A
A
Up
for
the
project
export
import
by
replacing
it
pretty
much
so
we'll
we'll
look
at
those
boards.
A
Plenty
of
fun
and
work
in
those
areas
to
to
make
that
the
product
that
we
needed
to
be
so.
A
A
The
exposed
information
about
what
will
not
be
migrated
is
kind
of
a
user
experience.
A
Thing
where
oh,
this
is
different,
I
thought
it
was
going
to
be
a
different
issue.
A
So
yeah,
maybe
you
could
tell
us
yeah
for
sure
recently
on
the
back
end,
they
was
implemented.
D
It
will
will
be
and
it
might
be,
an
updated
one
outdated
one
and
we
need
to
communicate
this.
D
D
D
A
Yeah
yeah:
that's
the
discussion
that
we
had.
That
was
a
really
good
discussion
to
be
had
to.
A
Sort
of
sort
out
how
we're
gonna
do
transitioning,
you
know
as
we
go
from
not
being
to
to.
A
A
Of
source
and
destination
is
is
going
to
like
impact
all
of
that,
so
we
had
a
great
discussion.
A
We
got
to
agreement
of
how
it's
going
to
look
so
this
is
this
looks
really
sharp
as.
A
A
A
Going
to
be
able
to
tell
what's
going
to
work
and
what's
not
going
to
work
when
they
migrate.
D
Yeah
and
my
two
cents,
as
as
gitlab
expands,
I
believe
that
new
and
new
things
will
appear
even.
D
D
D
Yeah,
this
is
great,
so
this
is
a
great
addition
to
the
user's
experience,
especially
now
in
the.
A
Documentation
to
figure
out
what
may
or
may
not
come
across
yeah
for
second
one.
It's
just.
D
Continuing
finishing,
actually,
they
work
on
git
validation,
which
was
recently
introduced.
D
Initial
git
import
could
be
initiated,
oh
yeah,
I
mean,
and
this
sources
also
needs
the
same.
A
A
D
My
developer
list,
which
I'm
migrating
grown
very
big,
and
I
really
believe
the
sticky
column.
D
A
This
is
it
this
is.
This
is
really
good
priority
for.
A
Thank
you
for
that,
so
quality,
maybe
andre.
You
could
talk
about
your
priorities,
yeah,
so.
B
B
So
that
to
the
tests
that
migration
finishes
without
errors,
it
already
caught.
One
issue
like.
B
Customer
but
it's
still
like,
like
some
underlying
errors
that
shouldn't
be
there.
B
And
one
issue
is
now
kind
of
happens
periodically,
which
is
the
worst
thing.
B
Usually
to
understand
if
it's
a
test
issue
or
or
actual
application
issue,
I
will
most
likely.
A
Okay,
so
is
there
anything
on
the
github
importers
side?
I
know
we
have
that
yeah.
B
B
Import
that
runs
daily
got
broken
somehow
and
I'm
not
like
I'm
fairly
certain.
It's
like
it's.
B
A
But
for
the
github
importer
that
would
be
valuable
to
sort
of
add
that
we're
not
covering.
A
Currently
depends,
I
think
it
depends
on
amount
of
spare
time,
because
you.
B
B
A
Okay,
so
any
thoughts
about
anything
else,
high
level
before
we
go
and
just
review
the.
A
Possible
in
in
the
milestone,
so
do
we
have
a
yeah?
I
guess
we
have.
A
Sorry
would
you
have
any
comments
on
like
how
this
is
going
and
maybe
how
far
you
think,
like
you.
A
Know
how
far
down
the
backlog
do
you
feel
like
you
might
be
able
to
get
during
14
and
six
yeah.
C
I
think
the
I
could
probably
get
through
the
pipeline
triggers
in
history,
but
I
don't
know.
C
C
D
Else
makes
it
across
fine,
but
if
not
that's
sort
of
the
goal
we're
trying
to
achieve.
A
A
And
here's
the
thing:
well,
here's
one
one
board
that
looked
very
similar
a
month
ago
when.
A
We
looked
at
it
and
I
thought
this
was
just
gonna
get
cleaned
out,
so
maybe
we
can
talk
about
how.
A
D
Just
to
10
cents
from
me,
I'm
just
working
on
the
security
feature,
which
is,
I
believe,
the
only.
D
In-Depth
it
will
be
a
carryover
our
milestone,
but
I
hope
to
make
it
to
the
next
security
release.
D
Which
is
one
week
later
on
the
release,
but
I'm
not
sure
I'm
pretty
sure
that
the
one.
D
In
ready
for
development
is
still
blocked
by
italy
team
if
I'm
correct
so
but
hey
well,
I'm
still
a.
A
Some
kind
of
a
slightly
so
some
kind
of
follow-up
to
see
sort
of
where
this
might
be.
D
Minor
work
from
our
side
to
pass
the
property
to
italy,
but
it
will
be
a
really
quite
small
one.
A
And
then
I
think
you
know
I
sort
of
know,
because
I
asked
about
the
attribute
cleaner,
that
we.
A
Close
this
issue
that
can
start
which,
because
it's
it's
just
tracking
all
of
the
other
issues
so.
A
A
Similar
to
each
other,
so
maybe
they
can
all
get
looked
as
a
group
and
pushed
across
as
a
group.
A
There
is
this
new
flow
that
we
can
use
also
to
indicate.
I
don't
know
if
that's
kind
of
where
this.
A
Doing
anything
on
it,
then
you
know
this
is
kind
of
where
we
need
to
place
some
things
for.
A
A
Somebody
actively
doing
something
on
it,
so
my
thoughts
on
it,
I
think
doug
has-
may
have
pinged.
A
And
this
here
is
a
a
new
incoming
issue
that
landed
on
our
plate.
This
is
the
only
one.
A
A
It's
in
the
backlog
and
it'd
be
great
if
we
can
get
that
going
as
well.
F
F
That
further
and
I
give
weekly
updates
in
the
engineering
allocation
meeting
around
the.
F
Confidential,
so
that
they
don't
necessarily
have
to
wait
on
the
the
security
release.
I
don't.
F
Know
whether
there
is
already
a
plan
as
to
your
point,
to
sort
of
test
them
all
in
batch
at
the
end.
F
So
I
will,
I
will
check
in
there
and
make
sure
we
get
it
cleaned
up
or
at
least
status
updates.
F
On
maybe
like
the
parent
issue
of
what
the
plan
is:
okay,
cool
yeah
and
this
one
looked
like
you.
A
Know
if
we
could
maybe
push
some
things
across
here,
we
could
just
quickly
call
this
done.
A
A
I
think
that's
all.
I
have.
A
A
F
We
need
to
do
in
terms
of
like
making
the
lives
easier
for-
I
guess
us,
but
george.
F
Sort
of
already,
but
he
was
wondering,
if
there's
anything
else,
we
should
consider
this
milestone.
A
It's
a
good
question.
I
would
say
that
it'd
be
good
if
we
could
just
do
a
taper.
A
A
But
at
the
same
time,
I
don't
expect
anyone
to
start
an
issue
right
before
the
end.
So
if.
A
And
I
think
that's
probably
the
best
way
to
to
end
this,
and
so
that's
just
my
thought.