►
From YouTube: Iteration: Release Management - UX/FE sync on Share production environments across projects
Description
Rayana and Nathan review UX proposals for the MVC https://gitlab.com/groups/gitlab-org/-/epics/4276
A
B
So
I
want
to
review
together
the
issue
24.56.
I
think
you
have
it
open
there,
but
I'm
going
to
sit
in
here.
Anyways
yep,
which
is
a
group
group
environments,
group
production.
B
I'm
not
sure
exactly
how
we're
calling
this
and
I
updated
the
acceptance
criteria.
Let
me
also
open
here
and
share
for
just
for
the
sake
of
this
recording
based
on
our
latest
discussion.
B
So
yeah
this
is
about
it:
dynamically
population,
populating
the
group
environments,
page
with
production
environments,
and
I
saw
some
of
your
questions
nathan
and
let
me
just
go
down
here
quickly
because
I
think
it's
nice
to
start
with
these
pieces
about
what
are
we
showing
and
how
we
are
grouping
these
things.
B
So
your
question
was:
why
are
we
interested
in
showing
on
production
environments
right
now,
and
I
reply
here
that,
because
for
the
mbc
just
production,
we
had
a,
I
think
we
had
a
discussion
where
we
would
say
yeah.
We
show
also
the
review
environments
at
this
page,
but
then,
as
far
as
I
understood,
it's
just
production.
C
B
I
think
it's
a
little
bit
of
vote.
Okay,
I
think
for
the
sexy
mbc
production,
so
we
can
deliver.
Maybe
a
small
thing
that
we
can
iterate
on
yeah.
C
B
Also,
when
looking
at,
let's
say
the
release
and
what
they're
interested
in
seeing
and
validating
right
now,
it's
really
the
production
environment
right,
of
course,.
C
B
You
have
the
review
apps
and
then
the
review
environments
and
the
docs,
but
I
think
production
is
really
the
start.
Yeah.
C
C
A
B
C
B
Cool
and
then
I
looked
into
your
comment
here
about
how
we
are
grouping
them
or
how
we
would
group
these
environments,
and
I
think
my
understanding
and
that's
I
have
a
question
for
you
there.
My
understanding
is
that
we're
gonna
get
the
url
right,
the
dynamic
url
or
these
environments.
We
say:
okay,
if
they
all
share,
I
don't
know
something:
dot.
Gitlab.Com
they're
gonna
show
in
that
one
group,
regardless,
if
it's
and
and
also
if
it's
in
under
production
right,
there's
two
filters.
There.
C
Yeah,
so
that
that
was
just
a
suggestion.
That's
not
currently
part
of
it
and
my
thought
with
that
is
that
people
might,
I
don't
know
if
people
are
already
using
this
url
for
things
and
they
wouldn't
want
to
actually
group
by
it,
and
if
so,
I
was
saying
we
could
add
another
key,
for
example,
group
to
add
a
grouping
mechanism,
but
I
don't
think
we
should
go
that
route.
C
To
begin
with,
I
think
just
grouping
by
url
makes
sense
to
me,
especially
for
the
nbc,
so
I
I
think
just
doing
that
is
a
good
first
step.
C
B
Something
else
in
the
group,
because
when
I
was
first
working
on
the
mvc,
this
is
at
the
epic
level
right
and
then
I
put
in.
A
B
Examples
so
we
have
project
one
that
could
be,
for
example,
pajamas
and
projects
ui,
and
they
both
have
the
same
url.
Let's
say
whatever.
C
B
C
I
forgot
that
you
can
build
the
url
dynamically
with
variables
we
might
need
to
get
in
touch
with
the
back
end
person
to
see
how
that
would
work
to
see
if
those
would
actually
be
grouped
together
or
if
those
would
just
be
considered
different,
because.
A
A
C
B
B
C
B
And
I
think
we
can
follow
the
same
pattern
that
we
have
now
like
20
items
and
then
paginate,
since
if
we
only
do
production,
but
if
we
do
production
plus,
then
maybe
we
can
just
reuse
the
current
pattern
from
the
from
the
environment
page
and
go
back
here
where
you
have
like
a
little
more.
C
C
B
Which
I
think,
if
we
go
only
with
production,
I
don't
think
we
should
use
the
show
all
I
think
we
should
be
just
like.
You
know
everything
that
is
under
production
or
gitlab,
but
if
we,
if
we
make
more
complex,
I
think
we're
gonna
have
to
either
use
this
pattern
or
re-evaluate
the
whole
thing,
because
it's
not
gonna.
A
C
B
B
B
Okay,
so
this
is
the
flow
for
the
acceptance
criteria
right
for
what
I
detail
here.
So
in
the
group
level,
we're
going
to
add
a
side
menu
item
for
operations.
B
B
C
B
And
then,
if
you
have
nothing,
let's
say
you
don't
really
have
any
production.
So
it's
an
empty
state.
We're
going
to
need
an
illustration
here,
so
I
think
we
can
just
the
first
pass.
We
go
without
an
illustration,
just
static
text
and
then
I
open
an
issue
in
the
bitlab
design,
because
this
needs
approval
and
it
might
take
a
while.
B
C
Yeah,
we
could
even
include
some
in
that
page.
You
could
say:
group
environments
are
like
include
more
instructions
in
there,
so
that
they
wouldn't
have
to
necessarily
jump
to
the
documentation
like
environments
that
our
production,
our
production
environments,
will
come
here
automatically
and
are
grouped
by
url
or
something
just
like
a
little
some
little
snippet
to
help
them.
A
C
C
B
B
Awesome,
so
if
you
don't
have
anything
empty
state,
if
you
do
have
some
items,
we
pre-populate
with
with
this
data
so
that'll
on
this
page.
Let
me
go
step
by
step,
live
data
description,
so
everything
is
grouped
under
production.
So
we
show
the
title
production
here
and
a
counter
of
how
many
environments
there
are.
C
B
Order
in
production,
it's
kind
of
like
a
static
so
right
now,
if
I
go
back
to
the
environments
view
here
right,
so
instead
of
showing
just
this
information,
we
show
the
project
where
I
don't
know,
release
comes
from.
A
B
The
only
extra
thing
here
is
the
project
detail,
which
is
the
avatar
the
name,
so
you
click
you
go
to
the
to
the
project
overview
and
all
the
other
things
are
the
same
so
deployment
you
hover
here.
You
have
information,
you
can
click
and
go
to
the
commit
details
and
also
you
can
see
each
individual
deployment.
B
You
can
also
click
the
I
and
see
the
detail
of
that
deployment,
which
would
be
a
page
like
this
and
also,
if
you
don't
have
deployments
it's
the
same
same
thing
as
today.
We
have
today
just
no
deployments
yet
any
paginates
and
the
only
I
think
the
big
thing
here
is
that,
because
everything
deploys
to
a
single
url,
then
we
have
this
button
here
for
view
deployment,
and
I
just
added
the
url
so
that
users
know
that
hey.
This
is
actually
where
it's
going
to
be
displayed.
C
C
C
B
Yeah
I
was
a
bit
like.
Okay.
Do
we
need
to
add
more
contacts
here?
You
know
explain.
What's
going
on
for
first
time,
users.
C
B
And
at
this
point
you
cannot
really
do
anything
other
than
seeing
the
deployments
and
seeing
the
details
of
the
environment,
but
I
think
once
we
have
like
the
ability
to
create
group
environments
at
this
level
or
you
know,
stop
deployment
roll
back
things
just
be
work
or
release
we're
going
to
shape
this
view
to
be
something
yeah.
C
C
B
Yeah
we
have
an
issue
for
that:
jackie
open
just
a
placeholder
so
that
we
start
to
start
discussing.
A
B
B
So
don't
bother
even
looking
at
the
current
one,
but
then.
A
C
B
C
B
C
C
C
One
there
we're
kind
of
consistent
with
that
one,
so
maybe
people
will
kind
of
know.
That's
the
button
to
jump
to
the
actual
environment.
A
C
A
C
B
Yeah
this
is,
I
think
this
is
from
the
new
pack,
the
new
icon
pack.
B
B
B
C
A
C
So
overall,
this
looks
super
good
to
me.
I
do
a
couple
minor
questions
when
you
say
production
here.
Where
does
this
name
come
from
because
right
now.
A
C
C
Yeah,
the
only
thing
is
that,
if
we're
my
understanding
is
that
we're
filtering
by
production,
so
everything
on
this
page
kind
of
by
definition
will
have
production
yeah
as
its
name
and
then
there
might
be
some
that
have
different
urls.
So
we
don't
want
to
group
those,
so
that
would
mean
like
basically
everything
would
be
named
production.
B
C
B
And
then,
maybe
later,
if
we
say
that
yeah
we
are
organizing
this
by
both
environment,
name
and
url.
If
you
want
to
filter
that
to
have
this.
C
And
do
you
like
the
like
in
the
in
the
gitlab
yaml?
It's
it
has
a
protocol
such
as
https.
We
can
definitely
chop
that
off
for
display
purposes
like
that,
if
you'd
like
that,
otherwise
we
can
also
just
spin
it
in
there,
as
is
whichever
you
think,.
B
Let's
leave
it
on
the
under
the
boy
button
because
later
on,
if
you
want
to
expand
and
have
like
the
expansion.
C
C
Let's
see
if
the
other
very
minor
comment,
I
don't
know
if
we're
going
to
use
graphql
for
this
page,
which
I
don't
know
if
we've
decided
yet,
but
if
so,
we
probably
won't
be
able
to
use
this
style
pagination
similar
to
the
discussion
we
have
about
the
releases
page
you'll
probably
just
need
to
be
previous
next.
B
Awesome,
oh
and
another
thing
I
put
in
the
acceptance
criteria
that
we
would
use
a
table
component
just
because
we
have
titles
headers
for
business,
okay,
but
yeah,
I'm
not
sure
how
ready
the
component
is.
C
B
Because
everything
that
we
ship
now
it
needs
to
be
pajamas
ready.
So
if
you
say
that
yeah
this
we're
gonna
need
to.
A
C
C
B
And
if
it's
not
responsive,
we
can
just
open
an
issue
later
and
then
in
the
second
phase,
because
I
think
the
only
thing
that
would
make
this
table
a
bit
more
smart
is
that
things
need
to
be
ordered
by
and
last
updated.
That's
it
other
than
that.
It's
pretty.
B
C
C
C
B
C
B
Let's
not
go
there,
okay,
because
if
you
say
that
you
know
since
it's
auto-populated
anyways
and
it's
always
just
like
an
appointment
in
the
project
level
where
things
are
ordered,
you
know
by
yeah,
less
updated.
C
C
C
A
B
C
B
I
would
suggest
maybe
for
the
future,
let's
say
that
he
under
gitlab
docs,
you
have
multiple.
Let's
say
that
not
bitcoin
box,
but
one
of
these
is
a
review
right.
I
mean
review
dot
gitlab.com,
for
example,
and
then
you
have
a
cell
right.
Whatever
you
have
something
here
and
you
have
graduation
right.
A
B
A
B
B
C
Yeah,
so
I
think
that's
what
I
was
my
guess
is
that
patent
nation
actually
won't
be
a
huge
issue
in
this
case,
because,
if
we're
only
showing
a
production
environment
like
we're,
pretty
heavily
filtering
this
down,
so
I
can't
imagine
people
would
have
30
different
projects
that
all
are
considered
production
under
the
same
url,
so
I
we
could
probably
even
get
by
without
doing
any
pagination
to
start
and
then
add
in
pagination,
once
we
kind
of
figure
out
how
how
and
where
to
add
it.
C
I
think
that's
why
that
the
current
environments
page
has
that
kind
of
weird
showmore
system
is
because
we're
kind
of
showing
two
levels
yeah
of
things
here,
and
so
it's
not
clear
which
level
we're
paginating
against
and
I
think
it
in
the
environments
page
it
patches
against
the
top
level
so
review.
The
review.
Folder
is
one
and
then
the
next
folder
is
another
item,
so
we're
actually
paging
through
those.
B
B
Now
is
that
in
the
future,
if
you're
a
release
manager-
and
you
want
to
have
the
ability
to
not
just
a
low
back
or
redeploy
or
stop
these
environments,
but
you
also
have
approvals
so
not
showing
like
the
at
a
glance
like
environments
or
products
or
deployments
that
are
pending.
Approval
would
be
kind
of
weird,
but
I
think
you
can
solve
some
of
these
problems
later
on
with
the
filtering
sorting.
C
C
B
C
B
B
B
Because
I
think
also
it
would
be
nice
to
have
a
plan,
or
at
least
have
a
proposal.
We
can
test
this
against
some
users
of
you
know
if
we
had,
if
you're
going
to
support
more
different
different
environments,
but
then
it
would
be
weird
to
just
apply
this
to
the
group
level
view.
Maybe
we
can
already
talk.
A
C
C
A
B
Oh
and
one
thing,
another
thing
is
thinking
the
loading
of
this
page.
C
B
We
use
the
one
that,
from
this
view,.
C
B
We
I'd
rather
just
use
the
one
we
have
now
to
not
create
more.
You
expect
I
I
still
have
to
tackle
the
one
for
the
release
page
and.
C
B
Yeah,
I
think
that
was
a
recent
update
and
also
I've
seen
other
teams
using
different
skeleton
loaders.
They
are
also
using
it
for
graphs
and.
B
I've
seen
some
design
proposals
there,
but
it's
not
very
consistent
from
where
we're
using
them.
A
B
Awesome
cool
awesome,
I'm
gonna,
I'm
making
the
updates
to
the
tradition
description,
but
I
think
the
current
prototypes
are
ready
to
be
posted.
There.
B
C
B
On
jackie's
initial
proposal-
or
this
one
I
mean
her
initial
proposal
was
just
about
populating
the
page,
but
then
we
are.
We
are
grouping
these
environments
because
we
want
to
provide
the
users
with
our
customers
with
the
url
so
that
they
can
show
to
their
end
users
right
or
the
marketing
or
whatever.
This
is
the
url,
the
production
url
for
gitlab.
Everything
is
into
this
one
thing,
but.
B
C
C
C
C
C
I
feel
like,
since
our
last
meeting
we
decided-
I
know
maybe
shawn
can
confirm,
but
I
feel
like.
I
think
we
decided
not
to
restructure
how
things
are
associated
as
he
was
proposing,
and
instead
just
kind
of
use
these
existing
structure
and
just
make
things
visible
on
that
page.
So
those
that
diagram
might
not
be
relevant
anymore.
B
C
C
C
That's
awesome,
yeah.
The
one
thing
we
should
follow
up
with
john
about
is
a
dynamic
url
when
it's,
what
has
a
variable
in
it,
how
we're
gonna
handle
that
and
how
we're
gonna,
if
we
group
in
that
case,
do
you
want
me
to
ask
about
that
or
do
you
wanna
follow
up.
C
B
So
next
steps
for
me
I'll,
publish
this
to
the
issue
and
then
I'll
check
with
configure
if
they're
doing
the
operations
menu.
I
know.
C
B
B
C
Interesting
so
they're
they're
really
adjusting
it
at
the
at
the
project
level.
B
Yeah-
and
you
can
also
see
this
one
where
they
immediately
talks
about
having
a
releases
menu
with
the
for
the
project
right.
B
But
in
microsoft
I'm
I'm
putting
everything
under
operations.
So
let
me
actually
share
with
you
here,
because
I'm
working
on
the
three-year
prototypes
for
releases
and.
C
B
B
B
Yeah,
but
for
now
we're
just
gonna
have
environments
or
group
environments.
A
A
Thank
you
so
much
nathan,
I'm
gonna,
push
the
prototype
and
I'll
leave
a
comment.