►
From YouTube: Release Management Frontend/Backend Sync - 1
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
B
B
Think
it's
this
article
actually
but
yeah.
Okay,
well,
I
started
thinking
about
it
again
because
there's
an
issue
floating
around
at
the
moment
about
whether
I
think
it's
probably
getting
a
bit
late,
but
whether
a
third
endpoint
know
we
should
have
a
version
5
of
the
API
instead
of
current
version
4.
Of
course
it
would
be
possible,
but
I
think
obviously
the
don't
like
the
video
if
we're
going
to,
because
it's
a
but
yeah
it's
a
broken
change.
A
A
A
B
C
B
C
Alright,
we're
here
for
our
front-end
back-end
priority
sync
for
release
management.
It
is
our
first
one,
so
Nicole,
what's
going
to
kick
off
with
you
thanks.
A
So
the
first
item
I
had
here
was
prioritization
when
an
issue
requires
get
lab
UI
contribution,
so
the
the
issue
I
have
linked
here
is
an
item.
That's
in
ready
for
dev,
but
the
get
lab
UI
component
is
incomplete,
so
Jake
had
suggested
a
worker
out
there,
but
it
looks
like
we
don't
even
have
designs
for
what
that
get.
Lab
UI
component
should
look
like
so
I
think
for
the
most
part,
the
priority,
in
my
opinion,
would
be
we.
If
we
have
a
feature
that
requires
a
new
component.
A
C
The
product
standpoint:
it's
ready
for
development,
because
the
spec
is
there,
you
we
have
like
a
problem
solved
and
that
they
could
implement
the
solution.
That's
available
today,
which
is
not
the
pajamas
approved
standard
right,
but
it
solves
the
problem
of
being
able
to
sort
their
releases
on
that
page.
C
I
completely
agree
that
we
can
create
an
issue,
that's
all
about
building
the
component
and
stage
that
one
to
be
a
release,
p1
and
deliver
that
work
first
and
then
a
minute
for
the
releases
page
I
think
that's
that's
a
complete
engineering
decision
and
the
only
part
that
needs
to
happen
for
me
is
just
slapping
their
release.
P1
label
on
it,
and
being
aware
that
we
won't
be
able
to
present
the
release
pages
sorting
as
a
release
post
item
until
that
issue
has
been
delivered.
C
So
it's
ready
for
development
because
it
meets
our
criteria,
which
are
has
a
way.
Has
a
preliminary
spec
on
it
enough
to
build
something?
And
there
is
discussion
between
back-end
and
front-end,
which
was
the
three
criteria
for
to
be
moved
into
ready
for
development
but
yeah
as
first
breaking
it
down.
That
can
be
engineering
completely
in
isolation
really.
A
C
So
since
it's
big
five
engineering
can
say
you
know,
we'd
rather
break
this
down
into
two
issues,
one
about
the
component
and
then
the
component
for
pyjamas.
We
need
to
go
through
the
full
lifecycle,
so
that
would
put
this
issue
still
and
ready
for
development,
because
the
spec
is
there,
but
we
had
update
the
description
to
say
it
needs
to.
C
This
problem
can
be
solved
in
two
different
ways:
the
pyjamas
process
or
building
or
really
implementing
the
current
get
lab
UI
solution
as
a
work,
great
okay,
so
from
a
product
standpoint,
I'm,
agnostic,
I,
want
the
problem
is,
could
be
solved
either
way.
But
your
decision
as
an
engineering
team,
to
tell
me
that
it's
gonna
be
more
efficient
for
us
to
build
this
as
a
component
and
then
that
new
issue
will
go
through
planning
breakdown
and
design,
which
will
then
block
this
issue
essentially
from
being
delivered
so
that.
A
So
yeah,
absolutely
if
that
makes
total
sense.
That
was
my
thoughts
on
it
as
well.
If
this
one
predates
me,
I
just
wanted
to
use
it
as
an
example,
but
had
hadn't
I've
seen
that
earlier,
that
would
have
been.
My
suggestion
is
to
get
a
component
issue
created
and
in
front
of
it
just
from
an
efficiency
standpoint.
I
guess
my
question
here
in
terms
of
like,
since
that
wasn't
done,
for
this
particular
issue.
Is
there
any
priority
around
this
issue
that
would
cause
us
to
say
in
efficiency?
A
C
So,
typically,
if
the
item
is
in
the
backlog,
still
it's
not
committed
got
it
so
I'm
only
going
to
put
things
in
a
milestone
if
I
feel
pretty
certain
about
the
size
and
what
we've
already
discussed
about.
But
for
this
one
it
has
a
backlog,
because
it's
a
nice-to-have
feature
yeah.
It
will
be
a
beautification
option,
but
it's
not
if
it's
not
in
a
milestone.
That's
not
a
release!
P1
that
I'm
counting
on
us
like
being
committed
to
to
move
my
direction
forward
from
a
product
business
standpoint.
B
So
yes
and
I
asked
this
question
in
evaluating
recently,
so
pyjamas
is
an
in-progress
project
and
the
idea
is
that,
eventually
we
will
have
all
these
components.
Yeah
I
think
I
compared
it
to
bootstrap.
In
the
last.
They
will
have
all
these
components
that
can
just
kind
of
plug
and
play
that
with
it's.
It's
definitely
working
for,
like
it's,
not
really
many
of
the
paths
that
we
see
on
good
lab
now
accustomed
for
they
page
only
and
they're,
not
pajama
components,
quick
statement.
A
Yeah
and
my
my
understanding
also
is
that
pajamas
is
more
of
the
design
guidelines
like
Google
material
or
what
have
you
and
that
they
get
lag.
Ui
is
the
actual
implementation
of
that
guideline
into
a
component.
So
so
there's,
actually
you
have
to
have
the
pajamas
piece
to
implement
the
gate
lab
UI
component.
So
there's
a
few
steps
there
and
in
this
case,
in
this
issue,
we
were
discussing
I,
don't
even
think
there's
a
design
for
the
component.
A
C
Yeah
and
for
some
of
these
more
UX
driven
conversations,
rather
than
like
API
driven
conversations,
I'm
a
little
bit
more
accommodating
to
Ayanna.
So
she
gets
to
advise
me
on
priority,
which
is
interesting
and
I
know
other
product
managers
don't
really
gel
that
way,
but
I
feel
like
she
has
the
voice
of
the
customers.
C
Experience
in
her
mind
and
she's
the
one
that
gets
to
tell
me
when
things
things
are
ready,
so
typically
she'll
raise
her
hand
and
move
it
into
ready
for
development
if
she
feels
like
something
can
be
implemented
without
without
something
without
a
full
design,
and
in
this
one
it's
still
currently
in
her
epic
for
review,
because
we're
kind
of
thinking
through
the
exact
same
thing,
between
having
a
Potamus
design
and
then
you
get
lab
UI
component
being
implemented.
That
way.
C
B
A
Okay,
I'm
sorry,
just
a
couple
more
and
use
mine
I'll
be
quick,
and
so
we
talked
about
or
started
to
talk
about
the
opportunity
for
converting
Hamel
to
view
I.
Guess
I
just
want
to
raise
this
as
wherever
we
have
Hamel
views
and
because
my
understanding
is,
the
approach
has
been
if
it's
a
new
UI
we're
just
gonna
write
it
in
view.
If
it's
an
old
UI,
that's
where
you
you
know
we're
doing
Hamel
right
now,
but
there's
an
opportunity
there.
So
if
we
have
those
I
I
was
using
pages.
B
A
B
B
C
Our
build
board
for
these
candidates
I
can
then
make
sure
that
we're
prioritizing
those
mixes
appropriately.
So
maybe
we
can
stack
rank
some
of
these
technical
debt
items
that
either
have
front-end
or
technical
debt
with
UX
like
higher
up
like
that.
I
am
open
to
to
creating
a
new
label,
but
also
leveraging
the
technical
debt
combination
of
tech,
debt
plus
front-end.
We
just
need
a
scrub.
The
scrubs
are
billboard
for
those
label
said
perfect,
so.
B
That
actually
leads
into
a
great
point,
so
so
we
can
just
create
labels
I'd
like,
and
so,
if
we
do
that
they
like
this.
This
is
a
good
example
like
would
we
want
to
court?
We
would
want
to
coordinate
with
other
develop
engineering
groups
that
we've
created
a
new
label
or
the
weekly
and
label
specifically
for
ourselves.
So.
C
We're
in
the
get
lab
project
you
can
create
a
label
in
the
get
lab
project
or
get
lab
group
for
other
people
to
use
so,
for
example,
Ori
and
I
created
the
release
P
one
two
and
three
labels,
and
then
other
teams
wanted
to
start
using
those
labels.
So
we
ended
up
elevating
yeah,
so
they
started
using
their
own
package
p12,
and
so
what
they
wanted,
though,
to
do
is
to
be
able
to
like
use
that
across
all
of
the
projects
and
they
get
lab
group.
B
C
B
But
but
you
know
say:
we
currently
have
an
API
right
and
then
we
have
we're
public
API,
and
then
we
have
this
kind
of
undocumented
API
and
then,
when
our
use
graphical
for
the
front-end
stuff
and
I've
actually
discussed
this
a
couple
times
with
with
Nathan
and
it's
there
seems
to
be
there's
not
a
lot
of
you
know
all
the
front-end
developers
just
know
you
just
use
these
various.
You
can
use
any
three
of
those
you
know
hitting
on
those
three
and
just
you
know
it's
more.
A
high-level
decision.
B
B
You
know
for
for
our
engineers
ourselves
it's
a
bit
of
a
big
segue
from
that
and
issue,
but
it's
really
because
everything
goes
all
the
views
too
close
to
the
API
right,
whereas
the
ham
will
go
strictly
against
the
controllers,
but
yeah
and
possibly
possibly
is
where
it
came
from
right,
because
you
know
they
probably
just
free
purposes.
Then
controllers
to
start
observing
the
view
stuff,
I.
A
Agree
with
that
and
and
I
think
it's
something
that
I'll
definitely
look
into
it's
something
that
wasn't
even
on
my
radar.
So
thanks
for
raising
that
and
I
think
we
should
have
some
discussion
or
a
bit
I.
Don't.
B
A
C
B
C
Need
to
figure
out
like
if
we
want
to
fix
a
whole
new
Hamel
label
here,
so
that
we
can
drive
visibility
or
if
we
want
to
leverage
again
technical
and
UI
components.
I
feel
like
either
of
those
might
be
appropriate
as
existing
labels.
So
I'll.
Let
you
all
think
about
that,
and
we
can
start
implementing
that
into
billboard
and
then
I
agree
around
documentation
for
both
I
just
googled
our
issues
and
it
sounds
like
we've
implemented
some
documentation
and
12.4,
but
the
documentation
is
still
pretty
sparse.
So
I'm.
C
B
B
A
A
B
B
C
B
B
B
C
B
C
Again
they
have
this
thing
called
span,
which
is
about
cross
stage,
users
and
namespaces.
So
that's.
The
second
part
is
making
sure
that
we
increase
stages
per
active
namespace.
So
I'll
link
these
issues
here,
but
I
think
what
you
and
I
talked
about
could
be
the
three
that
we
like
stack
hands
on
internally,
and
you
know
for
us
us
us
aligned
here
to
make
sure
that
we
move
forward.
B
C
Of
get
lab,
and
then
we
should
focus
on
developing
our
teammates,
so
making
sure
that
we
have
scope
that
will
stretch
them
and
challenge
them,
and
you
have
those
conversations
with
them.
Yeah
and
that
should
be
r2.
I
know
that
your
your
managers
are
going
to
encourage
you
to
be
ambitious,
but
if
we're
focused
on
too
many
things-
and
we
won't
be
delivering
quality
are.
B
B
C
Yeah,
so
this
is
gonna,
take
a
lot
longer
than
I
expected.
We'll
probably
have
a
separate
meeting
or
we'll
dedicate
our
time
in
our
next
meeting.
But
what
I
wanted
to
do
was
walk
through
the
billboard
with
you
all
and
start
identifying
the
filters
by
which
we
want
to
start
prioritizing
things
like
technical
debt
like
bugs,
because
I
feel
pretty
alone
in
this,
and
as
a
project
manager,
I
don't
like
to
ever
feel
alone.
I
want
to
have
as
many
voices
as
possible
that
I
have
to
reconcile
and
enmesh
to
form
what
our
priority
is.
C
Work
we're
delivering
some
high-priority
bugs,
but
our
backlog
of
bugs
is
still
pretty
high
and
I
would
say
high,
it's
probably
relative
term,
because
I've
definitely
had
products
that
were
ten
years
old
that
had
a
thousand
bugs
that
were
ugly
as
sin
right.
But
these
bags
are
are
still
accumulating
and,
as
we
ran
our
offering
any
of
these
hiccups
that
our
customers
hit
will
reduce,
will
create
friction
and
will
cause
our
customers
not
to
want
to
use
our
solution.
So
I
want
to
exactly.
C
B
Yeah,
because
I
would
I
would
love
to
do
that,
because
I'm
still
learning
about
how
to
build
board
works.
You
know
as
an
engineer,
you'd,
it's
pretty
simple
right.
You
just
get
the
next
item,
but
there's
obviously
a
lot
more
to
it
that
yeah
and
in
a
step
bank.
What?
How
does
that
work?
Was
it
all
say?
Oh.
C
C
B
B
B
C
B
A
C
I'll
share
both
of
these.
These
are
like
the
users
and
the
usage
metrics
that
I
care
about,
but
then
from
like
a
work-in-progress
and
Mars
and
Sean
I
know.
I
talked
your
ear
off
about
this
before,
but
I
think
that
we
need
to
get
a
good
healthy
baseline
before
we
Charlie
really
hammering
on
our
team
to
deliver
ten
Mrs.
The
fact
that
we've
added
a
new
teammate,
the
fact
that
they've
changed
manager
several
times
on
both
the
front
and
in
the
back
inside.
B
C
A
That's
awesome,
and
that
is
why
I
wanted
to
bring
up
the
Oh
cares
because
I
actually
had
an
OK
art
for
maintaining
our
mr
rate
versus
increasing,
just
because
of
all
the
above
items
that
you
mentioned.
So
it
would
be
fantastic
for
Shawn
and
I
to
be
aligned
there
right.
It
doesn't
make
sense
for
us
to
have
to
I
think.
B
My
main
tithing
is
a
good
starting
point.
Absolutely
also
we'd,
like
is
a
reason
it's
WIP
group,
or
was
it
just
I
think
I
mentioned
this
earlier.
So
if
we
want
someone,
some
changes
made
on
this
and
I
can
see
who
you
know
and
do
it,
but
these
a
there's,
a
group
that
should
be
doing
it
for
us
or
an
issue
for
them.
We.
B
C
B
A
C
Then
this
last
one
I
just
have
this
filter
linked
here.
This
is
just
front-end
back
in
issues
that
are
in
progress,
so
pretty
much
I'm,
looking
at
the
in
dev
and
in
review
columns
and
just
wanted
to
check
in
see
if
there's
anything
that
you
guys
are
hearing
or
you
all
are
hearing
from
the
team
and
if
there's
anything
that
we
need
to
to
clean
up
I
think
there
might
be
extra
consideration
Nicole
for
the
ready
for
development
column.
C
Now
that
we
have
you
on
the
team
and
you're
like
a
little
bit
more
up
to
speed
that
if
we
can
go
through
with
like
a
fine-tooth
comb
that
yes
keep
your
drugs
issues
have
the
right
design
and
if
they
have
a
front-end
label
on
them
and
all
that
jazz
I
feel
like
we
should
evaluate
our
criteria
and
feel
actually
comfortable.
Pinging
me
on
and
be
like
Jackie
I.
Don't
this
is
ready.
It
needs
to
go
back
to
scheduling
or
each
to
the
box
planning
breakdown
and
then
her
name
yeah.
C
B
C
I
think
for
me,
I've
really
only
picked
PP
ones
and
p2s
into
the
ready
for
development
column,
but
we
have
like
p3
is
that
are
hanging
out
there
that
are
more
like
beautification
M
ours.
So
if,
for
example,
we
get
blocked
on
a
front
end
piece,
I
wanted
to
have
scope
for
someone
like
me,
thinner
or
Jake
to
pick
up
something.
B
B
B
C
B
B
C
A
B
C
It's
taking
time
from
us,
but
it's
gonna
be
so
nice
a
year
from
now
when
we
need
to
add
a
milestone
to
a
different
layer
like
say
that
we
expand
this
whole
run
books
feature,
and
now
we
want
to
be
able
to
associate
a
particular
run
book
to
a
milestone.
We're
gonna
be
able
to
use
that
same
damn
thing,
and
so
what
if
it
took
us
two
milestones
to
do,
we
won't
have
to
redo
that
word
for
another
month,
like
you
know
exactly.
B
B
A
B
B
And
so
maybe
I'm
just
I'm
thinking,
perhaps
we
might
choose,
maybe
the
second
I
would
say
just
do
one
week
right
and
maybe
if
we
would
do
the
second
week
because
well
I'm
open
to
wish
everyone
would
be.
But
I
guess
the
face
where
he's
decided
to
talk
about
in
the
last
week
is
the
end
of
the
cycle.
So
they
kind
of
significant
weeks
or
what's
your
opinion
on
which
one
it
should
be
or
do
we
just
kind
of
do
I
think.