►
From YouTube: Manage:Import 14.10 planning
Description
This is the sync planning session for the 14.10 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17472
A
Hello
all
and
welcome
to
the
14.10
planning
call
for
import.
A
We
are
going
to
be
taking
a
look
at
what's
up
for
the
import
team
in
next
milestone.
A
A
So
the
velocity
seems
to
be
more
stable.
As
far
as
the
issue
number
goes,
there's
some
kind
of
a
weight
increase
here
for
the
previous
milestone,
but
this
is
kind
of
fairly
I'd,
say
typical
flight.
I
don't
see
any
big
deviations
there,
so
the
proposed
objectives
for
for
this
is
hopefully
this
is
hopefully
a
milestone
of
a
pivot
to
where
we
go
from
that
big
focus
on
security
and
and
the
whole
engineering
allocation,
two
more
of
directional
items,
so
it
seems
like
we
are.
A
We
have
two
engineering
allocation
items
open
and
they're
and
they're
both
in
review.
So
once
we
get
once
we
take
care
of
those
once
those
are
completed,
then
we
should
be
able
to.
You
know,
mix
a
lot
more
things
into
into
what
we're
doing
and
hopefully
we'll
be
able
to
pick
up
some
directional
stuff.
A
So
for
1410
I
feel
like
we're
going
to
come
in
with
some
inertia.
There
is
a
security
item
that
I
know
georgia
working
on,
should
the
baby
be
completed
for
49,
but
there
was
another
one
that
got
added.
A
So
we'll
probably
just
need
to
pick
pick
this
up
so
that
we
stay
on
top
of
our
security
issues
and
then
we
don't
let
that
backlog
grow
and
but
then
past
that
you
know
we
can
probably
focus
on
these
two
directional
items,
which
is
for
the
project,
migration,
adding
the
releases
and
the
designs
which
would
then
complete
our
parity
with
the
current
project
export
import.
That
is
a
huge
milestone.
A
So
that
is
big,
because
once
we
migrate
everything
that
the
current
project,
migration
and
current
project
export
import
does,
we
will
be
able
to
start
promoting
this
way
of
migrating
groups
and
projects
together
as
the
primary
way
for
people
to
move
groups
and
projects
and
to
the
point
to
where
you
know,
we
could
probably
start
planning
over
over
several
milestones
to
change.
A
The
ui
to
you
know
make
this
the
primary
way,
maybe
even
eventually
take
out
the
project
export
import
out
of
the
import
flow
ui,
and
only
let
people
maybe
go
to
the
project
where
they
do
the
download.
Maybe
they
could
do
upload
there.
A
So
maybe
we'll
just
remove
it
from
like
the
obvious
way
for
people
to
access
it
and
maybe
ban
it
into
some
kind
of
a
secondary
flow
to
deprioritize
as
much
as
possible,
so
something
that
comes
from
that
is
we're
going
to
be
very
responsive
to
the
bugs
we
find
in
the
project.
Migration-
and
I
know,
there's
there's
one
now
open
and
I've
come
across.
You
know
a
couple
different
little
improvements.
Some
are
about
summer
enhancements,
so
we'll
be
prioritizing
some
of
that
stuff.
A
You
know,
maybe
not
this
milestone,
but
next
milestone
at
the
furthest
in
order
to
make
sure
that
this
experience
is
really
solid
before
we,
starting
before
we
start
to
make
that
switch
and
start
to
advertise
it
more
because
there's
no
there's
no
second
chance
on
first
impressions,
so
we'll
try
to
impress
people
with
a
solid
way
to
do
this.
That
is
a
clear
upgrade
from
what
they've
been
doing.
C
A
A
That's
also
something
we
don't
do
currently,
but
it's
been
asked
for
a
lot
and
it's
pretty
much
an
expectation
so,
but
that
makes
it
so
that
I
can
talk
to
professional
services
sooner
and
tell
them
that
you
know
we
already
do
everything
that
so
as
soon
as
we
have
designs,
we
already
do
everything
that
we
currently
do.
So
it
just
you
know,
moves
our
plan
like
the
marketing
plan
a
little
sooner.
I
don't
think
it
changes
the
priorities
of
things
but
yeah.
C
I
just
want
to
point
out
that
you
know
migrating
releases
is
a
lot
of
data
like.
C
Magnitudes
more
so,
I
think
we
should
be
very
careful
if
that's
something
that
we
want
to
pursue
because,
as
far
as
I
understand
releases
include
all
the
artifacts
and
stuff,
like
the
actual
files
that
you
know,
whatever
the
files
that
are
being
put
in
there
is
what's.
C
Of
gitlab
project
release
is,
but
you
know
it
can
be,
let's
say:
well,
I'm
downloading
it
now
and
it's
gonna
be
like
a
gigabyte
or
something.
So
if
you
multiply
the
amount
of
releases
like
120
like
dry
120
releases
in
github
right
now,
that's
like
a
120
gigs.
You
know,
so
I'm
just
saying
that
it
might.
C
A
C
A
Later
so
yeah,
let's,
let's
maybe
continue
refining
this
and
you
know
split
it
across
that
line,
potentially
so
split
it
across
the
line
to
where
you
know,
we
migrate
the
fact
that
there
is
a
release
and
whatever
the
release
notes
are
whatever
you
know.
The
lighter
object
by
the
actual
the
file,
maybe
not,
and
there's
maybe
an
option
eventually,
because
at
some
point
we're
gonna
have
to
start
having
some
options.
For
how
can
I
get
a
leaner
migration?
A
You
know
like
don't,
migrate,
closed
issues,
or
you
know
things
like
that,
like
leaving
some
things
behind
that
have
been
archived
has
been,
there's
been
discussion
about
it
or
leaving
some
things
behind
that
are
older
than
x.
A
So
that
could
be
a
separate
discussion
then,
together
with
this
and
then
maybe
provide
some
options
for
migrations
to
where
users
can
specify
how
much
how
much
data
they
want
to
get
or
how
much
stuff
they
want
to
migrate.
They
really
want
everything
or
not
so
that'd,
be
a
good
discussion,
but
yeah
thanks
for
bringing
it
up.
Let's
work
on
splitting
at
least
this
issue
because
it
seems
like
it
could
be
split
at
least
once.
B
C
Yeah
I
mean
a
release,
is
just
a
like
a
tag
yeah
like
a
a
nicer
way
of
presenting
your
source
code,
but
I
think
you
can
well
I'm
not
too
sure,
I'm
not
too
familiar
with
the
releases
functionality
but,
for
example,
in
github
yeah
you
could
upload
assets
to
the
right.
C
A
It
could
be
well,
let's,
let's
have
a
quick
run
of
refinement
on
this-
we're
not
going
to
pick
it
up
tomorrow
and
then,
if
we
come
to.
If
it
comes
to
the
point,
you
can
always
pick
up
the
designs
and-
and
let
this
one
simmer
for
another
week
until
we
know
exactly,
you
know
how
to
make
it
as
small
as
possible
as
a
first
iteration.
C
A
Yep
good
discussion
so,
for
the
front
end,
a
few
things
are
in
flight,
but
those
are
removed
from
here
because
they're
expected
to
arrive
in
49
the
one
big
one
that
we
have
accomplished
in
49
is
the
project
import
history,
which
looks
like
the
group
import
history,
where
all
the
imports
bitbucket
github
gitlab
are
all
on
one
page,
so
that'll
be
a
great
improvement
and
allow
people
to
understand
when
projects
have
been
project,
imports
have
succeeded,
failed
and
you
know
where
all
of
them
are
and
if
you've
done
multiple
imports
multiple
times
from
the
same
source.
A
Those
will
be
like
all
separate
entries,
so
that
will
be
very,
very
helpful
so
for
1410
we're
looking
at
showing
that
detail
status
for
github
importer
and
for
those
of
you
who
haven't
seen
it.
So
this
was
kind
of
the
starting
point
like
an
idea
of
just
having
a
way
of
seeing
more
of
what's
happening,
so
not
just
kind
of
having
the
importing
tag
there.
But
like
really
no
movement,
I
really
can't
tell
if
it's
importing
or
not
and
if
it
takes
hours
like,
is
it
frozen?
Is
it
not?
A
Do
I
keep
refreshing?
So,
there's
just
a
lot
of
anxiety
about
like
what's
happening
with
imports,
so
what
we're
looking
to
do
is
provide
a
way
and
here's
a
a
little
bit
more
detail.
Let
me
see
if
there
is
yeah,
so
this
is,
I
think,
kind
of
the
view
that
we're
looking
to
to
implement,
where
there's
an
expandable
details
section
in
the
row
to
sort
of
show
the
details
of
this
particular
import,
whether
it's
in
progress
or
completed
so
for
completed.
A
These
will
be
the
final
numbers
for
the
ones
that
are
still
importing.
These
will
be
kind
of
the
numbers
in
progress
and
eventually
so
not
part
of
I'm
not
sure
if
that's
gonna
be
part
of
this
issue
or
not,
but
we
need
to
like
split
that
off
having
the
partial
import
or
completed
with
failures
or
completed
with
you
know,
however,
we
would
have
phrased.
This
is
definitely
becoming
a
lot
more
important
to
to
point
out.
A
So
that's
that's
big
that
that'll
be
that'll,
be
a
great
improvement
to
have.
I
know
this
is
this
is
still
kind
of
the
design
is
hopefully
almost
complete,
so
it's
not
quite
ready
for
pickup,
but
hopefully
inside
of
1410
we'll
be
able
to
complete
the
refinement
of
it
and
then
and
then
be
able
to
pick
it
up.
So
that's
that's
the
one
big
issue,
please
chime
in
in
here.
A
If
you
have
ideas
or
thoughts
or
reservations,
and
then
there's
this
one
issue
that
just
helps
up
with
our
okrs
because
we're
trying
to,
I
think
it's
really.
Is
it
really
just
us
or
is
it
really
related
to
the
the
other
ux
get
the
pajamas,
the
pajama
stuff
right,
yeah.
A
And
then,
as
far
as
quality
goes
two
things
andre,
you
wanna,
maybe
tell
us
about
it.
B
Yeah,
so
I
was
looking
through
what
what
we
already
have
in
terms
of
gateway
migration
coverage.
It
seems
I've
managed
to
catch
up
more
or
less
with
development
on
all
the
major
parts,
and
so
I
created
a
task
which
we
actually
discussed
a
while
ago
in
in
one
of
the
dailies.
B
I
think
that
we
would
like
to
also
have
a
similar
test
to
what
we
do
with
the
github
importer
and
that
is
actually
import
real
life,
somewhat
larger
project
to
kind
of
catch,
the
data
related
issues
and
just
to
monitor
the
performance
and
stuff.
B
B
And
the
other
one
is
still
like
a
continuation
of
our
github
importer
test,
which
is
still
failing
on
staging
it's
not
failing
on
on
the
like
isolated
environment,
so
would
be
good
to
understand.
What's
the
issue
there,
so
we
kind
of
are
a
bit
more.
D
A
Any
regressions.
B
A
B
Have
to
get
yeah
okay,
I
think
it
will
be
like
it
will
be
useful,
because
the
end-to-end
tests
that
we
run
in
merger
lists,
they
are
very
limited
in
scope
that
they
check
only
the
bare
bones
functionality,
so
they
wouldn't
necessarily
catch
any
performance
problems
or
or
like
more
elaborate
project.
Setups.
A
And
a
lot
of
times
you
know
what
these
do
is
is
protect,
protect
the
functionality
from
features
being
implemented
by
other
teams.
So
you
know
we
get
a
lot
of
regressions
from
people
implementing
something
new,
some
some
new
data
element
that
requires
some
other
data
element
and
then
we
don't
catch
those
failures
and
it
becomes
an
emergency
for
us.
B
B
And
in
the
essence,
the
the
first
task,
and
actually
the
second
task
as
well,
they
are
kind
of-
might
might
take
a
while
to
implement.
I
didn't
add
anything
else
to
this
milestone
this,
especially
since
I'm
of
next
week,
I'm
not
sure
when,
when
this
milestone
starts,
but
still.
A
Yeah
that'll
be
pretty
much
the
first
week
of
the
milestone
that
you're
out
yeah
all
right
cool
and
then
there's
this
lingering
documentation
issue
that
we
do
need
to
complete.
And
it
is
really
just
catching
up
documentation
to
all
of
the
recent
changes
and
updates
that
we've
done.
A
And
then
I
think
past
that
we're
also
going
to
be
looking
at
a
little
bit
of
refactoring
the
documentation
to
to
really
represent
how
we
think
about
people
importing
versus
just
kind
of
having
these
be
searchable.
But.
A
For
example,
does
the
gitlab
migration
live
under
group
imports
or
under
project
imports?
Should
they
live
under
both
and
like?
How
do
we
represent
that
in
our
documentation?
That's
not
structured
for
this
new
feature
really
well,
so
that's
gonna
be
probably
a
follow-up,
but
first,
let's
just
get
the
information
in
so
that's
up
to
date
and
then
we'll
make
it
easier
to
consume.
C
Yeah,
another
thing
that
I
want
to
add
is
the
gitlab
migration
tool
it
allows
well,
it
allows
just
project
imports
on
the
on
on
their
own
as
well.
It
doesn't
require.
You
know.
E
I
I
thought
about
that,
but
for
now
it
is
like
we
do
not
have
we
have
an
ability
in
ui
to
select
on
the
top
level
group
for
import.
So
unless
that
change
it,
we
should
treat
it
as
a
group
one.
I
also
I
was
also
thinking
to
like
well
in
the
future.
We
would
say:
hey
you
need
to
move
anything
from
gitlab
project
group.
No
matter
you
should
go
to
gitlab
migration,
but
this
is
a
matter
not
of
the
nearest
future.
Unfortunately,.
C
Yeah,
no
for
sure,
right
now,
the
gitlab
migration
is
tied
to
groups
that
include
projects
but
like
later
on,
which
can
definitely
expand,
is
to
just
allow
project
migration
using
the
gitlab
migration
tool,
where
you
know
similarly
to
how
we
create
a
new
group,
we
allow
you
know
how
we
import
a
new
group.
There
are
two
choices:
file
based
or
enter
the
url.
C
A
Yep
no
great
points
and
yeah.
So
that's
kind
of
part
of
like
how
we
think
about
this
and
I
feel
like
in
the
end
there
will
be.
You
know:
it'll
be
a
separate
choice.
It
will
really
it
really
wouldn't
be
tied
to
groups
or
projects.
It
will
be.
You
need
to
migrate
anything
from
a
gitlab
instance
to
another
instance.
So
gitlab
migration
is
its
own
thing
separate
from
project
imports
and
projects.
You
know,
project
export
imports
and
group
exporting
ports
will
hopefully
just
go
away.
A
So
this
will
be
the
only
way
to
really
migrate.
The
groups
but
you're
write
the
projects
which
are
available
right
now
through
the
api
so
and,
and
the
professional
service
is
aware
of
that,
and
they
may
take
advantage
of
that
in
congregate.
They
may
be
calling
this
api
to
migrate
projects
to
begin
with,
but
yeah
I
think
like
the
first.
Maybe
a
boring
solution
would
be
to
just
add
another
choice
to
the
project
imports
and
have
pretty
much.
This
would
be.
A
This
was
really
a
sprint
to
a
word.
The
minimum
functionality
that
we
can
feel
is
useful
to
someone
so
kind
of
the
mvc
and
getting
to
the
point
to
where
people
are
going
to
start
using
it,
and
it
is
a
replacement,
hopefully
for
the
old
project,
export
import
and
group
export
imports.
But
yeah
there's
a
lot
more,
that
we.
D
A
With
it
so
we'll
plan
for
that,
we
do
want
to
take
a
look
at
also
a
lot
of
the
flow
and
the
wording
around
this
to
ensure
that
users
are
aware
what
actually
gets
migrated
in
each
one
of
the
cases.
A
D
A
To
sort
of
see
where
all
that
we
talked
about
is
on
it,
you'll
see
that
the
board
does
have
several
things
that
are
in
progress
by
external
contributors
and
what
I've
read
somewhere
or
heard
somewhere
is
that
this
is
some
kind
of
a
class
and
that's
why,
like
a
lot
of
people
from
the
same
area
like
suddenly
signed
up
to
to
do
this
work?
A
But
it
seems
like
it's
some
some
part
of
class,
which
means
that
there's
a
lot
of
hand
holding
and
we
have
had
help
from
people
outside
of
imports
like
bob
and
stan
like
a
couple.
Other
people
have
chimed
in
and
are
trying
to
help
these
along.
But
there's
some
there's
some
noise
from
that
to
be
taken
into
account.
A
Things
that
are
ready
for
development
are
some
of
the
bugs
and
issues
that
were
recently
identified
so
that
video
that
I
did
there
was
just
few
low-hanging
fruits.
So
I
would
consider
these
more
as
not
kind
of
a
primary
goal
for
the
for
the
milestone.
But
if
we
have
some
bandwidth
a
few
things
that
could
be
potentially
done,
especially
the
bug
here
on
top
of
refinement,
are
the
two
migration
ones
that
we
discussed.
The
two
back
end
ones
the
designs
and
the
project
releases.
A
This
one,
as
we
mentioned,
might
be
broken
up.
This
one
might
be
ready
to
be
picked
up
and
I
think
that's
probably
it.
I
have
moved
some
things
out
of
refinement
and
kind
of
back
into
this
area
here,
where
I'm
not
ready
to
schedule
it
yet
because
I
don't
want
to
pollute
the
refinement
as
much,
but
it's
it's
a
staging
area.
A
So,
as
far
as
design
goes
anything
you
want
to
point
out,
then
that
is
kind
of
your
on
your
radar
for
the
next
milestone.
F
F
Otherwise
I
think
a
focus
for
this
milestone
will
be
taking
stock
of.
What's
there
already,
what's
still
applicable
and
prioritizing
some
of
that
stuff
to
move
forward.
A
A
And
I
think
it's
a
good,
it's
good,
that
we
are
focusing
some
on
sort
of
rehashing
the
current
experience
and
polishing
that
up.
You
know
because
I
think
we're
getting
to
like
once
we
get
to
that
nbc
for
the
project
migration.
I
think
we
kind
of
pause
and
look
back
and
see
you
know
what
what
is
some
technical,
that
we
may
need
to
pay
back.
What
is
some
of
the
ux
that
we
need
to
pay
back?
A
A
You
know,
should
be
priority
before
like
adding
a
lot
more
new
functionality
in
so
so
then,
thanks
for
looking
at
that
flow
and
and
hopefully
catching
the
things
before
they
go
out-
and
you
know
frustrate
people-
and
that's
kind
of
the
point
of
why
I
did
some
of
the
walkthroughs
that
I
did
is
to
sort
of
catch
some
obvious
things
that
may
not
be
logical
to
someone
who's
using
it
for
the
first
time,
for
example,.
D
A
C
Well,
I'm
still
not
sure
about
those
releases
in
project
releases
to
be
included
in
the
migration.
Perhaps
we
can
also
add
mr
approvers
as
a
backup,
or
I
mean
I
don't
know,
we're
quite
flexible.
It's
not
like
we're
locking
in
the
these
issues
for
the
milestone,
because
we're
doing
kanban
so.
A
A
Heard
that
never
be
being
asked
for,
but-
and
also
it
was
my
understanding
that
that
portion
was
already
coming
across
from
the
project
export
imports.
So
for
me
to
be
able
to
go
in
front
of
everybody
and
say:
please
not
everybody
use
this,
because
there's
no
reason
why
you
shouldn't
I
needed
to
have
everything
that
was
there.
So
if
that's
not
there,
that
definitely
takes
it
back
in
priority.
C
Well,
I
don't
think
we
migrated
releases,
but
I
don't
know
maybe
congregate
is
doing
something
something.
Custom,
no.
A
Probably
not
no,
no,
so
we'll
take
we'll.
Take
we'll
take
a
look
at
this,
so
this
one,
you
know
clearly
doesn't
need
to
be
picked
up
right
now
and
you're
right.
If
this
becomes
you
know
either
we
split
it
and
we
take
the
smaller
piece
in
or
we
substitute
the
mr
approvers.
If
we
get
that
far
like
I'd,
be,
it
would
be
lucky
if
we
can
actually
get
into
two
three
of
these
final
issues
in
1410.
That
would
be
really
a
great
release:
okay,
yeah
and
the
mr
approvers.
I
feel
like
that.
A
One
is
fairly
ready.
I
think
that
one's
refined,
potentially
or
or
close
to
be
refined.
C
A
We
do
have
some
some
ideas
for
the
maybe
from
the
from
github
migration
of
what
what
might
be
some
of
the
because
now,
actually
they
didn't
come
across
in
github
either
yeah.
So
maybe
not
so
maybe
this
is
a
little
bit
of
a
discovery.
B
C
Already
to
have
it
approved
the
rest,
I'm
not
too
sure
yeah.
A
So
we
can
potentially
split
off
some
of
those
things,
so
you
know
things
like
an
event
that
says
this
was
approved
would
be.
C
C
Play
with
what
are
we
gonna
do
if
there's
no
user,
you
know
if
the
member
mapper
is
not
did
not,
you
know,
migrate,
the
user.
That
means
we
shouldn't
migrate,
the
approver
either.
So
I
don't
know
that's
something.
A
Feel
like
that
would
be
the
same
like
we'll,
probably
keep
the
same
rules
around
assignees
and
approvers.
So
you
know
we
have
those
rules
and
we
will
follow
the
exact
same
rules
and
if,
if
they're
not
there,
we
would
assign
the
importer
and
put
a
note
in
there
that
it
was
not
the
importer.
It
was
this
user
potentially.
A
But
let's
take
that
one
also
into
refinement.
I
was
looking
at
it
right
now.
It's
not
in
refinement
it's
in
star,
so
it
was
already.
It
wasn't
marked
as
ready
for
refine,
but
maybe
we
can
do
a
quick
round
of
refinement
and
just
identify
a
few
smaller
things
out
of
it
that
we
could
push
forward,
and
you
know
then,
once
we
do
that.
Maybe
we'll
learn
more
about
like
what
are
some
of
the
tricks
about.
A
You
know
getting
the
full
approvers
reviewers,
all
the
things
done,
but
let's
maybe
identify
a
first
step
like
the
first
iteration.
That
will
also
help
us
learn
how
that
works.
A
Cool
one
thing
to
note:
is
that
so
we
have-
and
I
haven't-
I
don't
know
if
I've
seen
an
announcement
anywhere,
but
doug
is
sorry.
Max
wolf
is
helping
us
with
the
customer
escalations,
so
the
escalations
that
happen
through
the
channel
and
that
get
entered
like
as
customer
escalations,
we're
getting
about
two
milestones
worth
of
coverage
starting
after
next
week,
so
starting
with
the
with
a
new
milestone
and
max,
will
help
with
that.
A
So
that
should
hopefully
allow
us
to
really
focus
on
delivering
what
we
talked
about
here
versus
you
know,
being
distracted
by
by
those
escalations
and
hopefully
in
two
milestones,
we'll
have
rodrigo
on
board
and
then
we'll
have
more
coverage
for
that
type
of
stuff.
So
that
that's
that's
something
that
I
feel
is
gonna.
Allow
us
to
move
somewhat
faster
through
this
and
not
get
just
stopped
in
tracks.
If
there
is
an
escalation
and
also
doug.
A
Maybe
let's
talk
about
that
like
we,
we
kind
of
talked
to
him
about
like
here's,
your
little
world
and
you
have
to
worry
about
other
things
type
stuff.
But
let's
see
if.
A
That's
good
cola,
so
let's
see
how
we
can
when
he
comes
back
next
week,
he's
on
his
pto.
I
think
so.
When
he
comes
back
and
joins
me,
we
will
find
a
way.
I
I've
invited
him
into
our
weekly
as
well,
and
we
can
discuss
that
and
see
sort
of
how
we
can
make
each
other's
world
more
observable.
A
Even
if
they're
not
completely
merged
together
and
doug
is
also
helping
with
the
av
with
the
vmware
escalation.
So
if
he
was
involved
in
some
of
the
original
stuff,
there
would
have
been
casio
if
there's
more
there's,
it's
still
not
done
like
they're
still
testing
something
and
they
find
something
and
something's
off.
A
There's
always
a
little
bit
of
noise
from
that
and
there's
a
potential
that
there's
another
something
big
that
we
need
to
do,
but
that's
really
just
being
handled
that
should
be
handled
by
doug
and
I
feel,
like
michelle's,
also
involved
a
lot
in
that.
A
G
I
think
there's
a
lot
of
back
and
forth
between
vmware
and
gitlab
at
this
point,
so
I
think
they're
testing
it
now
and
then
we'll
report
the
results
back
to
us.
Then
we
might
need
to
fix
something
again
hand
it
over
to
them.
So
we'll
see.
A
Cool
awesome
planning,
I
I
think
we
really
got
on
top
of
a
lot
of
stuff,
so
thank
you
all
for
a
lot
for
all
of
your
hard
work
feels
like
we're
really
getting
on
top
of
things
now.
G
Oh
just
one
thing:
maybe
you
want
to
stop
the
recording,
I
don't
know
might
not.
I
don't
think
it's
confidential,
but
anyway,
just
in
case.
A
So
let
me
stop
the
recording
then
well
for
all
of
you.
Listen
to
the
recording.
This
is
all
that
that
was
part
of
the
plan.
Thank
you
very
much.