►
From YouTube: Group Releases Prototype Review #1
A
Alrighty,
so
we
have
this
issue
right
here,
I'm
chatting
it
to
you
and
it's
about
associating
group
milestones
to
a
particular
release.
So
in
the
gitlab
use
case
we
obviously
use
a
group
milestone
as
a
part
of
our
monthly
release
cadence
and
today,
it's
very
challenging
to
orchestrate
and
plan
across
all
these
different
projects.
A
If
you
can't
use
the
same
sort
of
milestone
if
you're
using
milestones
for
planning,
so
the
gist
of
this
issue
is
to
hi
hi
anna
is
to
allow
us
to
connect
that
planning
at
the
group
level
across
all
the
projects
for
their
releases
and
now
that
hayan
is
here.
I
can
cut
it
over
here,
but
that's
just
the
context.
Any
questions
or
thoughts
on
that
immediately.
C
B
C
You
can
click
that,
let's
see
if
it
starts
in
the
right
page,
my
first
time
doing
that
so,
let's
see
all
right
cool.
So
this
prototype
is
interactive.
Just
to
give
you
some
context,
but
you
cannot
click
on
everything
and
I'm
gonna
ask
a
couple
of
questions.
So,
if
you
can
yeah
just
answer
it
out
loud
as
you
navigate
yeah,
the
first
question
is:
where
would
you
go
to
create
this
group
level?
Really?
Is
a
group
level
version
for
this
group.
B
Either
under
it,
where
the
milestones
are
so
I
don't
remember
where
the
my
songs
are
by
hearts.
To
be
honest,
but
probably
I
would
like
to
see
it
like
a
sidebar
here
like
like,
I
really
don't
remember
where
the
milestones
are,
but
probably
either
under
issues
or
like
epics,
where
I
can
have
like.
Okay,
this
is
the
milestone
and
the
milestone
has
this
release.
So
under
the
milestone
information,
I
would
see
the
release
associated
with
it.
B
Since
the
releases
associated
to
milestone
right
since,
like
like,
for
example,
gitlab
uses
milestones
to
plan
a
release,
I
would
expect
that
a
release
in
the
milestone
are
pretty
much
the
same
thing
from
a
changelog
point
of
view
or
from
a
deployment
point
of
view.
So
the
release
should
have
the
issues
related
to
it.
Also,
the
milestone
should
have
the
issues
related
to
it,
and
the
release
on
the
milestone
are
like
one-to-one
relationship
right.
B
B
B
C
B
Yeah
so
milestone,
I
expected
to
give
me
the
list
of
the
open
milestones,
probably
even
the
close
milestone.
If
I
want
to
create
the
previous
release
that
we
already
done,
I
would
not
expect
to
see
the
release
note.
So
if
it's
an
upcoming
milestone,
probably
the
release
notes
are
still
not
are
still
not
final
right,
so
things
can
change,
so
maybe
that
would
be
done.
This
would
only
either
pop
up
or
give
me
the
option
to
add
it.
When
I
choose
a
milestone,
that's
already
closed.
B
C
B
Okay,
so
select
releases,
aha,
okay,
so
these
are
the
releases
that
are
inside
of
the
project
already,
so
there
are
there's
already
a
release
existing
for
that
project
so
for
the
gitlab
project,
there's
about
these
releases
and
for
the
pajama
designs.
There's
these
releases
okay,
so
I
suspecting
so
this
group
might
just
create
from
is
basically
grouping
multiple
releases
into
one
release.
Okay,
now
I
get
it
so
yeah
just
create
firm,
makes
a
lot
of
sense
now,
so
I
expect
to,
for
example,
yeah
and
then
the
milestones
so
go
ahead.
B
B
Can
can
seem
strange,
but
I
like
that
we
have
a
create
new
one.
So
if,
if
it's
an
upcoming
thing
and
the
my
song
does
not
exist,
I
can
create
one.
That's
I
quite
like
that
and
the
manage
milestone
links
as
well,
because
it's
always
nice
to
quickly
link
to
those
stuff
and
then
yeah.
I
I
like
that
it's
actually
split
up,
because
sometimes
we
have
everything
in
one
list
and
it's
not
very
obvious
which
one
is
group
levels
and
which
one
is
project
level.
A
B
Okay,
so
you're
saying
and
okay
in
a
scenario
where
the
runner
does
not
follow
13.3,
for
example,
it
follows
1.5
right
right,
yeah.
That
makes
sense
because,
like
there's
a
lot
of
projects
that
does
this
and
gitlab
like,
for
example,
workhorse
getaway
and
things
like
that,
they
have
their
own
pro
specific
milestones.
B
C
B
B
Yeah
so
I
like
that,
I
can
split
between
the
expired
while
they're
expired,
I'm
not
too
sure
what
expired
means.
Does
that
mean
previous
releases,
or
does
that
mean
something
else,
because
then
I
would
expect
if
it's
expired,
meaning
that
the
releases
have
already
happened.
That
would
mean
that
I
would
see
two
here
because.
C
B
B
B
Test
five
stone
and
first
milestone:
this
is
the
list
of
milestones,
I'm
not
guessing.
So
these
are
the
milestones,
and
these
are
the
releases,
maybe
naming
something
here
releases,
because
we
already
specify
milestones
here
so
might
be.
Maybe
it's
just
me
like
being
explicit
at
what
these
are
like.
A
A
C
B
B
B
A
B
B
So
theoretically,
we
already
have
seven
releases
upcoming
for
me,
as
a
user
like,
for
example,
2.2
got
released
right
now,
I
would
have
to
scroll
down
to
actually
find
3.2
without
so
I
would
say
the
default
view
would
be
the
ones
that
are
released
and
then,
if
I'm
actually
interested
in
the
upcoming,
I
will
look
at
the
upcoming.
So
that's
one
one
improvement
I
can
think
of,
and
can
you
repeat
the
question
again?
Please.
B
So
yeah
the
current
milestones,
I
would
say
a
way
to
look
at
what
the
issues
are.
So
probably
it
depends
on
how
we,
the
person,
generates
the
changes
like
right
if
it's
fire
issues
or
biometrics
or
a
combination
of
both
but
an
easy
way
to
look
at
what
actually
changed,
might
would
be
the
number
one
priority.
So.
B
Look
finding
a
button.
Okay,
I
can
click
on
it
and
I'll
get
an
aggregated
list
of
the
changes.
For
example,
I
do
so
I'm
guessing.
This
is
because
it's
still
not
closed
the
milestone
itself,
but
since
it's
already
hundred
percent
complete,
I
don't
really
need
to
see
this,
but
I'm
not
sure
what
the
difference
between
group
release,
1.3
and
1.2
is.
B
If
it's
just
because
of
the
date,
I'm
confused,
why
it
is
not
is
not
marked
as
an
upcoming
milestone,
since
the
milestone
is
not
closed,
so
I
expect
it
to
be
upcoming
unless
there's
a
difference
between
an
upcoming
release
and
a
still
open
milestone.
I
do
not
know
because
it
does
not
it
does.
It
seems
strange
that
I
have
a
milestone
and
in
the
middle
of
the
milestone,
I
have
a
release
attached
to
it.
So
does
that
mean
that
a
maestro
can
have
multiple
releases
group
releases?
Sorry.
B
I
I
I
guess
it
depends
how
you
like
it's
just
how
I
viewed
group
milestones
from
my
point
of
view.
It's
like
a
milestone
is
something
that
everyone
released
at
the
same
time,
meaning
that
like,
for
example,
let's
say:
okay,
people
can
release
at
different
times.
For
example,
the
runner
releases
two
days
before
gitlab,
but
for
me
that's
still
an
upcoming
release,
because
13.2
has
still
not
finished
yet
until
boy,
both
kittler
brunner,
getty,
lee
workhorse
and
all
that
tagged
the
tags.
B
And
then
we
say
okay,
this
releases
public
now
so
everyone
has
can
download
it
right.
So
sub
projects
can
release
earlier,
like
probably
what
group
release
1.3
did.
But
for
me
it's
still
an
upcoming
release
because,
like
for
example,
it's
still
not
packaged
as
one
release
right.
That's
how
I
think
of
it,
but
I'm
pretty
sure
there
are
others
and
use
cases
where
it
is
completely
valid.
Use
case.
A
So
I'm
wondering,
if
there's
if
a
badge
like
current
release
would
be
useful
and
maybe
that's
what's
pinned
at
the
top
as
if
it's
the
current
one,
although
if
there's
multiple
concurrent
releases,
that
could
be
that
can
compete
for
the
top
real
estate,
but
a
different
badging.
Do
you
think
that
would
help
kind
of
differentiate
for
you.
B
B
B
A
B
A
Yeah,
so
one
thing
that
we
were
thinking
about
here
is
this
idea
of
source
code
being
displayed
at
the
group
level.
Given
that
there
isn't
a
repository
at
the
group,
we
would
need
to
take
all
of
the
assets
that
are
inside
of
each
of
these
group
or
each
of
these
projects
and
display
them
here.
Would
that
be
a
natural
experience
for
you,
or
would
you
rather
just
consume
the
assets
on
the
project
release.
B
I
would
expect
like
a
I'm,
not
sure
where
we
have
this,
but
I
think
we
have
it
in
the
job
page
where
we
have
like
a
download
button,
and
it
gives
me
a
list
of
artifacts
to
download.
So
probably
I
would
expect
a
button
here
like
a
download
button
and
it
when
I
click
on
it.
It
will
pop
up
and
give
me
the
list
of
assets,
but
I
would
not
expect
a
whole
list
of
assets.
For
example,
I
don't
know
the
runner
team
provides
like
30
assets
per
release
and
like
seeing
30
assets.
C
C
C
B
A
But
you
don't
get
to
see
the
cross
group
progress
or
cross
project
progress
in
gitlab.org,
because
you
can't
plan
at
that
group
milestone
level
with
each
individual
release.
So
this
gives
you
the
opportunity
to
see
your
plan
versus
delivery
if
you're
using
milestones,
but
there's
also
the
use
case
of
customers
not
using
milestones,
and
they
want
to
be
able
to
aggregate
cross
project
releases.
A
So
they
have
a
single
place
to
go
to
create
their
bundle,
because
when
we
think
about
a
microservice
project,
for
example,
they
have
one
production
instance
that
16
different
projects
are
feeding
into
that
customer
end.
Experience
comes
out
on
the
30th
of
august,
but
every
other
team
is
going
to
be
delivering
their
pieces
in
succession
prior
to
the
30th
of
august.
So
they
want
to
aggregate
that
in
progress,
release
and
pull
it
into
this
view,
so
that
they
can
track
and
triage
and
see
everything
at
that
level,
regardless,
if
they're,
using
a
milestone
for
planning.
B
And
the
stairway
for
like,
for
example,
if
I'm
using
this
feature,
is
there
a
way
for
me
to
attach
an
asset
to
a
group
milestone
so
imagine
in
gitlab's
case
right.
It
provides
a
package
for
all
the
projects
specified
into
one
like
workhorse
pages
and
like,
for
example,
github
itself
right
they're
all
into
a
rpm
package
that
the
user
can
download
like.
Can
I
can
I
view
that
somehow
in
the
group
release
or
do
I
have
to
go
into
the
get
so.
A
That's
exactly
what
the
question
was
like.
Would
you
expect
to
see
the
assets
from
each
of
the
projects
on
this
view,
because
today,
like
we,
don't
have
that
provided
here?
That
will
be
an
action
that
you
go
into
each
of
the
projects
to
view
there
won't
be
like
an
upload
of
assets
to
the
group
release
in
this
current
world,
and
that's
mainly
because
there's
no
repository
at
the.
B
B
B
C
B
Yeah
I
I
like
the
idea
of
like
having
a
way
to
show
like
the
main
assets.
For
example,
I
see
that
imagine
multiple
microservice
buses,
but
then
you
provide
one
way
to
download
everything
as
one
binary
right,
so
just
providing
me
a
way
to
choose
an
asset
but
like
not
all
of
them
at
once
by
default,
because
that
would
be
way
too
overwhelming,
but
like
allowing
you
allowing
the
creator
of
group
releases
to
specify
which
assets
to
show
that
would
be.
That
would
be
beneficial
for
sure.
C
You
can
navigate
to
the
left
left,
I
think
yeah.
This
was
a
previous
prototype
as
well,
where
you
had
in
this.
This
is
just
a
screenshot.
This
part
here
just
a
screenshot
of
the
current
releases
view,
but
the
idea
was
that
you
could
either
add
new
assets
or
select
assets
from
existing
project
releases
should
be
displayed
at
the
programs
level.
B
A
Like
dig
into
this,
this
would
be
a
link
to
a
project
asset,
so
it's
an
asset
link,
not
really
like
the
actual,
okay,
tarball
or
yeah.
You
know
artifact,
so
that's
that's.
That
would
be
an
application
of
the
links
to
to
deep
link
into
the
project
artifact.
I
think
that
going
back
to
your
point,
it
allows
it's
an
mvc
like
a
lightweight
way,
to
display
information
on
the
group
release
without
requiring
us
to
support
repositories
at
the
group
level.