►
From YouTube: Support Release Review - 13.2
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
Which
is
really
cool,
we've
got
some
really
exciting
features
in
lab
13.2
and
if
you've
never
been
to
a
release
party
before
the
whole
point
of
it
is
hey.
It's
a
party
and
everyone
loves
a
party
and
b
it's
just
basically
to
talk
about
the
different
features
and
functionality
that
have
been
introduced
in
the
last
minor
release,
so
get
lab
releases
a
minor
release
every
month
with
a
major
release
every
year,
so
yeah.
A
So
I'll
just
share
my
screen,
so
everyone
can
see
what
I'm
talking
about.
Okay,
can
everyone
see
a
release,
review
support
team
document,
just
yep
cool?
Thank
you,
so
I'm
actually
taking
over
wei
ming
today,
because
he's
on
public
holiday
and
yeah,
I
thought
I'd
jump
in
about
so.
The
first
feature
I
wanted
to
talk
to
about
today
was
the
managed
php
dependencies
with
the
gitlab
composer
repository.
A
So
before
I
actually
came
to
gitlab,
I
was
a
php
developer
and
we
used
gitlab
extensively
because
of
the
devops
tool
chain.
We
liked
having
everything
in
one
place,
and
the
only
thing
that
we
didn't
have
was
composer
repositories
in
gitlab.
So
I'm
actually
very
excited
to
see
this
feature.
Finally,
in
gitlab-
and
I've
also
told
a
few
ex
colleagues
about
it
and
they're
also
very
excited
to
see
this
phone
in
gitlab
too,
so
I
thought
I
might
go
into
it
a
little
bit
and
show
you
what
it's
all
about.
A
So,
if
everyone
to
some
degree,
it's
very
similar
to
all
our
other
package
types
like
maven,
pi,
pi,
npm,
etc,
and
all
you
need
to
know
about
composer
is
composer.
Is
a
package
manager,
so
it's
like
it's.
It
manages
php
dependencies.
Basically,
so
it's
like
your
npm
for
javascript
or
you
may
even
put
your
java.
A
So
if
we
take
a
quick
look
at
the
actual
release
post,
we've
got
tim
from
the
packages
team,
who
has
done
a
very
quick
speed,
run
through
the
feature,
and
he
describes
how
to
build
a
project
from
a
composer
project
from
scratch
and
then
upload
it
as
a
package
into
the
get
lab
composer
repository,
and
he
shows
two
methods
how
to
do
this
through
the
workstation
through
your
local
workstation
or
through
get
lab
ci.
A
I
do
recommend
watching
that
if
you
want
to
get
familiar
with
it,
but
for
the
purposes
of
today,
I'm
just
going
to
power
through
it
even
faster
than
tim's
speedrun,
and
I'm
just
going
to
create
a
really
quick
package
using
our
documentation
because
everyone
loves
demo.
It's
a
bit
dry,
watching
people
scroll
up
and
down
pages,
so
something
a
bit
more
interactive.
A
So
let's
go
to
the
documentation
for
this.
Where
is
it
cool?
So
for
the
majority
of
get
lab
instances,
they
have
13.2
the
packages.
A
So,
first
of
all,
we
just
need
to
make
a
directory
to
store
our
project
and
we
need
to
touch
a
composer
json,
which
is
basically
a
manifest
file
that
contains
all
the
information
you
need
to
know
about
a
particular
composer
dependency
or
project
or
package.
The
names
are
interchangeable,
so
it
can
kind
of
get
a
little
confusing,
but
we've
got
a
name
type
licensed
version,
but
you
can
also
have
dependencies
so
say
I
wanted
to
have
curl
as
a
deficiency
in
my
composer
project.
That's
all
possible.
A
So
let
me
just
quickly
do
that
now,
so
I'm
going
to
use
my
wizardry
I've
actually
already
pre-populated
all
the
commands.
I
need
to
type
so
I
created
a
composer
package
and
now
I'm
cd
in
and
now
I'm
going
to
touch
a
composer
json,
but
we
need
to
actually
create
it.
So
we
can
see
I've
got
a
name,
insomn
composer
test
and
it's
version.
1.1
up.
A
A
A
A
A
A
A
A
A
Now,
if
we
go
into
the
packages
and
registries,
so
we've
got
this
here
for
those
that
haven't
seen
it
before
and
we
can
see
under
the
all.
We've
got
our
composer
test
package
that
I
just
uploaded
now
and
back
here.
We've
also
got
a
composer
tab,
just
like
all
the
other
different
package
repositories.
A
A
A
When
you
actually
go
to
install
the
package,
you
need
to
add
a
composer
repository
source
to
your
project's
composer.json
file
to
actually
pull
that
package
through
and
it
actually
goes
through
the
group
api.
So,
as
far
as
I'm
aware,
you
can't
use
a
personal
namespace
as
a
group.
So
that's
something
to
keep
in
mind
too.
A
It
might
trip
a
few
of
our
customers
up,
I'm
not
sure,
but
just
a
heads
up
and
finally,
I've
added
myself
to
the
knowledge
areas
for
the
support
team,
composer,
php
side
of
things.
So
if
you
are
working
on
any
composer
related
tickets,
I
am
definitely
happy
to
work
alongside
you
and
yeah
just
collaborate,
because
it
is
a
field
that
I've
been
working
in
for
a
long
time
so
happy
to
share
my
experiences
there.
A
A
A
A
A
The
other
thing
to
be
aware
of
with
this
feature
is:
if
you
are
setting
up
the
jira
integration,
it's
actually
necessary
to
enable
enable
jira
issues.
You
need
to
check
that
box
here
for
the
jira
issues.
Navigation
item
to
show
up
the
issue,
though,
that
we
have
to
keep
in
mind
is:
let
me
just
got
so
many
tabs
open.
So
we
go
back
to
here,
and
the
thing
is
by
having
both
jira
issues
and
get
lab
issues
enabled
it's
possible
that
users
might
get
confused
between
the
two
they
might
not
know
which
one
to
use.
A
So
we
actually
have
a
little
warning.
I'm
not
sure
if
you
noticed
just
below
here.
That
explains
your
issues
while
leaving
the
get
labor
issue.
Functionality
enable
might
be
confusing,
so
we
suggest
to
our
users
that
they
should
disable
get
lab
issues
if
they
want
to
use
your
issues
just
keep
things
stripped.
A
So
this
is
a
pretty
cool
feature
that
I
think
has
been
absent
and
well
overdue.
A
Where
previously,
when
you
were
importing
jira
issues
into
gitlab,
it
would
require
the
importing
user's
username
to
be
imposed
on
all
the
imported
issues,
the
comments
etc
and
that's
not
really
ideal.
In
the
best
of
cases
is
it
especially
when
you've
got
a
large
user
base?
A
So
when
we
try
that
functionality
out,
we
can
just
go
to
issues
list,
import
issues
import
from
jira
and
we
can
see
here.
We've
got
a
menu
where
I
can
choose
the
jira
project.
I
want
to
input
from,
and
we've
got
a
user
map.
So
on
the
left
side,
we've
got
slack,
trello,
jira
service,
disk,
widget
and
then
get
lab
usernames.
So
you
can
imagine,
I've
got
one
here
called
apophis,
so
you'd
want
to
select
the
poffice
on
the
site.
So
it's
all
mapped
up
correctly.
A
Now,
there's
already
a
few
issues
that
I
identified
through
a
ticket
where
a
customer
was
not,
they
weren't
completely
happy
with
how
the
feature
worked
and
where
is
it?
That's
good.
A
So
at
the
moment
you
would
have
noticed
that
it
just
went
anton
antoinette
on
anton,
and
I
realized
I
was
the
only
user
there
at
the
moment.
But
if
there
was
a
lot
of
other
gitlab
users
I
could
have
selected,
it
would
have
just
selected
myself
and
the
names
aren't
being
mapped
across
yet,
and
that's
mainly
because
it's
a
bit
difficult
to
do
because
on
the
atlassian
side
they
only
have
email
address
visible
to
gitlab.
If
the
user
email
address
is
set
publicly,
that's
a
specific
setting
on
atlassian
profiles.
A
A
A
The
other
caveat
that
I
ran
into
is
this:
this
upset
one
of
our
customers
a
lot
that
the
jira
issues
of
the
user's
projects
returned
is
limited
to
100
and
that's
just
due
to
a
hard
coded
value
in
the
graphql
api,
where
it's
only
returning
100
results.
A
A
Alrighty,
let's
move
on.
That
concludes
all
my
demos,
but
we
can
go
through
all
this
stuff.
I
thought
this
feature
was
actually
really
cool,
where
we've
got
real-time
feedback
for
the
ci
dot,
yml
file
and
the
web
idea.
So
we've
got
it's
kind
of
like
syntax
checking.
I
guess
in
a
way,
so
it's
kind
of
those
nifty
little
easter
eggs.
It's
kind
of
good
to
know
about
so
I
thought
I'd
just
show
that
here.
B
C
A
No
definitely
the
there
is
another
ci
lint
tool
that
you
can
use
if
you're
not
already
aware
of
it
and
I'll
add
a
link
later,
but
the
basic
it's
not
as
refined
as
the
web
ide
method,
you
basically
just
paste
your
gitlab
ci
dot,
yml
into
a
text
box
and
then
hit
the
validate
button,
and
then
you've
got
to
do
that
every
single
time
you
want
to
test
it,
which
is
it's
not
really
ideal,
but
it's
it's.
What
we've
had
up
until
now,
so
yeah
just
something
to
be
aware
of.
A
I
just
wanted
to
talk
about
some
of
the
omnibus
improvements,
because
often
the
things
that
are
overlooked-
and
I
think
one
of
the
really
cool
things
now
is
the
consolidation
of
object
storage
settings.
So
let's
take
a
quick
look
at
that.
A
So
for
those
that
are
familiar
with
these
settings,
you
may
have
realized
that
we
had
to
specify
these
connection
details
on
every
single
type
of
object:
storage,
whether
that's
lfs,
artifacts,
backups,
traces,
etc.
It
just
got
a
little
repetitive,
so
it's
really
great
that
we've
consolidated
this
into
one
set
of
settings
where
you
specify
your
connection
settings
and
now
we
have
all
the
different
buckets
that
you
just
have
them.
You
know
specify
yourself.
A
A
A
I'll
finish
the
next
point,
and
then
if
there
are
any
questions
we
can
discuss
them.
A
The
next
one
is
omnibus
install
package,
so
there
is
now
a
package
for
ubuntu
20.0.4,
which
is
really
cool,
because
previously
I
had
to
muck
around
with
the
ppas
to
use
the
bionic
ones
on
ubuntu
220,
but
now
we
can
use
the
focal
ones
which
is
really
cool.
A
Let's
click
into
that.
That's
not
where
I
wanted
it
to
go.
A
A
A
Alrighty
moving
on
important
notes,
so
this
caught
my
eye.
A
A
We
have
version
specific
upgrade
instructions
here,
but
it
kind
of
complicates
it
a
little
bit
for
us,
especially
if
we're
offering
version
upgrade
advice
to
customers.
So
it's
probably
important
to
check
if
they
have
multiple
application
nodes
when
we
make
their
device
from
now
on.
B
B
A
Yeah
so
yeah
so
13.2
we
recommend
going
to
13.0.0
or
we
could
maybe
just
blank
have
a
blanket
rule
for
everyone.
They
need
to
go
to
13.0
13.1
13.2.
A
A
Alrighty.
That
concludes
my
part
of
the
demonstration
today
in
the
release
party
and
I'll
hand
it
over
to
matthew.
B
B
So
the
first
one
I
wanted
to
talk
about
was
code
owner
section.
It's
a
really
cool
feature
about
dividing
up
your
work
between
different
groups
of
teams.
If
you
have
multiple
groups
of
teams,
you
can
separate
who
is
the
owner
of
that
section
and
get
approval
from
them
before
the
code
gets
merged
code
owners
has
been
around
for
a
little
while,
but
each
version
comes
with
extra
support
and
in
this
version
we
have
a
code
owner
section
which
is
really
cool.
B
So,
for
example,
on
my
screen,
you
can
see
the
screenshots
showing
documentation
database
security.
You
could
add
things
like
qa.
A
B
Design
if
you're
modifying
something
front
end
or
other
groups
added
here,
you
can
view
the
information
here.
This
just
extends
what
we've
already
had
with
code
runners
already,
but
it's
really
cool
to
see
the
additional
groups
added
here
as
well.
So,
for
example,
you
can
see
doc
here.
So
that's
an
extra
group
that
gets
approval
from
just
to
make
sure
that
everything's
following
the
rules,
I
guess.
B
A
I
just
want
to
add
that
yeah.
I
know
in
particular,
a
lot
of
customers
have
wanted
these
different
sections
for
a
long
time
so
yeah,
it's
definitely
cool
that
it's
finally
made
it
into
the
product.
B
All
right
next
up,
we
have
the
advanced
global
search.
Now.
This
is
something
that
our
other
competitors,
like
github,
have
had
something
like
this
for
a
while.
It's
it's
really
good,
because
when
you're
searching
for
code
before
when
you're
searching
for
code
and
you're
looking
for
a
specific
line,
it's
really
difficult
to
do
within
within
git
lab,
let's
say
you're
looking
for
in
my
example:
ldap
user.
So
it's
pretty
easy
to
just
kind
of
go
to
repository.
B
For
example,
I'm
gonna
go
to
just
get
lab.
This
is
our
repository.
You
can
just
search
up
here
in
the
top
right.
This
only
works
on
gitlab.com
by
the
way
right
now,
but
this
will
be
released
for
everybody
else
in
the
future
something's
going
on
with
my
ui
okay,
so
I
like
using
this
example,
because
it's
pretty
easy
to
find
you
just
go
into
the
search
bar
and
search
for
it.
Previously,
you
couldn't
find
the
code
and
it's
really
quick,
I
think
in
my
opinion,
it's
really
really
quick.
B
B
A
B
B
So
if
you're
looking
for
a
specific
snippet
of
code,
if
you're,
like
a
lazy
programmer
like
me-
and
you
want
to
just
look
for
some
authentication
code
in
your
target
language,
it's
only
going
to
do
the
current,
the
current
repository
right
now
or
the
current
project.
But
I
was
talking
to
one
of
the
search
people
on
the
one
of
the
people
on
the
search
team
and
they
mentioned
that
they
really
want
to
expand
this
out.
B
You
can
search
code
results
by,
for
example,
here
you
can
click
on
the
master
tag
and
say.
B
B
So
you
can
search
per
tag
but
starting
the
search
go
up
to
the
right-hand
corner
of
the
screen
and
then
start
the
search
and
then
from
there
go
to
the
options
where
you
can
change
the
branch
and
then
modify
where
you're.
Looking
from
here,
you
can
search
the
group
or
the
project
itself.
D
B
Looking
for
a
specific
code
is
a
little
different.
You
can
check
the
advanced
search
functionality.
There's
a
little
help
here.
If
you
click
this
you
can
see
and
then
from
there
you
can
look
at
different
use
cases.
You
can
find
bugs
syntax
search
filters
here.
So
please
check
this
out.
You
you
can
get
to
this.
B
B
B
All
right,
I
will
include
a
link
to
this
documentation,
the
administrative
documentation
to
enable
that,
but
right
now
the
feature
is
only
available
on
starter,
bronze
and
higher
tiers
on
gitlab.com.
A
A
Thanks
matthew
for
showing
us
through
that
and
we've
got
mike
now
he's
going
to
show
us
through
a
few
things
as
well.
D
So
that
means
when
you've
got
two
or
more
nodes,
doing
your
git
operations
through
goodly.
Previously
they
used
to
do
rights
asynchronously
and
it
should
work
unless
one
of
them
falls
down
now.
You've
got
them
working
as
a
transaction
do
phase
commit,
so
they
either
both
work
or
they
don't
and
that's
available
now
for
git
operations
over
https
and
ssh,
not
through
the
ui
and
the
other
one
was
to
do
with
the
wiki
one
is
you
can
now
see
differences?
D
It
was
pointed
out
at
the
top
of
the
release,
I've
used
to
work
with
the
wikis
a
lot
in
gitlab
until
I
discovered
that
issues
are
a
lot
more
powerful
for
what
I
was
using
them
for,
but
that'll
be
handy
to
be
able
to
see
what
you
actually
changed
from
one
version
to
another
without
just
having
to
load
the
whole
page
up
from
the
history
page
and
to
round
out
this
releases
integrations
with
the
atlassian
stuff.
You
can
actually
replace
the
built-in
wiki
with
a
confluence.
A
Okay,
now
I
open
the
floor
to
anyone
that
has
any
last
minute
features
concerns
that
I'd
like
to
discuss
with
the
team
before
we
wrap
up.
E
I
actually
had
a
question
so
so
regarding
this
transaction
right.
So
what
is
that
actually
like
before
git
confirms
one
right
as
final?
It
make
sure
like
the
right
is
replicated
across
all
the
gitline
or
something
like
that
or.
D
A
All
right
awesome,
I
think
we
can
call
that
a
success
and
a
very
happy
party.
Thank
you
to
everyone
for
joining.
Thank
you
to
everyone
that
presented
something
today
and
it's
definitely
great
to
see
all
your
faces
in
here
definitely
makes
my
day,
and
I
wish
you
all
the
very
best
and
the
rest
of
your
day
and
we'll
see
you
around
a
good
weekend.
Everyone
thanks
for
hosting
anton.