►
From YouTube: Group Releases Discussion with Marin
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
Given
that
there's
no
code
or
a
repository
at
the
group
we're
wanting
to
validate
and
think
through
this
workflow
and
consider
different
ways
that
people
would
interact
with
an
aggregated
releases
concept
at
the
group
level.
So
we're
hoping
to
pick
your
brain
about
some
prototypes
that
hayana
has
and
I'll
pass
it
over
to
her.
B
Awesome
so
mari,
you
know
the
drill
I'm
going
to
share
with
you
a
prototype
on
figma
and
we
have
a
bunch
of
questions
on
it.
So
if
you
can
answer
out
loud
and
tell
us
in
all
honesty
what
you
think
of
the
workflow,
that
would
be
awesome.
So
I
sent
you
here
in
the
chat.
So
if
you
can
share
your
screen.
B
You
shouldn't
need,
but
if
you
do
okay
cool
and
then
there's
a
play
button,
all
the
way
on
the
top
on
top
right,
yeah
click
that
you
going
full
screen.
B
Okay,
yeah:
did
you
see
up
hold
on.
B
Not
it's
loading.
It's
a
bit!
It's
a
bit
odd,
but
okay,
yeah!
So
can
you
tell
us
a
little
bit
of
what
you
see
in
this
view,
if
you
notice
anything
different
new,
improved.
C
The
only
thing
I'm
seeing
here
is
this
addition
to
releases
like
the
releases
overview.
I
guess.
C
I
would
expect
to
see
a
collection
of
most
recent
releases
for
each
and
every
one
of
the
projects
inside
of
this
structure,
so
I
would
expect
to
see
vulnerability,
research
latest
release,
language
tools
or
latest
release
manage
openshift
and
so
on
and
so
on.
I
know
that
this
is
a
subgroup,
but
that's
why
I'm
stating
it
as
well,
because
if
language
tool
has
multiple
projects,
I
would
expect
those
projects
to
roll
up
to
this
group
and
the
summary
of
it
to
end
up
in
the
releases
page.
C
Well,
there's
not
much
to
see
because
there
is
only
getting
started
so
yeah,
that's
pretty
much
it.
Actually.
Something
is
odd.
Here
is
this
because
of
a
prototype
most
likely,
I'm
missing
the
links
on
the
site
here,
so
it
could
be
just
a
prototype.
So
I'm
a
bit
surprised
that
I
went
here
and
I'm
still
rolled
up
to
the
group
overview
rather
than
the
releases.
C
B
So
you
expect
to
see
the
the
where
you
are
in
the
menu
yeah
yeah,
exactly
yeah.
This
is
the
prototype.
That
was
me
yeah
and
what
is,
if
anything
is
missing
here
in
this
view,
what
else
can
you
tell
us
about
this
page.
C
Well,
what
I
find
a
bit
odd
about
this
page
right
now
is,
if
releases
on
the
group
level,
are
supposed
to
be
a
collection
of
releases.
I
find
it
a
bit
odd
that
it's
telling
me
getting
started
with
releases
on
this
level.
What
I
would
kind
of
expect
to
see
here
is,
I
already
know
I'm
at
the
group
level.
C
Why
would
you
expect
me
to
think
of
the
releases
the
same
way?
I
would
think
of
it.
You
know
at
the
project
level
what
I
would
prefer,
or
what
I
would
expect
to
see
here
more
is
either
similar
structured
tree
like
we
saw
earlier
with
group
subgroups
and
so
on,
stating
no
releases
or
number
of
releases
or
just
like
a
general
overview.
C
B
C
C
A
It
was
more
like
you,
I
think
you
nailed
why
this
empty
state
looks
the
way
it
does
today
is
because
we're
wanting
it
to
be
flexible
for
users
who
have
like
a
micro
services
structure
where
they
really
do
have
one
application
that
populates
from
a
series
of
subgroups
and
groups
and
wanting
to
bucket
those
things
but
you're
totally
right
that
we
need
this
empty
state
to
also
be
intuitive.
For
those
who
would
be
interested
in
creating
maybe
a
cherry-picked
version
of
where
there's
different
projects
across
different
kinds
of
subgroups.
B
So,
martin,
what
do
you
expect
to
happen
when
you
click
the?
I
don't
think
I
cannot
see
exactly
from
your
your
screen,
but
there's
a
button
to
create
a
new
release.
The
green
button.
C
D
D
C
I
didn't
even
see
the
button,
so,
oh
sorry,
I
already
clicked
on
it.
Well,
I
guess
I
would
expect.
C
C
C
Would
there
is
maybe
like
one
use
case
where
I
would
use
the
same
title
for
multiple
projects,
but
I
would
still
expect
to
have
some
flexibility
on
what
those
projects
like
what
kind
of
tags
do
we
create,
or
we
we
connect
to
a
certain
release.
C
Let's
say
gitlab
releases
if
I
were
to
create
a
gitlab
release
for
the
22nd
of
august
2020.
I
would
probably
name
this
22nd
22nd
of
august
release
or
something
like
that.
So
that's
a
human,
understandable
context
and
concept.
C
C
D
C
D
A
No,
not
at
all,
I
feel
like
you're
the
the
fourth
interview
that
I've
done
on
group
releases
and
it's
it's
it's
not
too
divergent
at
all.
It's
it's!
It
is
a
gla.
I'm
glad
that
you
used
the
word
confusing,
because
that
was
the
impression
that
we
had
when
we
first
started
designing
this.
So
that's
good,
yeah!
A
C
A
C
So
that's
a
good
question.
It
really
depends
on
what
kind
of
flow
you're
expecting
here
like.
I
have
to
repeat
my
obligatory
thing,
which
is,
if
I
go
through
the
api,
I'm
most
likely
going
to
circumvent
this
whole
process.
So
the
api
is
important,
but
I
would
expect
that
each
project
within
a
structure
would
have
well
two
options
right,
like
they
have
a
unified
structure
which
makes
everything
super
easy
or
they
have
their
own
separate
structures,
which
is
majority
like
the
case
in
majority
of
time.
So.
C
How
that
you
would
do
that?
That's
well
your
problem.
I
don't
know
exactly
how
you
would
do
it,
but
and
if
that
is
not
an
option,
if
the
release
is
not
something
I'm
looking
for
because
right,
like
I
see
like,
I
don't
see
it
in
the
drop
down,
it
doesn't
relate
to
the
release,
I'm
creating
right
now.
I
would
probably
go
down
the
tag
level
to
create
from
a
specific
sha.
C
It
can
be
created
from
a
branch,
obviously,
but
I
think
I'm
leaning
more
towards
a
specific
shot,
because
that
kind
of
covers
both
a
branch
and
a
commit
and
right,
like
all
of
those
things.
So
I
think
that
would
be
like
the
thread
I
will
be
following.
A
So
to
repeat
that
back,
you
would
want
to
so
you'd
want
to
get
go.
Get
the
information
like
say
that
this
was
a
drop
down
menu,
select
what
you'd
want
to
create
from
those
the
projects,
and
you
would
rather
see
shaw's
in
that
drop
down
menu
that
way
you're
able
to
so.
C
In
the
drop
down
menu,
absolutely
not
a
shot,
because
that
would
be
really
confusing.
For
example,
right
you
have
like
hundreds
and
hundreds
of
commits
a
day
you
can
just
you
won't
filter
it
right.
You
won't
filter
it,
but
if
I
already
didn't
select
a
release,
an
existing
release.
D
C
A
So
supporting
more
of
the
the
shaw
interaction:
okay,
that's
perfect!
One
workflow
that
I'm
kind
of
flirting
with
right
now
is
going
to
this
page
and
looking
at
the
most
recent
branch,
that's
been,
you
know,
cut
from
from
master
and
declaring
that,
as
a
part
of
a
group
release
that.
C
Would
be
that
could
be
a
thing
to
do
but
think
about
it.
This
way
from
from
hitler
perspective,
for
example,
if
you
think
about
gitlaborg
gitlab
project
the
moment
we
create
a
stable
branch
from
master,
stable
branch
is
already
out
of
date
and
because
of
the
amount
of
volume
we
have
of
changes,
chances
of
someone's
branch
being
already
newer
than
the
stable
branch
are
very
large.
C
So
if
I
were
to
go
down
that
route,
I
would
probably
prefer
to
have
a
specific
prefixes.
So
say.
If
you
want
to
pre-populate
this,
you
may
be
collecting
the
protected
branches.
C
Right
like
there
are
productive
branch
rules,
master
is
protected
or
main
branch
is
protected,
and
probably
some
set
of
deployment,
branches
or
stable
branches
or
backboard
branches
like
something
that
is
tied
to
that
specific
workflow
and
selecting
the
most
recent
one
from
that
set
might
actually
make
sense,
because
all
the
other
ones
are
discardable
like
you
can
delete
them
at
any
point
in
time.
They
shouldn't
persist
absolutely.
B
C
Probably
the
release
title
immediately.
I
would
do
something
there.
C
Oh
that's
cool
yeah!
That's
pretty
much
why
I
expected
right
a
release
drop
down
now.
C
D
C
Is
this
the
fact
that
the
release
is
this
because
13.1
is
the
latest
release
or
because
13.1
was
created
weeks
ago
or
day
ago,
or
something
like
that
and
it's
already
out
of
date,
so
I
don't
know
that
information.
How
do
I
know
this
is
the
latest
and
based
on
what
would
that
be?
Okay,
let's
use
that.
Actually
let
me
use
this
as
an
example.
I'm
gonna
use
this
one.
C
Wait
for
which
so,
if
you're
telling
me,
I
need
to
create
use
a
milestone.
C
My
group
milestone,
but
is
this
from
a
group
or
a
subgroup
and
which
projects
does
this
group
contain
because
I'm
not
really
sure
right
like
if
I
know
the
name
of
the
group,
if
it's
a
subgroup
one,
I
might
know
all
the
projects
below
it
and
but
I
might
not,
and
I
don't
know
whether
I
need
all
of
that
or
or
not
right
like.
I
just
feels
a
bit
confusing
there
and
then
my
project
milestone.
C
C
B
Yeah
but
that's
a
good
point
there
and
I
think
in
general
we
are
don't
really
do
a
good
job
in
like
step,
step,
information
or
stat
process
in
the
in
the
forums.
And
indeed,
if
the
information
depends
on
the
previous
form
item,
we
should.
We
should
be
more
explicit
about
that.
C
C
I
would
expect
this
section
to
be
already
pre-filled
for
me,
even
if
it's
only
a
title
from
that
release
from
the
project
I
selected,
and
you
know
all
of
the
text
related
to
that
release-
that
I
can
then
delete.
It
will
become
complicated.
The
more
items
you
add,
but
there
is
a
way
in
in
markdown
to
actually
just
hide
that
as
a
comment,
so
you
can
actually
just
remove
the
comments
and
say
you
know,
cherry
pick
what
you
actually
want
to
show.
C
I
would
like
to
see,
for
example,
here
like
I
would
see
this
is
an
ideal
replacement
jackie
by
the
way,
it's
ideal
replacement
for
our
all,
like
release,
notes
all
over
the
place
that
we
have
like
in
the
handbook
in
project
pages.
C
Like
all
of
that,
I
think
it's
gitlab
or
gitlab
release,
notes
that
we
currently
put
in
there
should
probably
roll
up
to
the
group
and
include
all
of
the
other
components,
because
that
is
the
release,
actually
not
only
one
project,
and
then
I
will
probably
just
go
and
edit
things
around
here
to
make
it
a
bit
prettier.
C
So
right
now
I
selected
only
one
project
right
and
one
release
so
having
that
spot
pre-populated
might
be
useful,
but
it's
probably
more
useful.
If
I
select
multiple
projects,
all
of
them
have
their
own
releases
that
are
already
nice
and
pretty,
and
they
are
somehow
added
to
this
in
a
specific
way
so
that
I
can
then
go
and
uncomment
what
I
actually
need
from.
C
I'll
absolutely
expect
assets
here,
but
let's
talk
about
the
description
for
a
bit,
I
can
imagine
myself
if
I
were
to
use
the
interface.
I
can
imagine
myself
going
and
thinking
about
the
the
items
that
I
would
like
to
highlight
for
each
specific
release
as
a
draw
in
and
then,
if
I
go
and
remove
say
this
pajamas
project,
I
selected
it.
B
C
20
something
release
notes,
while
all
of
them
might
be
important
for
the
pyjama
people.
There
might
not
be
all
that
important
for
my
group
to
know
there
might
be
one
thing
from
that
release.
Note
that
I
want
to
highlight
and
say,
oh
and
leave
that
item
in
like
this
is
an
important
item
there
for
rest
link.
Right
click
link
to
go
to
the
other
release
notes
and
I
would
have
like
if
I
have
10
projects,
I
would
have
a
highlight
from
each
of
the
project
with
the
link
to
the
full
release
notes
for
each
project.
A
So,
to
extract
a
little
bit
from
this,
you
would
like
to
have
a
way
for
the
curated
release,
notes
that
are
on
the
project
to
further
curate
them
at
the
group
level.
So
this
may
mean
that
if
the
release
notes
of
the
project
level
are
populated
from,
let's
say
semantic,
release
and
use
december
architecture,
maybe
you
would
want
to
be
able
to
configure
an
option
that
says
you
only
pull
in
features
rather
than
bug
fixes
or
whatever,
like
having
a
configuration
option.
C
Yeah,
like
a
filter
like
a
label
filter,
we
have
everywhere,
would
be
an
option.
You
know
you
set
certain
set
of
labels
and
say
filter
on
this
one
I
want
to
highlight
this
is
a
bug
fix
release,
for
example
right.
These
are
all
the
bugs
we
fixed.
This
is
a
security
release.
Right
like
there
are.
Sometimes
you
have
these
mixed.
C
Where
you
just
want
to
highlight
features
where
you
want
to
highlight
these
performance
improvements
with
it,
it
really
depends,
but
that
option
might
be
actually
interesting
to
you.
A
Yeah,
so
it's
really
it's
really
cool
that
you're
saying
this,
because
we
do
have
an
issue
that
we're
looking
at
prioritizing
about
associating
releases
to
labels
so
that
we
would
be
able
to
more
fine-tune
like.
Oh,
I
want
to
see
all
the
releases
that
have
to
do
with
a
bug
you
know
inside
a
gitlab
whatever,
but
we're
also
going
down
different
release,
notes
being
generated
from
different
components
of
gitlab.
A
C
I
actually
would
prefer
that
in
like,
for
example,
for
a
big
company.
I
would
prefer
that
so
at
gitlab
for
example.
Right
now,
I
used
to
have
a
lot
of
confidence
that
our
commission
could
commit.
Messages
were
perfect
because
we
had
a
smaller
dedicated
team
that
was
very
much
focused
on
making
everything
tight
and
pretty
and
was
rightly
dedicated
to
the
workflow,
but
with
a
big
company
like
this,
that
dedicated
workflow
is
confronted
with
many
opinions
that
I
may
or
may
not
agree
with,
which
also
means
our
history
commit.
C
History
is
messier
than
it
used
to
be,
but
the
issues
and
merge
requests
titles
are
probably
more
important.
I
would
probably
focus
on
merge
requests
rather
than
issues,
because
merger
requests
are
the
one
that
are
bringing
in
the
code
unless
you
have
a
way
to
connect
a
merge
request
to
issue
and
like
say
like
this,
merge
request
is
rolling
up
to
this
issue,
and
then
we
are
going
to
use
this
right,
but
it
becomes
complicated.
There.
D
B
So
jack,
you
want
to
talk
about
assets
further
than
the
this
interview:
okay,
cool!
So
then
marin,
if
you
click,
I'm
not
sure
where
you
are
now
in
prototype,
so
I
can
save.
B
Yeah,
so
if
you
can
tell
us
what
you
see
on
this
view,
what
you
understand
from
from
this
prototype.
D
D
C
Wait
why?
What
confuses
me
is
the
my
group
release
that
I
just
created
and
I
selected
a
single
release
as
far
as
I
remember,
why
do
I
have
two
more
shown
that
are
not
the
ones
I
selected?
Is
this
a
prototype
thing
or
yeah.
B
C
First,
one:
okay,
okay,
I
get
it,
I
get
it
now.
I
don't
understand
why
I
would
have
zero
percent
complete
their
milestone
issues.
Like
all
of
that,
I
don't
understand
that
information.
Didn't
I
just
create
a
release.
C
That
means
things
are
completed,
so
it's
100
completed
all
the
time
because
I
created
the
release.
The
milestone
might
not
be,
but
that's
a
different
story
and
what's
going
to
happen
at
the
end
of
the
milestone,
someone
is
going
to
come
back,
groom
it
clear
it
up
out
close
the
milestone
and
then
it's
going
to
be
100.
So
did
I
just
create
a
release
out
of
an
uncomplete
milestone?
C
A
C
C
So
if
that
is
the
concept,
then
upcoming
is
very
much
confusing
here,
because
what
I
would
expect
from
an
upcoming
is,
I
already
created
everything
the
date
is
coming
around.
C
C
C
C
Those
are
like
basically
the
three
options
I
see
when
I
go
to
the
page.
The
second
thing.
C
The
interface
could
do
some
work,
but
this
is
not
what
we
are
talking
about
here.
I
guess,
and
I
like
the
group
release
three
like
that's
the
same
thing
as
the
first
one,
just
zero
or
100
like
it's.
I
think
it's
the
same
feedback.
I
don't
necessarily
know
what
I
would
do
with
that
information.
So.
A
A
A
In
the
release,
progress
view
in
the
archive
will
be
100
because
that's
the
reconciliation
of
this
is
what's
contained
in
this
release.
From
from
that
perspective,
so
that's
really
that's
super
feedback.
There
are
we
highly
do
you
have
any
other
questions
on
this
view,
because
I
kind
of
want
to
poke
at
assets
now
yeah.
B
Go
ahead,
I
just
have
a
questions
around
the
the
ui
elements,
like
maybe
I'll,
just
wrap
up.
There's
anything
that
you,
you
think
it's
missing.
From
this
view,
marine
yeah
highlights.
B
C
D
C
I
would
probably
want
to
highlight
with
the
latest
release,
although
if
you
put
it
out
in
the
top,
then
you
highlighted
it
already,
but
then
I
would
expect
all
the
older
ones
to
be
highlighted
a
bit
differently
right,
like
toned
down
like
not
white,
so
much
in
my
face,
but
like
something
different
to
just
put
them
back
in.
In
the
background,
like
my
current
release
is
what
I'm
looking
for.
A
C
Yeah
collapsing
it
one
way
paginating
it
like
something
like
that,
just
you
don't
have
to
have
it
in
your
face
like
if
you
take
a
look
at
how
packaging
systems
usually
do
things
top
down.
Everything
else
is
basically
archives.
Like
you,
you
just
go
click
an
additional
button
because
you're
looking
for
something
that
is
not
what
the
project
creator
is
expecting
you
to
look
at
right.
A
So
what
I
would
like
to
share
with
you
from
a
group
release
perspective.
We
currently
have
our
our
dog
fooding
of
the
releases
page,
where
it's
populated
from
the
release
post
and
what
I
would
want
to
see
in
the
future
is
that
it's
populated
on
the
group
page
and
we're
able
to
view
this
sort
of
granularity
of
each
of
the
projects
that
feed
into
this
to
help
our
sales
and
marketing
team
kind
of
navigate
what's
been
released.
A
C
I
I
get
that,
but
that
is
a
completely
different
audience
you're
talking
about
here,
right,
like
if
you're
talking
about
the
users
of
a
set
of
projects
or
or
or
of
this
release
like
I
would
come
in
to
download
an
artifact
and
look
at
the
release,
notes
to
do
something
with
it,
rather
than
look
at
the
wish
list
of
what
we
might
deliver.
If
I
want
to
do
that,
I
would
probably
click
something
or
zoom
in
or
you
know
like
highlight,
highlighted
in
a
different
way.
But
what
I'm?
C
A
C
A
So
since
you
already-
you
kind
of
think,
you
already
asked
this
question
for
me,
but
if
you
go
to
this
group,
release
page
being
able
to
click
into
a
specific
asset
or
artifact
for
each
of
these
sub-projects
from
this
view
would
be
a
useful
feature.
Yeah,
absolutely
okay,.
A
Perfect
just
wanted
to
validate
that
assumption.
What
are
your
impressions
of
this
feature?
What
do
you?
What
do
you
think
about
it?
I.
C
I
I
am,
I'm
actually
excited
if
we
are
able
to
use
it
through
the
api,
because
it
will
allow
us
to
do
a
couple
of
things
that
we
are
right
now
doing
in
in
a
programmatical
way,
but
from
from
our
release
tools,
we
would
be
able
to
tag
and
like
if
we
have
attachments
as
well.
That
would
be
outstanding,
because
that
would
allow
us
to
do
different
things
with
it.
We
could
attach
release
evidence
for
each
and
every
one
of
these
individually
and
have
them
roll
up
to
this
group
level.
C
Then
we
don't
have
to
deal
with
additional
pages
that
we
have
out
there,
the
the
release,
notes
or
the
change
long
notes,
whatever
you
want
to
call
them
like
that.
All
could
be
rolled
up
here.
C
I'm
yeah
like
if
we
are
able
to
first
of
all
offer
attachments
and
then
also
add
arbitrary
attachments
to
the
release
as
an
additional
thing.
So,
yes,
you
have
the
release
artifacts,
but
you
also
have
the
additional
things
that
you
would
like
to
bundle
into
a
release.
Right,
like
you,
generate
release
evidence
automatically,
but
we
have
wider
scope,
for
example.
So
I
would
like
to
generate
a
single
release.
Evidence
file
that
I
would
like
to
attach.
Here's
for
everyone
else
to
to
use.
C
Well,
it
would
be
nice
for
it
to
be
automatically
done.
I
have
some
additional
requirements
with
licensing,
and
so
on
that
I
need
to
insert
post
release
creation,
and
that
would
be
interesting
to
to
offer
out.
A
Oh,
I
you
just
picked
my
like
peeks
my
ears
on
on
release.
Evidence
we'll
have
to
have
another
call
on
that
one,
but
because
I
would
love
to
build
out
that
feature
for
our
dog
food
and
use
case.
Obviously
it's
super
minimal
right
now
we're
just
trying
to
like
get
stuff
in
it,
so,
but
definitely.