►
From YouTube: Release Group Product & UX Sync • 2022-02-24
Description
Daniel Fosco (Senior Product Designer) and Chris Balane (Senior Product Manager) discuss the current and upcoming work for the Release stage.
Agenda (internal): https://docs.google.com/document/d/1Enn_E0guWmRBpi_sl_0Kw0p7K8QQNF6SbXliGvMwvxI/edit#heading=h.3mopkvc0fgpx
A
Hello,
everyone-
this
is
daniel
fusco,
I'm
the
senior
product
designer
on
the
release
group
and
I'm
here
with
chris
balani
who's,
our
senior
product
manager
for
the
release
group
as
well.
This
is
the
release
product
and
ux
weekly
today,
we'll
go
over
a
walkthrough
of
all
the
new
updates
for
the
environments,
page
that
we
have
in
production
and
a
few
other
updates
and
our
upcoming
ux
work.
So
I'll
start
by
sharing
my
screen
chris,
let
me
know
once
you
can
see
it:
it's
good!
Here's
our
agenda,
so.
B
A
Let's
start
with
the
with
the
good
stuff
right,
we
finally
managed
to
merge
all
the
changes
to
the
environments
page
and
really
really
managed
to
nail
what
we
wanted
to,
at
least
in
my
opinion,
as
a
designer
in
terms
of
of
how
we
wanted
this
page
to
look
like
so
I'll,
show
you
the
before
and
after,
but
essentially
right
now
we
have
folders
that
expand
into
environments
and
then,
if
the
environments
have
have
deployments,
the
two
latest
deployments
show
whatever
the
status
they
have.
It
shows
what
was
the
latest
deployed.
A
It
shows
you,
the
deployment
id
the
commit
id
that
you
can
also
copy
how
long
it
happened,
the
the
latest,
sorry,
the
latest,
commit
in
the
in
the
deployment
with
a
link
to
it,
and
you
can
also
see
some
additional
details
here,
like
the
job.
This
one
came
from
the
api,
so
that's
why
it
says
that,
but
who
triggered
it
the
job
and
the
branch
or
tag
behind
that
that
deployment
so
yeah?
What
are
your
thoughts,
chris?
That
does
it
meet
your
expectations?
What
you
had
in
mind.
B
Yeah,
it
definitely
does.
It
looks
really
good.
We've
solved
a
lot
of
the
problems,
as
daniel
pointed
out
that
I
I
think
we
had
with
the
the
old
version
sort
of
just
layout
information
being
cut
off
all
the
things
that
all
the
key
pieces
of
information,
that
a
platform
engineer
or
maybe
even
even
a
release
engineer-
might
want
to
to
look
at
at
a
glance
in
terms
of
what's
been
deployed
to
their
environments.
B
So
yeah
really
really
excited
about
this.
Thank
you,
daniel
for
really
being
the
one
to
drive
this
one,
because
a
lot
of
it
was
really
the
ui
and
user
experience
and
kind
of
the
information.
That's
that's
contained
here.
So
thank
you
for
that.
A
Yeah
thanks
for
saying
that
I'm
really
happy
how
how
our
research
efforts
to
really
understand
what
were
the
key
problems
on
the
page
resulted
in
this,
and
this
is
just
the
first
iteration.
But
the
idea
here
was
really
to
make
sure
that
the
page
could
be
scalable
both
in
terms
of
how
much
information
it
can
hold.
So
we
could
render
10
deployments
here,
like
the
10
latest,
instead
of
the
two
latest.
If
we
wanted
to
right
just.
B
A
A
Yeah,
so
this
was
the
the
previous
version
that
we
had
right
with
the
table
and
you
can
see
there
that
there
were.
I,
like
some
of
most
of
the
pieces
of
information
were
here
as
well,
so
you
had
the
commit
name,
the
commit
id,
the
branch,
the
job,
but
most
of
it
was
clipped.
You
had
some
some
problems
and
you
just
couldn't
add
more
stuff
to
it
right
because
everything
was
crunched
together
in
one
table
row.
So
we're
happy
that
we
can
keep
keep
expanding.
A
This
just
keep
improving
this
on
the
next
iterations
and
it's
nice
that
we
already
got
customer
feedback
to
do
one
one
quick
iteration.
So
that
is
my
next
point
chris.
Unless
you
have
any
less
comments
here,
I.
B
Know
that's
great,
I
think
I
think
this
isn't.
This
is
a
great.
This
is
a
great
first
mvc
or
first
version
in
iteration
of
this
and
then
yeah
looking
forward
to
the
feedback
looking
forward
to
having
having
our
delivery
team,
maybe
start
to
use
this
and
also
give
us
some
feedback
which
would
be
great
and
and
iterating.
B
A
And
yeah
one
last
thing
that
is
a
little
bit
of
a
design
is
flex,
but
I'm
super
happy
that
we
took
the
effort
to
make
this
responsive.
So
you
know
no
matter
how
small
your
screen
is
and
and
some
users
have
like
11
inch
desktops.
So
this
is
pretty
much
a
reality
that
is
needed
for
some
of
them.
It
really
collapses
everything
into
a
way
that
it's
still
readable
and
still
usable.
A
So
I'm
happy
that
me
and
andrew
different
engineer
that
that
developed
this
really
really
worked
on
the
details
to
nail
the
the
smaller
screens
as
well,
so
happy
about
that.
But
yeah.
Let
me
close
this
one,
so
the
the
feedback
that
we
got
from
from
a
customer
was
that
the
new
design
looks
good
and
better
than
the
old
one,
but
it
removed
the
ability
to
view
the
status
of
all
environments
all
at
once
right-
and
that
was
someone
expected
from
us-
and
you
can
clearly
see
here.
A
A
I
left
a
proposal
to
add,
add
a
drop
down
on
the
top
of
the
tape,
with
a
few
check
boxes,
keep
folders
open,
keep
environments
open
or
keep
environment
details
open,
and
so
you
can
mix
and
match
whichever
ones
you
prefer.
This
could
be
saved
either
in
a
backend
flag
or
in
a
browser
cookie,
but
essentially
what
it
should
do
is
once
you
reload
the
page,
it
will
keep
the
ui
stay
consistent
right.
A
So,
if
you
opened,
like
all
environments,
will
be
open,
if
you
chose
them
to
be
open,
all
details
will
be
open
if
you
chose
them
to
be
open
as
well.
So
if
you
prefer
to
just
not
having
to
open
folders
and
all
that,
you
would
be
able
to
do
that.
So
that's
that's.
First,
I
added
next
up
label,
so
you
can
pick
it
up
on
further
further
milestones.
B
Yeah,
I'm
just
reading
the
feedback.
Thank
you
daniel
for
picking
up
on
that
on
the
on
the
customer's
comment.
That's
that's
excellent
and-
and
I
appreciate
the
quick
feedback
also
from
that
customer.
So
thank
you
yeah
and
sounds
good
yeah.
I
wonder
I
need
to
expand
all
environments
to
see
the
status
right
right.
I
think
it
sounds
like
the
pain
point
is
needing
to
expand
it
yeah
either
every
single
time
or
maybe
on
load.
So
we'll
yeah
sounds
good.
A
A
B
A
Daniel
thank
you
yeah
you're,
welcome!
That's
it
for
this
one
and
then
for
for
for
other
stuff
that
moved
forward
a
little
bit.
I
I
adjusted
our
our
deployment
block
ui
to
the
environment,
detail
page,
so
we
can
quickly
go
over
here.
This
is
the
current
design
and
production
of
the
environment.
Detail
page
there,
it's
not
as
problematic
as
the
main
environments.
Page.
Everything
on
the
table
is
really
readable.
Except
for
these
items.
These
actions
here
the
icons,
are
very
confusing,
like
these
are
different
icons.
A
A
lot
of
people
don't
see
that
we've
received
that
feedback
before
and
this
deployed
too,
but
not
very,
very
clear,
either
so
yeah.
The
idea
here,
for
the
mvc
at
least,
is
essentially
to
you
know,
implement
the
deployment
blocks
here.
So
it
looks
pretty
much
the
same
as
the
environments
page.
The
only
difference
is
there,
there's
no
nesting,
because
there
are
no
folders
here,
it's
just
a
flat
list
of
of
deployments
and
then
expand
expand
the
buttons
that
we
have.
We
had
on
the
original
one.
A
So
add
the
labels
to
it,
and
that's
it
right
like
this-
is
just
expanding
the
button
labels
to
make
them
a
little
bit
more
clear.
I
still
think
these
this
copy
is
not
very
clear
for
all
of
the
buttons
sure
and
then
in
that,
in
that
sense
I
have.
A
This
is
a
responsive
one
and
then
an
idea
for
the
next
iteration
right
is
to
to
rework
both
the
icons
and
the
copy
here,
essentially
to
redo
this
deploy.
This
is
the
last
latest
deployed
deployment,
so
the
action
is
all
the
same
right.
It's
just
get
this
deploy
and
run
it
again,
but
in
this
case
this
is
the
latest
one.
I
call
it
redo
this
deploy
for
all
the
previous
ones
row
back
to
this
deploy
right,
so
roll
back
this
current
environment.
A
To
this,
the
current
deploy
that
you're
looking
at
and
then
this
is
this-
is
this
move
down?
It
should
be
up
here?
This
other
button
is
is
tricky
because
they
all
do
pretty
much
the
same
thing,
but
it
is
also
a
deployment
button,
but
it's
deployed
to
any
other
any
other
environment
outside
of
this
one.
A
There
was
a
what
is
it
yeah,
a
two
tip
here,
so
so
the
the
the
two
tip
for
the
the
button
would
also
say
deployed
to
a
different
environment.
Hopefully
there
will
be
enough
to
to
make
it
clearer,
but
maybe
maybe
we
can
iterate
it
into
something
different.
I
would.
I
would
appreciate
russia's
input
on
this
one
for
the
copy,
because
it
is
possible
that
we
could
just
rethink
even
even
the
actions
themselves.
Maybe
they
could
all
have
the
same
name.
You
know
I
don't
know.
Maybe
they
could
all
be
called
re-run.
A
B
A
A
But
yeah
the
design
is
broken.
I
have
to
to
move
this
up.
I
think
this
computer
a
little
bit
as
well
yeah
and
then
the
last
the
last
change
I
made
this
was
after
our
latest
talk,
I
think,
was
updated.
The
dynamically
populated
environments
page
on
the
group
level.
So
this
is
the
empty
state
yeah
I
as
we
speak,
I
removed
the
the
the
the
product
folders
that
that
were
grouping
them,
since
this
is
a
high
level
overview.
A
Assuming
that,
specifically
users
don't
want
to
look
at
project
level,
otherwise
they
would
be
on
the
projects.
So
we're
no
longer
grouping
my
project
here,
it's
just
a
flat
list
of
deployments
for
all
production
tier
environments.
In
this
group.
Like
the
examples
gitlab.org,
you
still
have
project
information,
so
you
can
see
the
project
perhaps
even
like.
A
If
there's
another
group
in
between
you
can
see
the
group
and
the
project
but
yeah,
you
can
see
the
project
here
and
and
which
environment
you
went
to
and
this
this
is
kind
of
like
a
silly
example,
because
they
all
have
the
same
name
but
yeah.
This
is
the
environment
name,
it's
named
main.
It
could
have
any
other
name,
and
then
the
tier
is
here
as
production
right.
B
It
does
because
it
could
be
like
back-end
production
and
front-end
or
or
something
even
something
else
right,
like
yeah,
yeah,
yeah,
yeah,
environment,
a
right,
yeah,
okay,
cool
yeah.
Now
that
looks
thank
you
for
making
this
update
this.
I
think
this
makes
a
lot
more
sense
sort
of
from
the
user
standpoint.
I
think
I
think
this
looks
great.
A
Oh
yeah
and
there's
a
there's,
an
ordering
drop
down
here
that
that
I
think
first
this
this
by
definition,
is
supposed
to
be
a
large
list
because
it
aggregates
deployments
for
all
product
projects
in
the
group
right,
so
I
think
it
it
definitely
has
to
to
to
go
out
with
some
sort
of
ordering.
A
I'm
not
sure
if
these
are
the
right
parameters,
but
but
some
parameters
would
be
good
eventually
having
like
this,
this
is
the
right
setup
to
add
just
a
bunch
of
filters
to
let
people
really
narrow
down
the
list
to
whatever
they
want
to
look
at,
but
just
a
quick
way
to
reorder
this.
I
think
it's
important
just
for
the
mvc.
A
I
think
I
think
that's
good
yeah
cool
all
right,
so
I
think
the
last
thing
we
had
after
this
was
upcoming
work
right.
So
I
added
the
49
planning
issue
here.
B
Oh
sorry,
damn
one
second,
sorry
one!
I
wonder
one
thought
and
I'm
sure
this
is
probably
what
you
thought
of
already,
but
in
the
dynamically
populated
org
level
view
well,
yeah.
Okay,
I
see
the
approval
options.
Yeah!
That's
great!
I'm
sure
we'll
want
to
incorporate
that
at
some
point
too.
A
Yeah,
okay,
cool
yeah.
I
think
I
think
it
makes
sense
for
it
to
be
here
as
well.
I
I
don't
know
if
it
makes
sense
for
the
nbc,
but
but
definitely
should
be
here
at
some
point,
especially
because
this
is
one
of
like
we've
seen
this
in
customer
calls
right
people
setting
up
all
kinds
of
workarounds
to
have
the
centralized
approval
place.
So
I
think
it
makes
sense
here,
sounds
good
cool
and
yeah
in
terms
of
upcoming
work.
For
for
this
milestone.
This
first
one
is:
is
the
this
this
environment
detail?
A
I
would
say,
aside
from
feedbacks,
it's
pretty
much
closed
and
then
yeah
the
one
I
consider
the
big
one
outside
of
that
is
is
the
connection
between
releases
and
environments
right,
it's
just
breaking
down
this
issue
and
start
exploring.
Specifically,
how
can
we
show
environment
information
in
releases?
B
A
That
is,
that
is
at
least
what
I'm,
what
I
think
it's
most
exciting
for
this
milestone.
The
rest.
The
rest
is
so
exciting
in
the
sense
that
it's
improving
things
in
in
in
the
stuff
that
we're
working
on
with
with
environments
and
deployments,
and-
and
there
is
some
some
some
overlap
between
this-
this
copy
change
and
some
of
these
issues
right.
So
this
one
is
about
the
poor
wording
for
redeploying
environments,
also
on
the
on
the
confirmation
model
that
comes
up
when
you
submit
that.
B
A
A
That
there's
this
little
issue
on
environments
showing
as
stopped
even
though
the
stopping
operation
fails.
So
I
think
it's
more
of
a
front-end
and
a
little
bit
of
back-end
communication
to
make
sure
that
ui
reflects
the
back-end
state
and
yeah.
There's
some
discussion
here
that
we
scheduled
as
well
for
the
skip
outdated
deployment
jobs.
I
think
this
is
a.
This
is
an
important
one.
A
B
B
No
and
I
think
we're
right
at
time
as
well,
so
no
thank
you
thanks
daniel
yep,
great
progress.
Thank
you
for
getting
those
that
deployments
page,
making
those
updates
and
catching
that
customer
feedback
so
quickly.
So
that's
yeah,
that's
great!
It
makes
me
think
I
wonder
if
I
should
have-
or
I
should
make
a
feedback
issue
for
the
environment
pages
redesign,
so
something.
A
A
All
right,
thanks
for
the
chat
chris
and
yeah,
have
a
great
day
to
daniel.