►
From YouTube: Release Management PM/UX Weekly - 2020-06-08
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
A
B
And
then
we
say
that
is
this
one
here
that
I
want
to
schedule:
14
13.2,
it's
a
small
change
as
well
to
remove
a
doubling
a
double
button
in
the
environments
page
when
there
is
no
environments
out
of
there,
an
empty
state,
so
yeah,
just
kind
of
heads-up
and
also
to
align
with
what
we
are.
What
we
want
to
do
with
our
UX
that
issues
I
just
want
to
bring
more
visualization
to
that.
B
C
Thanks
Hannah
for
bringing
this
up,
so
we
haven't
been
discussing
this
before
that
I'm
just
gonna
give
a
quick,
intro
so
Jackie.
This
is
something
that
we
actively
discussing
in
the
verify
and
early
stage
groups
right
now,
we're
actually
like
almost
well
almost
in
agreement
with
all
PMS
in
verifying
the
release.
C
So
the
idea
here,
I'm,
not
sure
if
you
have
been
coming
across
the
video
that
Marcel
have
created
a
few
weeks
ago
around
the
experience
with
our
merge
request
with
how
like
well
confusing
and
kind
of
like
spread
across
information,
is
when
you
are
working
with
the
widgets
in
the
merge
request.
Like
the
you
know.
C
Sometimes
it
shows
you:
okay
yeah,
you
do
a
little
change
and
then
it
shows
you
like
you
have
introduced
like
I,
don't
know
hundreds
of
for
abused
and
you
know
really
well,
it
seems
it
seems
confusing
and
seems
to
show
not
the
truth,
information
etc.
So
there
was
a
big
okie
are
a
sat
around
are
specifically
for
that
they've
create
stage
group,
but
we
have
since
verifying
who
least
age
groups
are
so
so
closely
connected
and
so
strongly
affecting
the
user.
Experience
of
merge
requests
widgets.
C
So
in
this
issue
that
hi
Anna
placed
here,
we
have
collected
a
list
of
recommendations
that
are
existing
today.
Divided
power
stage
group.
Well
thank
God
in
our
case
for
the
release,
management
was
only
three
I,
think
hi
Anna
or
for
so
that's
like
the
least
active
stage
group
with
the
recommendations,
and
so
our
proposal
was
in
order
to
support
it.
Okay,
our
from
that
tough,
create
stage
groups.
We
wanted
to
have
a
conversation
with
the
product
management
in
recent
verify
and
see
what
of
those
recommendations.
C
C
There
are
really
good
improvements
in
the
table
so
like
the
goal
before
13th
of
June.
That's
like
the
last
final
date.
What
we
are
agreeing
on
the
next
milestone
scope.
We
want
to
have
an
indication
for
engineering
like
hey.
This
is
one
of
what
we
want
to
address
a
four
days
OPR
and
like
kind
of
like
aligned
with
that
on
that
with
engineering
before
the
start
of
the
next
week
like
this
is
our
contribution
and
I
was
thinking.
C
A
C
We
could
mark
like
one
two
three
I
know.
However,
you
will
want
to
prioritize
for
water.
To
that
we
say:
hey
we
contribute
like
this
is
our
little
contribution
to
this
OPR
because
later
at
the
end
of
well
actually
in
the
beginning
of
next
week,
because
this
Friday's
family
and
friends
day
I
will
be
like
making
a
little
report
and
we'll
be
reporting
on
that
you're
deaf
create
to
Christy
and
everyone
who's
involved
like
hey.
C
This
is
all
of
the
contributions
that
we
plan
to
do
in
quarter
two
from
the
release
and
verify,
and
so
that
would
be
like
if
you
could
put
like
a
little
mark
there
like
a
yes
for
a
Teague,
the
for
the
items
that
you
have
selected.
That
would
be
really
equal
and
for
me
that
would
be
an
indication
hey.
C
A
B
B
Yeah
this
one
Jackie,
let's
mention
of
red
team,
invited
us
to
a
state
to
discuss
the
DC
wax
OPR,
to
propose
three
improvements
for
first-time
experience
and
identify
ten
others
for
experiment.
Backlog
I'm
not
super
into
context,
but
I
saw
that
Mario
was
active
in
the
issue.
They
were,
maybe
not
ain't
know
what's
going
on,
but
I
just
wanna
like
leave
a
heads
up
and
also
ask
what's
going
on
here
and
how
can
can
we
contribute
I?
Think.
D
Think
about
what
you
want
to
define
it
out
and
give
her
three
examples
and
and
walk
through
those
three
examples.
Using
her
real
board,
that's
the
best
I
can
tell
yeah
I,
think
she's,
trying
again
like
that.
Okay
are
to
to
get
things
done
and
to
thought
this
would
be
a
good
way
to
do
it
across
a
class
stage
for
us,
so
can't
go
wrong.
I!
Think
if
you
just
least
and
provide
her
what
your
definition
is.
First
time
then
she'll
have
someone
context
of
why
you
provided
those
those
three
things
you.
D
A
Yeah
I
mean
I
know
we
have
a
lot
of
a
lot
of
things
that
we're
doing
from
the
UX
side.
One
like
this
whole.
How
do
we
enable
cross
stage?
Think
big
conversations
like
that's
taking
a
lot
of
time,
and
then
we
also
have
this,
mr
investment,
in
release
that
we're
trying
to
do.
On
top
of
you
know
the
vision
stuff
that
we're
trying
to
craft
and
your
normal
workload.
A
So
we
should
evaluate
the
okay
yards
that
you
have
and
kind
of
think
through,
like
which
ones
do
we
really
want
to
drive
forward
in
q2?
This
doesn't
seem
to
fit
with
our
priorities,
though
so
I
would
strongly
suggest
as
saying
we're
not
even
going
to
participate
in
providing
first-time
user
experiences.
This
quarter
it'll
be
a
q3
thing
because
we're
so
invested
in
creating
cross
stage
now.
B
That's
it's
next
Monday,
then
yeah.
You
can
join.
A
B
Also
gonna
be
recorded.
Then,
let's
see
what's
going
to
commodities
quickly.
Next
item,
just
a
question
actually
for
next
steps
for
CIA
director
dashboard.
So
we
identified
and
read
like
the
components
table
I
think
now.
We
still
need
from
tenderest
to
see
how
components
are
structured
and
what
we
can
reuse
and
what
we
can
and
I
just
wanted
to
also
give
a
heads
up
has.
B
A
So
we
talked
with
John
Mason
before
about
the
generic
Analytics
report
and
all
that
stuff.
The
biggest
risk
that
we
run
into
there
is
a.
We
aren't
delivering
the
value
that
our
CI
CD
customers
are
looking
for,
which
is
a
group
aggregation
of
release,
information
and
CI
minutes.
So
that's
kind
of
why,
on
the
issues
that
we
have
created
them,
I'm
asking
you:
are
we
okay
to
implement
the
raw
gitlab,
UI
charts
and
those
kinds
of
things,
because
we
can
then
partner
who
their
teams
on
delivering?
A
You
know
the
pajama
implementation
of
the
get
lab,
UI
components
they
still
don't
have
like
the
scope
inside
those
issues,
don't
have
like
aggregation
of
metrics
and
I.
Don't
know
how
long
it's
gonna
take
them
to
deliver
that,
but
we
definitely
need
in
order
to
compete
with
ZB
labs,
like
value
stream
metrics
about
releases
and
we
have
to.
A
We
have
to
deliver
hill
near
Andorra,
so
that
people
feel
like
we're
able
to
actually
measure
deployment,
because
today
we
use
environments
as
a
proxy
for
deployment,
but
there's
nothing
measurable
about
deployments
in
get
lab
and
that's
a
problem,
because
people
aren't
going
to
be
able
to
see
the
value
of
deploying
with
get
lab
if
they
don't
have
those
metrics
in
front
of
them.
So
we
this
is
kind
of
like
an
ROI
exercise.
A
B
I'm,
getting
none
that
make
sense.
I
just
wanted
to
rock
the
races
because
yeah,
but
was
really
no.
We
out
of
context
from
their
discussion
and
I
just
wanted
to
kind
of
get
a
sense
that
our
we're
not
building
to
similar
things
in
two
different
stage
groups
from
what
I
understood
from
them.
Also
they
want
to
have
the
flexibility
to
just
generate
dashboard
or
some
data
points
from
the
CI
file.
So,
yes,
they
have
a
different
complexity,
but
it
was
interesting
to
see
that
this
could
be
something
that
that
is
an
overlap.
B
B
I
have
one
open
merger
plans
to
accept
issue
and
is
going
to
highlight
that
we
had
tweet
merge,
request
plan
for
this
past
summer.
We
actually
delivered
four,
so
that
was
super
cool
and
then
for
this
week.
Maybe
we
can-
or
maybe
you
already
have
an
idea
Jackie
just
to
align
the
priorities
because
I'm
looking
at
the
network's
issue
and
I
just
gonna
follow
the
order
there
and
an
x1
is
support
when
you
Association
to
go
to
milestones,
but
then
yeah
there's
anything
else
is
more
important.
Just
doesn't
know.
That's.