►
From YouTube: Plan stage weekly meeting - 2019-09-11
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
So
I'll
share
my
screen,
so
yesterday
we
finally
had
drag
and
drop
ready.
It
is
currently
in
UX
review
and
hopefully
the
code
review
will
finish
my
end
of
this
week,
so
we'll
have
it
merged
into
master
by
next
week
early.
So
these
are
the
changes
that
we
made.
If
you
recall
last
time,
we
had
three
tabs
here
we
had
discussions
shown
by
default
on
page
load
and
we
had
three
and
one
F
tabs,
so
we
had
three
tabs
at
the
bottom
of
the
page.
C
So
after
receiving
the
feedback,
when
we
enabled
the
dragon
to
github.com
and
the
other
changes
that
we
did
around
all
the
tree
looks
and
the
behavior.
These
are.
The
changes
like
B
now
called
the
three
tab.
Epics
and
issues
and
roadmap
is
next
to
it,
and
content
itself
is
part
of
the
description
area
of
the
epic,
so
user
wouldn't
have
to
switch
to
a
different
tab
just
to
see
what
are
the
attached
issues
and
epics
present
for
the
given
epoch
and
let's
go
straight
to
drag
and
drop
now.
C
C
You
would
see
that
the
cursor
shows
that
it
is
not
allowed
and
the
things
do
not
move
around,
which
means
that
it
can
only
be
reordered
within
the
issues
list
and
I
can
basically
leave
it
anywhere
and
it
gets
reordered,
see
anything
happens
to
that
fix
like
I,
can
reorder
epochs
within
itself,
but
the
moment
I
get
into
the
issues
or
editor.
It
shows
the
cursor.
Not
if
we
have
one
of
the
epics
expanded.
C
The
items
within
the
subtree
of
the
epoch
remain
confined
to
itself.
So,
for
example,
if
I
try
to
reorder
this
and
try
to
somehow
grab
it
outside
the
parent,
it
is
not
allowed
because
we
do
not
allow
changing
parents
of
individual
items
using
drag-and-drop,
at
least
for
now.
So
issues
can
be
reordered
within
its
own
subtree,
but
they
they
cannot
be
moved
outside
the
sub
or
any
item
from
the
outside
cannot
be
moved
inside.
C
So
that's
there
and
if
you
try
to
move
an
entire
expanded
epoch,
then
it
would
grab
everything
along
and
then
you
can
move
that
entire
thing
into
the
list.
So
you
can
see
that
all
the
children
items
move
along
with
it
and
can
be
placed
anywhere
and
the
moment
you
reorder.
So,
let's
see
how
basically
the
order
is
reserved.
C
C
What
we
do
plan
to
do
in
the
next
release
is
basically
at
least
allow
intersperse
reorder.
What
that
means
is
that
you
should
be
able
to
move
issues
into
the
epics
list
and
Abby
is
in
between
two
epics,
so
basically
interchanging
of
items
will
be
allowed,
hopefully
in
12.4,
but
as
far
as
changing
parent-child
relationships
are
concerned.
That
is
still
something
that
we
are
evaluating,
but
because
it
is
tricky
from
both
front
and
back
in
perspective
and
updating
the
team
call
as
always
or
depending
on
what
we
decide.
C
C
Oh,
you
exchanges
that
we
have
done
and
if
there
are
any
significant
changes
proposed
by
several
team
members,
then
we
will
come
back
to
the
design
and
see
how
it
can
be
improved
and
if
it
is
received
well,
then
we'll
basically
remove
the
piece
and
animal
it
for
everyone.
So
any
questions
or
suggestions
so
far.
A
C
C
So
the
way
we
are
doing
it
right
now
is
that
if
you
open
any
issue,
you
can
basically
look
at
the
sidebar,
and
it
will
help
this
epic
item
where
you
can
click
on
edit
and
basically
it
will
show
all
the
eligible
epics
that
you
can
select
and
update
the
parent
for
this
earlier.
It
was
not
that
straightforward
I
mean
only
way
you
could
do
that
early
on
is
to
either
copy
the
URL
of
the
issue
itself
or
visit
the
epic
page
and
then
paste
in
the
URL
there
and
add
it.
C
C
So
only
way
right
now
to
update
the
parent
for
any
given
epoch
is
to
basically
first
visit
the
parent
epoch
itself
like,
for
example,
if
I
want
to
move
this
front
end
roadmap
2020
inside
the
accessibility
roadmap,
then
I
would
have
to
first
open
the
accessible
civility
roadmap.
Go
back
to
this
particular
racket
copy.
The
link
address
come
back
here,
click
on
add
an
epoch
and
then
paste
in
the
URL
and
then
click
on
add
and
that
that
is
the
only
way
where
you
can
change
the
pattern
for
any
given
epoch.
C
Obviously,
this
is
not
a
very
good
experience,
so
we
want
to
be
able
to
show
a
drop
down
in
some
way
in
the
sidebar.
So,
as
you
can
see,
only
way
that
we
can
do
currently
is
my
integrating
drop
down
within
the
ancestors.
So
Alexis
and
I
had
a
brief
discussion
on
how
to
title
this.
Am
I
updating
the
ancestors
qi
last
week
and
we
have
an
issue
as
well.
D
A
D
It's
just
the
draw
awareness
to
this,
like
we
have
this
kind
of
plan
at
the
minute
to
kind
of
try
and
find
areas,
the
application
that
we
can
tighten
up
from
a
performance
point
of
view,
but
it's
not
necessarily
just
technical
work.
It's
not
necessarily
just
like
n
plus
1
queries,
but
could
be
parts
of
the
application
and
the
way
it's
design
that
would
allow
people
to
take
advantage
or
be
like
noisy
neighbors,
an
example
might
be
in
service
desk.
D
You
know
it
may
be
possible
to
like
enumerates
email
addresses
and
then
spam
spam
I
think
it's
issues
with
comments.
So
we
want
to
find
these
kind
of
things
and
close
them
down,
and
so
that's
why?
If
I
paste
in
that
link
to
the
two
epics
one
for
portfolio
management
and
one
for
certified
but
they're
quite
light
at
the
minute,
there's
not
a
whole
lot
in
the
backlog,
so
I
just
want
to
make
people
aware
of
it
and
and
kind
of.
D
E
Security
issues:
there
is
a
message
from
security
team
about
like
only
focusing
on
some
critical
vulnerabilities
for
this
release.
I
was
just
wondering
if
we
want
to
I,
don't
know
continue.
Working
I
I
know
that
you're
moved
a
lot
of
the
security
issues
into
twelve
three,
so
I
think
there
is
a
week
left
in
this
I
was
wondering
if
you
want
to
kind
of
move
those
issues
over
to
the
next
release,
or
just
continue
to
roll
with
them,
and
those
will
probably
get
into
next
security
release.
Oh
yeah,
just
kind
of
attention
to
them.
A
E
E
A
F
Yeah,
it's
totally
I
mean
we're
having
our
kickoff
call
for
12
for
on
the
18th,
so
I
think
the
code
freeze
is
on
the
17th
I
believe,
but
just
so
we're
not
rushing
I
guess
like
if
you
can
get
security
issues
through
the
review
process
and
verification
process
by
the
17th.
Then
please
include
them,
but
for
like
major
features
and
stuff.
F
If
it's,
if
they're
not
done
by
this
Friday
or
at
least
in
like
review
verification,
probably
gonna,
be
like
go
get
through
those
stages
within
the
next
few
days
that
I'm
just
gonna
go
ahead
and
bump
them
to
twelve
four.
So
we're
not
having
to
do
a
bunch
of
like
last-minute
things
for
the
release
posts,
but
yeah
feature
free
or
code
freezes.
Seventeen
kickoff
for
twelve
for
is
eighteenth
and
feature
development
should
like,
if
you
want
to
get
it
into
twelve
three,
get
it
in
review
by
the
end
of
this
week
at
the
latest.
A
Yeah,
so
the
security
and
John,
maybe
you're
a
little
bit
more
familiar
with
the
security
releases,
but
it
goes
by
a
little
bit
of
a
different
schedule
and
our
normal
release.
So
I
think
we
may
have
a
couple
extra
days
to
get
security
fixes
in
might
be
on
the
17th,
but
then
I'm
not
sure,
because
we
have
the
backfill
a
bunch
of
like
we're,
not
just
getting
it
into
the
12
3
release.
We
also
will
need
to
back
board
a
lot
of
them
in
previous
releases.
A
So,
on
the
front
end
I
think
there's
only
I
think
we
only
have
two
security
security
fixes
and
those
who
are
both
scheduled
for
12:00
3:00.
So
for
those
two
I
think
we'll
keep
in
twelve
three
I
know
there
are
a
bunch
of
back-end
issues
that
were
moved
up.
We
should
just
look
at
each
of
them
and
see
if
we
still
need
to
prioritize
getting
them
done
before
any
of
our
other
stuff.
E
Firm
up,
like
my
understanding,
was
that
in
twelve
three,
the
security
team,
like
will
not
accept
and
in
you
fixes
so
to
say
other
than
some
critical
vulnerabilities
that
they
want
to
push
push
out
and
release
so
yeah.
At
least
that
was
my
understanding
from
the
message,
but
if
not
then
you're
fine.