►
From YouTube: Release Management PM/UX Weekly - Group Releases
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).
B
A
C
Finally,
I
applied
to
this
the
beginning
of
the
year,
then
because
of
corona
everything
got
canceled
or
postponed
and
it's
summer
course
in
research
and
design
methodology,
etc.
I'm
a
bit
scared
because
it's
at
the
university
level-
and
it's
been
a
couple
of
years-
let's
say
in
12
years,
I-
think
so
I'll
do
my
classroom.
What
I'm
super
excited,
because
yeah
I
learned
a
lot
day
to
day
job
but
I
really
want
to
have
fun
or
academic
experience
and
I.
B
B
A
B
So,
if
I
can
swap
out
some
of
the
work
that
we
currently
have
scheduled
for
13.3
to
be
more
focused
on
those
lenses,
I'm
happy
to
and
also
like,
if
we
want
to
pull
in
more
release,
bugs
that
are
P,
P,
2
s
and
P
threes
I
think
that's
a
great
opportunity
to
get
our
M
R
rate
up,
reduce
review
cycle
time
and
really
empower
you
to
go,
learn
and
enrich
your
experience,
not
being
worried
about.
Oh
gosh
I
got
to
do
these
things
back
here,
so
don't
want
it
really
management
being
anxiety
here.
C
B
C
So,
let's
see
I
think
I
have
the
next
couple
of
agenda
items
and
then
I
actually
want
to
share
with
you
and
also
get
some
feedback
from
everything
that
was
in
my
head
and
now
it's
on
visuals
for
group
releases
and
also
the
director
dashboard
I've
mostly
worked
on
releases.
To
be
honest,
so
brace
yourselves,
let's
see
if
I
can
tell
this
story,
I
was
watching
Jackie,
some
of
the
calls
and
some
of
them
go
back
to
January.
We
were
talking
about
the
releases
and
milestones
as
planning
and
planning
mechanism
in
releases.
C
How
to
call
this.
This
compliance,
the
audit
view
and
I
don't
have
a
lot
of
visuals
right
now,
because
I
was
trying
to
distill.
This
information
also
play
around
a
little
bit
with
the
two
workflows
that
I
want
to
validate
with
you
two
before
I
jump
into
high
fidelity
prototypes,
so
nothing
special
here,
I
think
you
can
see
my
screen
right,
yeah,
I
think
so
yeah.
C
So
this
also
helped
me
to
explain
this
information
little
bit
to
other
designers,
so
making
this
differentiation
between
releases
on
the
group
level
to
verify
what
we
delivered
right
together
with
the
time
box.
That
is
the
milestone
you
direct
me
from
wrong
yeah
because
that's
it
was
a
lot
of
information.
Yeah.
B
So,
particularly
around
time
boxes,
we're
really
dependent
on
what
plan
chooses
to
do
with
their
iteration,
so
what
they
decide
to
call
them.
So
we
need
to
think
about
how
we
can
create
some
agnosticism
of
milestone
and
iterations
and
iteration
selectors,
because
what
we
may
see
in
a
side
panel
is
that
there's
an
expansion
of
the
milestone
to
be
an
iteration,
and
we
would
want
there
to
be
enough
flexibility
to
have
releases
associate
to
all
separate
time
boxes
because
really
releases
are
a
delivery
snapshot.
B
C
The
kind
of
break
down
that
I
was
trying
to
to
do
in
the
UI,
as
in
we
can
have
a
group
release
without
having
a
group
milestone
set
right.
Then
we
talked
about
not
happy
tags
and
having
upcoming
and
expire
releases.
All
these
concepts
in
in
this
one.
This
one
this
one
workflow,
but
for
me
for
this
prototype
I,
add
ins
milestones
right
just
so
that
we
know
how
this
would
look
like
in
UI
and
try
to
capture
dependencies
with
components
with
Falls
whatever.
C
So
this
is
me
trying
to
think
what
views
we
would
have
here,
what
the
user
word
user
would
go
so
worried
click
and
what
you
do
on
the
pages.
So
I
can
translate
these
new
prototypes,
but
quickly,
I
started
with
looking
to
creating
a
group
release
from
existing
project
releases
right,
and
this
still
follows
the
the
milestone
flow.
So,
in
the
group
overview
you
land
on
the
group
review
and
then
you
navigate
to
releases
potentially
a
new
section.
C
The
group
view
new
group,
the
project
group
level
and
I
got
names,
so
in
the
group
releases
overview
you
want
to
create
a
new
release
at
the
group
level,
so
you
click
to
create
a
new
one.
You
land
on
the
form
and
then
same
old.
You
add
a
name
to
this.
New
group
release
enter
a
title
and
next
you
can
want
to
determine
the
versions.
C
B
At
the
group
level.
We
can
do
that,
but
first
MBC,
the
only
I'm
caring
about
because
this
is
what
users
have
told
us,
is
that
I
won't
be
able
to
get
my
existing
releases
as
an
application
at
the
group
level,
because
sometimes
I
could
represent
applications
or
end
user
experiences
and
projects
underneath
that
are
different
components
of
the
end
user
experience.
Yeah.
C
That's
also,
and
that's
a
line
to
deal
with
this
with
this
proposal,
because
I
started
like
reading
all
the
questions
that
we
have
in
the
contrasting
videos
and
also
like
okay.
How
would
that
even
look
in
the
UI,
because
it's
so
much
complexity
for
you
just
to
have
the
ability
to
select
either
text
like
a
video
component,
wise
right
interaction?
We
don't
have
that
I
would
have
to
yeah,
spend
more
time
creating
components
or
updating
components
for
that
so
and
I
also
had
this
questions
related
to
you.
C
C
When
you
stop
sharing
exactly
find
this
file,
when
you
create
a
group
release,
do
you
still
want
us
to
add
assets
there?
You
still
want
to
add
a
release
notes.
Do
you
want
to
add
all
the
complexity
from
the
project
release
to
the
group
release
and,
if
not,
is
this
really
a
release
or
justice?
You
know
this
package
version
with
everything
or
a
way
to
link
to
all
these
standalone
project
release
releases
in.
B
B
We
may
provide
links
to
the
project
assets
under
the
asset
links
so
that
they
can
at
least
go
to
the
releases
overview
page
another
group
and
then
click
into
the
project,
release,
assets
and
release
notes.
And
then,
as
we
do
more
validation,
we
can
iterate
to
create
the
single
group
asset.
But
that's
a
new
archetype.
You
know
like.
Are
we
going
to
allow
uploading
to
group
releases
in
my
mind?
C
B
Not
the
compliance
need
because
it
really
seven
ants
will
be
at
the
project.
Still
there
isn't
gonna
be
released.
Evidence
generated
at
the
group
level
cuz
there
again,
there's
no
code
at
the
group
level.
Yet
maybe
we
will
support
group
repositories,
I,
don't
I,
don't
know
when
and
if
that's
the
truth
or
not,
but
today
like
there
will
be
no
release
evidence
at
the
group
level
because
there
isn't
a
thing
to
do
that.
C
B
C
B
C
B
C
B
Say
that
they
want
to
select
all
the
release
run
books
for
each
of
the
sub
projects,
so
that
you
can
see
the
different
processes
and
statuses
of
the
release
sub
project
at
a
glance.
So
it's
less
about
the
source
code
and
more
about
the
surrounding
activities
of
the
release.
They're
linked
to
a
specific
project.
Okay,.
C
C
A
C
B
Would
love
it
to
be
an
auto
change
lock
from
the
project
releases,
but
there's
an
option,
maybe
that
we
add
in
a
second
iteration?
That
is
a
toggle
even
though
Marin
hates
toggles.
Maybe
it's
a
different,
a
different
configuration
option
that
says
auto
populate
from
project
release,
notes
or
create
new
group
release
notes,
because
I
could
see
a
world
where
they
use
this
auto.
They
use
this
release,
notes
to
depict
the
experience
they're
trying
to
create
for
their
end
user,
rather
than
a
description
that
I've
enabled
Mac
OS
on
my
runner
right,
yeah.
C
B
C
C
B
B
And
that
way
they
can
reconcile
at
a
glance.
I
am
10%
down
with
my
project
milestone,
and
my
group
milestone
actually
has
a
bunch
of
other
projects
in
it
and
a
30
percent
complete,
but
my
work
in
the
sub
projects
may
not
be
always
related
to
the
group
milestone.
So
we'll
need
to.
This
is
a
good
picture
to
paint
right.
I
can
show
that
I
need
to
do
additional,
wet
work
on
my
project
milestone
before
the
green
milestone
gets
done.
C
B
A
C
B
Because
releases,
when
you
aggregate
them
at
this
level,
we
can
start
weekend.
We
can
play
with
this
some
more
but
like
a
release
in
get
world
is
always
total
related.
So
first
I
have
this
like
friction
in
my
mind.
Right
now
of
setting
the
right
expectation
of
what
we're
trying
to
accomplish
with
group
releases,
I,
don't
know
it's
actually
a
release
because
there's
no
code
in
it,
it
really
is
like
a
representation
of
your
delivery.
B
B
We
have
on
Monday
Ayana
a
conversation
with
Ori
about
really
stage
three
year.
Mocks
I
could
see
this
view
that
you're
showing
me
right
now
expanding
to
include
environment,
target
environments
and
having
this
be
like
the
one-stop
place,
where
people
can
view
their
deployment,
progress
right,
yeah,
that's
a
three-year
target,
but
like
this
is
something
to
to
show
how
extensible
we
want
this
for
you
to
be,
because
it's
not
about
code.
In
this
case,
it
can't
be
because
there's
no
repository
at
the
group,
it's.
C
B
C
You
actually
enter
my
questions.
I
had
all
these
are
really
things
VR
questions
if
you
need
to
assign
a
date
or
create
milestones
from
here,
but
everything's
clear,
going
back
to
this
view,
I
added
here
tacit,
that's
just
because,
because
in
my
head
we
would
get
all
these
releases
and
then
create
one
Z
file
or
whatever,
where
you
can
download
everything
instead
of
users
having
to
go
here,
then
we.
B
B
When
I
think
of
an
action
ability
on
this
view,
Ayana
I
think
I'd.
Rather,
people
perform
their
actions
on
the
project
release
page,
so
I'd
rather
launch
them
to
the
project
view
and
then
do
their
asset
work
there
and
has
the
group
view
be
like
a
launching
place
rather
than
like
the
place
where
you
fix
assets
to
your
project
releases,
but
that's
an
assumption
based
on
there
isn't
a
such
of
an
archetype
today
in
the
get
land
of
a
release.
Bundle
yeah.
B
C
Be
worth
showing
you,
you
know,
let's
say
rumbles
whatever
you
just
have
a
selection
here,
but
I
wonder
like
if
you
need
to
not
just
sort
of
have
the
overview
data
ListView.
What
you
need
to
act
on
this
stage
going
to
each
of
the
video
project
release
to
download
this
as
I'm
just
curious,
also
to
see
how
people
know
how
much
friction
I
think.
B
This
is
the
great
validation
to
talk
with
both
Moran
and
Steve
about,
because
that
will
be
our
developer
persona.
That
would
be
the
first
teams
to
consume
this
kind
of
a
feature.
Always
I
really
don't
know
from
what
I
understand
our
customers
use
case
to
be
and
what
they
would
be
actually
doing
with
assets
today,
yeah.
B
Yeah
and
maybe
maybe
it's
actually
a
link
to
all
project
assets
and
that
opens
up
like
a
new
modal
or
a
new
page
window
or
whatever
we
whatever
our
framework,
is
here
and
it
lists
all
of
the
project
assets
rather
than
it
being
like,
and
expand
and
collapse
kind
of
experience.
Yeah
I'm
worried
about
this
page
becoming
another
endless
scroll.
Yes,
that's.
C
C
B
It
would
be
really
cool
if
we
can
get
Dennis
again
as
like
the
inner
sourcing
embedded
software
use
case,
because
he's
been
waiting
for
assets
and
uploading
assets
to
releases
for
a
long
time.
So
it
would
be
a
cool
thing
to
like
actually
engage
him
on
and
for
what
it's
worth,
I'm
loving
the
little
tab
action
you
have
up
here
on
and
expired.
That
is
very
slick.
My
friend.
C
Because,
since
we
don't
really
have
the
ability
to
filter
sort
or
anything
in
the
releases,
the
project
release
already
I
was
thinking.
Maybe
we
should
just
that,
at
least
for
now
to
give
people
with
some
flexibility,
and
then
we
talked
to
me
last
week
about
not
showing
releases
that
don'ts.
Do
you
have
how
to
call
that
upcoming
releases
right
in
this
from
this
overview
and
have
a
way
to
really
differentiate
those?
B
A
B
B
C
You
know
just
play
around
with
how
would
look
like
to
select
milestones
if
they
belong
to
a
group
or
a
project
in
the
release,
detail
view
so
you're
out
the
project
releases
edit
release
and
let's
say
that
you
want
to
promote
right.
You
also
touched
on
this
point
where
you
have
an
item
and
you
want
to
make
that
project
release
part
of
the
group
release
and
I
was
like
okay.
How
do
you
do
that?
B
Think
that
group
really
serves
arcs
fundamentally
a
different
object,
so
there
won't
really
be
a
promotion
path
when
we
look
at
it
mainly
because
the
roof
release
is
a
bucket
not
tied
to
code.
So
a
project
release
will
always
be
tied
to
code,
but
we
can
talk
about
this
more
with
the
technical
side
of
it.
Maybe
it
becomes.
Maybe
our
promotion
is
actually
a
creation
of
a
group
release
and
it
adds
the
project
tag
automatically
or
the
project
release
tag
so
like
the
action
is
promote
like
backslash,
promote
to
group
release.
B
C
So
it's
really
just
you
know,
so
she
ad
to
an
existing
group,
release
right
so
that
you
have
another
item
in
the
list
or
like
what
you
saying
create
a
new
one
so
that
you
can
now
add
other
purchases.
Then,
when
I
was
looking
at
the
Association
through
milestones,
I'm
like
this
doesn't
make
sense,
because
what
if
there
is
already
a
project
milestone,
then
how
is
that
gonna
work
with
the
you
know,
selecting
from
this
view
so
I
tried
also
which
I
liked
yeah.
B
B
And
this
we
can
dive
into
this.
What
I
mean
by
that
different
in
different
folks
know?
There
were
at
time
right
now,
but
when
I
think
about
this
object,
it's
not
like
it's
not
a
release.
You
know
it
just
doesn't
have
the
same
properties,
it's
a
completely
different
object.
That
means
something
different
different
to
a
release.
Manager
right
like
this
is
visibility
as
an
umbrella.
So
it's
to
look
into
and
to
be
aggregator
for
the
project
deployments
right,
I.