►
From YouTube: Release Management Community Office Hours - 2020-10-28
A
B
A
A
Okay,
so
welcome
everybody
to
the
release
management
community
office
hours
number
one
on
the
28th
of
october,
so
this
meeting
is
going
to
be
a
regular
meeting
once
a
month
and
it's
for
the
purpose
of
having
community
members
meet
with
members
of
the
release
management
engineering
team
if
they
have
if
they
would
like
to
contribute
to
release
management,
pick
up
an
issue.
Maybe
they
have
some
questions
about
an
issue
and
how
to
work
on
those
those
type
of
items
I'll
do
a
bit
of
introduction.
A
So
so
the
meeting
will
go
generally
for
30
minutes,
depending
on
what
questions
we
might
have
and
just
to
introduce
the
the
team
members
on
the
call.
So
myself,
I'm
sean
carroll,
I'm
a
back
end
engineer
in
release
management.
That
means
I
mostly
work
on
the
rails
stack
so
feel
free
to
ping
me.
My
handle
is
shawn
underscore
carol
about
any
any
whales
questions.
B
D
Thanks
david
hi,
I'm
jake
burden,
I'm
also
on
the
release
management
team,
front-end
engineer
much
like
nathan.
I
work
in
view
and
work
on
the
releases
page
and
occasionally
we'll
work
on
other
release
management
settings
like
deploy,
freezes
and
and
front
end
stuff
for
gitlab
pages.
Once
in
a
while,
and
I
will
now
move
the
introduction
over
to
vlad.
E
A
Sure
hi,
nicole
williams,
the
engineering
manager
for
release
management,
okay,
so
just
before
we
continue,
I
just
wanted
to
point
out
that
this
meeting
is
being
recorded
and
it
will
be
posted
on
youtube,
and
so
there
it
seems
like
we
do
have
a
community
member
on
the
call.
Would
you
like
to
introduce
yourself
nishank?
F
Yeah
so
hi,
I'm
nisha,
so
I
have
just
started
to
explore
the
open
source
software,
so
I
landed
on
gitlab,
open
source
software.
I
messaged
the
shushing
of
vladimir
susheen
few
days
back,
but
somehow,
like
I
had
got
like
a
huge
amount
of
work
in
my
company,
so
I
couldn't
start
with
the
issue
which
I
have
like
messaged
him.
So
I
am
looking
forward
to
contributing.
A
C
A
Excellent:
okay,
that's
really
great
okay!
So
what
I'll
do
now
is
I'll
just
kind
of
talk
a
bit
about
what
does
the
group
release
management
actually
do
so
we're
quite
a
broad
group.
We
cover
a
number
of
different
rails,
a
number
of
different
gitlab
projects,
but
just
before
we
kind
of
get
to
the
actual
underlying
technologies.
A
And
we'll
take
a
look
at
this
main
issue
so
that
you
would,
you
would
have
come
to
this
issue.
We
will
have
a
separate
one
of
these
issues
for
every
community
office
hours.
This
is
the
one
for
today
where
the
agenda
is,
and
I
put
a
whole
lot
of
links
in
here
for
future
reference.
So
if
we
go
to
this
first
link
here,
this
is
what
what
does
release
management
do.
So
we
have
these
different
categories.
We
have
continuous
delivery.
A
A
So
then
we
have
three
main
applications
that
we
work
on,
so
those
features
are
actually
enclosed
in
these
three
main
applications.
So
the
first
one
is
the
git
lab
rails
community
edition
and
there's
a
link
there
to
the
repo.
So
this
this
is
a
this
is
a
rails
app!
It's
it's
the
main
gitlab
application
that
you
would
see
when
you
go
to
gitlab.com.
A
There
is
also
a
corresponding
enterprise
edition,
which
is
the
paid
tier,
but
the
community.
The
community
work
is
focused
on
the
community
edition.
Obviously,
then,
we
also
have
git
lab
pages,
which
is
a
golang
application,
that
the
link
to
the
code
is
there
as
well,
which
I
just
mentioned
before
it's
used
for
a
static
site
serving
it's
quite
a
large
go-ling
application.
So
if
you
have
a
golang
background,
you
might
find
it
quite
interesting
to
work
on
and
then
we
have
another
much
smaller
younger
golang
application,
which
is
the
gitlab
releases,
cli
command
line
interface.
A
So
in
this
case
we,
you
know
it's
a
classic
golang
cli
and
it's
used
it's
actually
used
by
the
the
git
lab
ci
to
to
perform
releases
on
itself.
So
it's
kind
of
this
circular
process,
but
you
can
also
it's
a
binary.
You
can
take
it
and
you
can
use
it
separately
to
to
interact
with
the
gitlab
api
viral
cli.
A
Okay,
so
so
then
we
we
have.
We
have
some
labels
that
we
use
on
our
issues.
So
if
I,
if
I
go
to
well
I'll,
go
to
the
issue
board
in
just
a
moment,
but
we
have
four
main
labels
that
we
work
with
with
the
community,
so
the
first
one
is
accepting
merge
requests.
If
an
issue
has
this
against
it,
then
you
know
anyone
can
contribute
to
it
and
we.
A
We
certainly
welcome
your
contribution
if
you
feel
that
something
is
a
bit
too
difficult
or
you
don't
quite
understand,
feel
free
to
just
you
know,
using
your
gitlab
account
just
put
a
comment
in
the
issue.
You
know
we
interact
with
the
community
in
the
same
way
as
we
as
we
interact
with
each
other
and
most
of
our
issues.
You
know
more
than
probably
90
of
our
issues
are
publicly
available
and
publicly
commentable
on
and
contributed
to
by
by
anyone
essentially,
and
then
we've
created
these
two
new
badges
or
labels.
A
Sorry,
so
it's
good
for
new
contributors,
which
is
a
very
the
idea
of
this
label.
If
you
see
that
one,
there
should
be
a
relatively
simple
issue:
gitlab
is
a
very
complex
product.
So
there's
nothing.
That's
super
simple,
but
we
try
to.
We
try
to
make
them
as
simple
as
possible,
whereas
the
community
challenge
badge
label
is
actually
designed
to
be
it's.
It's
considered
to
be
something
that's
a
bit
more
difficult
and
and
goes
into
a
bit
more
depth,
and
so
therefore
it's
someone
who's
more
familiar
with
gitlab,
internals
and
then
low
hanging.
A
A
Now
so
anything
in
release
management
goes
on
this
board
when
it's
in
this
column
here
workflow
ready
for
development,
it's
been
triaged
and
it's
ready
to
go.
However,
there
may
also
be
some
that
are
in
in
the
open
that
are
ready
to
go
because
they
would
have
accepting
merge
requests
on
them.
So
you
would,
you
could
come
through
here.
You
could
take
a
look
at
the
issue
and
you
might
say
you
know
what
I
think
I
can
do
that
and
then
you
would
just
come
here
and
assign
yourself
to
this
issue.
B
A
Run
it
oh,
I
didn't
realize
that
okay,
thanks
nathan,
so
in
that
case
yeah.
So
in
that
case
you
would
just
go
into
the
issue
and
ping
one
of
the
people
that
was
at
this
meeting
and
we
would
we
would
help
you
with
that,
okay,
so
how
to
contribute.
So
if
we
go
to
the
con
there's
a
we
have
a
document
contribution
guidelines,
so
this
is
quite
a
large
document.
It's
a
documentation.
Exit
levy
is
nearly
always
up
to
date.
A
A
A
A
A
A
There's
quite
a
lot
of
information
about
permissions
and
security,
and
then,
if
you
have
questions
or
for
example,
you
wanted
to
work
on
this,
you
would
just
say
I
would
like
to
work
on
this
and
ping
somebody.
But
also,
if
you
had
any
questions,
you
would
just
write
them
here
in
the
issue
and
and
off
you
go
and
okay.
So
that's
that
is
a
rails,
ruby
on
rails
issue
against
the
main
pit
library
type.
A
E
Yeah,
please
can
you
open
the
issue
itself?
Yes,
actually
it's
a
very
simple
front-end
fix
and
I
would
say
that
if
anyone
like
have
some
small
experience
with
the
html
and
you
can
reproduce
it
locally,
then
you're
very
welcome
to
fix
it.
Basically,
if
I
get
it
right,
maybe
nathan
can
correct
me.
It's
just
the
size.
Vertical
sides
of
the
edit
field
is
not
correct
on
some
browsers.
If,
if
I
get
the
comments
right,
it's
on
linux
and
on
chrome
of
my
particular
versions,
so
if
anyone
can
reproduce,
it
you're
very
welcome
to
fix
it.
E
I'm
not
sure
how
actually,
how
widespread
this
issue,
since
not
so
many
comments
on
it,
but
yeah,
and
this
issue
is
not
like
we're
not
we
weren't
selecting
best
issues.
We
just
found
some
of
them,
so
this
is
easy
fix
for
someone
never
contributed
to
the
gitlab
before
let's
say
and
have
who
has
some
experience
with
front-end
development?
A
E
It's
actually
a
front-end
issue,
it's
just
edit.
It's
just
an
interface
for
setting
up
pages
doesn't
render
the
fields
correctly.
There
is
like
you
see
this
first
screenshot
with
gitlab
pages
verification
code.
There
is
an
underscore
in
the
first
character
character,
and
you
don't
see
it
here
and
that's
the
small
ui
problem.
E
So
again,
if
you
have
some
small
experience
with
go
and
looking
for
a
small
fix
and
small
contribution,
first
contribution
to
the
gitlab
and
also
have
some
experience
with
make.
Probably,
but
that's
probably
an
easy
part,
then
yeah
also
small
issue.
Easy
to
fix-
and
you
will
actually
help
other
contributors
as
well,
because
they
can
easier
set
up
pages
development
later
so
yeah,
basically
just
download
the
pages
clone.
The
pages
repository
run,
make
setup.
A
A
So
this
is
this
is
in
the
gitlab
www.gitlab.com
project,
which
is
basically
source
code
for
about
gitlab.com,
so
the
main,
the
main
documentation
for
for
kid
lab,
so
it's
basically
holiday
markdown
files
and
some
ruby
code
that
that
organizes
those
files,
and
we
have
specific,
we
have
a
specific
generator
for
release
management,
and
so
this
is
not.
In
fact,
this
is
not
even
actually
a
rails
issue.
This
is
pure
ruby
for
anyone.
Who's
got
a
simple
ruby
background
and
so
yeah
I'll
just
actually
just
click
through
to
it.
So
we
have.
A
We
have
you
know
this
ruby
script,
that
is,
it
needs
a
bit
of
refactoring
right
like
it's
just
you
know,
the
methods
are
very
long
and,
and
basically
it's
a
little
bit
unclear
what
some
of
the
parts
of
the
code
do.
So
it
needs
to
be
refracted
and
then,
more
importantly,
it
actually
doesn't
have
any
tests
associated
with
it,
and
so
we
would
like
to
add
those
tests
and
then
there's
a
model
for
those
which
is
linked
here,
which
is
for
another
part
of
the
organization.
A
A
Even
if
you
don't
have
strong
ruby,
I
mean,
if
you
have
any
type
of
you,
know,
oo,
programming
or
even
procedural
programming.
I
mean
you
should
be
able
to
probably
deal
with
this
okay,
so,
okay,
so
before
I
go
any
further,
has
anyone
got
any
questions
about
those
or
do
you
have
anything
you'd
like
to
talk
about
that's
outside
of
this
list?
Any
issues
that
you've
looked
at
yourself.
A
F
E
I
just
wanted
to
sorry.
I
just
want
to
say
that
if
you
want
to
work
on
any
of
these
issues
or
on
any
other,
please
leave
a
comment
on
the
issue
that
you're
working
on
it.
So
other
people
know
that,
like
someone
already
works
in
it
and
not
like
five
people
working
on
the
same
issue-
and
you
can
pick
someone
who
you
see
so
on
this
call.
F
E
F
Yeah,
so
I
have
like
gone
through
a
bit
of
code
of
the
main
rails
application
so
like
how
should
be
a
entry
point
for
a
developer
like
the
code
is
like
really
very
large
and
I
have
been
developing
in
ruby.
I
have
been
a
rails
developer
from
last
10
months
and
like
I
am
also
like
finding
a
core
bit
of
like
a
complex
so
like
how.
How
should
be
the
entry
point
for
a
new
developer
like.
A
That's
a
really
excellent
question,
nishank
and
in
fact
I
think,
anyone
who
comes
to
gitlab
wrestles
with
the
same
problem,
because
it
is
so
the
good
thing
about
gitlab
is
it
is
actually
it's
pretty
much
a
regular
rails.
App
like
it
follows
standard
rails
conventions
with
some
extensions
specific
to
gitlab,
but
you
know
it.
You
know
it's
got
models.
Views
controllers,
the
front
end
was
mostly
was
hamel.
We're
now
moving
to
most
mostly
of
ujs
front
end,
but
still
it's
fairly.
It's
still
fairly
standard.
A
So
to
answer
your
question
specifically,
you
would
let
the
the
issue
itself
drive
you.
So
if
I
was
to
work
on
a
new
issue,
I
would
try
to
first
understand
the
issue.
What
is
what
it's
actually
trying
to
ask
me
to
do,
and
then
I
would
search
through
the
code
base
and
try
and
find
the
location
in
the
the
code
where
that
issue
is,
is
relevant.
A
That
also
might
involve
looking
at
the
front
end
I'll,
come
to
how
to
set
up
your
local
workstation
in
just
a
minute
and
then
I
would
typically
start
with
finding
some
existing
tests
that
are
that
are
around
this
area
and
then
see
you
know.
If
I
change
this
test,
you
know,
will
it
cause
the
issue
or,
or
you
know,
I'd
either
drive
it
from
the
test
first
or
start
to
make
the
code
changes
and
then
run
the
tests
most
of
the
most
the
back
end
development.
You
can
do
really
without
doing
much.
A
A
A
Yeah,
so
let's,
let's
have
a
quick.
Let's
have
a
look
at
that
because
that's
really
important,
so
the
gitlab
development
kit
is
as
you're
saying
it's
basically
a
full
gitlab
instance.
That
includes
you,
know
our
external
monitoring
tools.
It's
basically
everything
but
designed
in
such
a
way
that
you
can.
You
can
develop
onto
it.
A
A
And
so
then
you
know
you
follow
these
commands
and
then
you
know
you,
but
you
basically
follow
those
commands.
You
pull
the
repo,
your
unmake
bootstrap,
you
install
the
gem
and
then
you
you
do
this
install
step.
So
then
you
then
what
you
have
is
you
have
a
full
gitlab
instance
running
natively
on
your
machine
which
you
can
develop
into
you
can
put
debugging
into
and
then
you
would
just
take
a
branch
against
that
repo
and
and
push
that
code.
F
Happened
during
time
like
first,
when
I
tried
I
stole,
I
forgot
to
do
like
stop
the
jdk,
and
I
was
not
able
to
access
the
port
3000
for
some
reason,
but
then,
like
I
have
again
gone
through
documentation
and
consumed.
Like
my
half
day
in
my
job,
where
I
was
working
like,
I
was
not
being
able
to
localhost.
My
rails
have
the
which,
on
which
I
am
working.
H
H
G
H
A
A
I
mean
the
point
of
the
gdk
is
that
it's
installed
natively
right
like
there
is
also,
I
think,
an
experimental
docker
compose
version
of
the
gdk
yeah.
It
is
experimental,
but
no,
I
haven't
specifically
noticed
that,
but
you
could
you
could.
Actually
you
could
open
an
issue
on
the
gdk
about
that
to
see
with
other
people
have
had
that.
Has
anyone
else
experienced
that.
E
Yeah
sean
yeah.
I
actually
want
to
hijack
the
sensor
yeah
actually
a
few
months
back.
First
of
all,
hey
diego
hey
max
to
your
family,
hello,
yeah.
So
a
few
months
back
yeah.
I
also
was
interested
in
that
it
was
slower.
Then
it
was
acceptable
to
me
and
what
I
did
first
of
all,
webpack
actually
consumes
a
lot
of
resources.
E
And
if
you
can
ping
me
on
this
issue
or
yeah,
just
ping
me
on
this
community
of
service
issue,
and
I
will
just
send
you
my
gdk
yaml
file,
which
contains
the
settings,
but
remember
that
you
sometimes
may
need
to
force
refresh
pages
after
that.
Just
because
I
guess
it
breaks
hot
reload
for
the
webpack.
But
I
don't
know
for
back-end
developer,
it's
not
so
important.
H
Now
I
will
just
say
what
I
mean
with
slow,
because
sometimes
you
know
when
you
hear
slow
it
just
can
be
a
lot
of
things,
so
the
the
actual
operations
daily
like
I
do
an
update
or
I
download
whatever
I
mean
it's,
it
was
never
so
fast
because
it
has
to
download
and
check
so
many
things.
Okay,
that's
understandable!
H
What
I
mean
is
that
every
time
that
I,
for
instance,
let's
say
I
make
notifications
in
something
or
I
change
branches,
and
I
want
to
restart.
That
is
what
takes
a
lot
more
longer.
Now
I
mean,
since
I
came
because
I
was
taking
a
long
hiatus
on
on
development
and
then
I
came
back
and
then
you
know
I
just
speak
about
starting
up
the
whole
rails
and
the
components
plus
maybe
spring,
because
I
want
to
have
it
for
development
takes
about
two
minutes.
D
H
E
Yeah
yeah,
actually,
I
was
solving
precisely
the
same
problem.
Basically
after
you
change
something
the
reload
time
can
take
a
lot
of
time,
and
especially
after
changing
branches,
you
need
to
restart
jdk
or
something
so
this
actually
webpack
settings
help
a
lot
with
that
and
yeah.
We
also
have
powerful
laptops,
but
gitlab
and
whole
jdk
consumes
a
lot
of
resources
as
well.
Unfortunately,.
A
A
D
C
D
B
One
trick
a
while
ago,
I
think
it
was
shinya
that
posted
about
it
was
that
you
can
disable
prometheus
metrics
in
the
gdk.
I
think
they're
enabled
by
default,
and
I
know
he
said
that
sped
things
up
a
lot
for
him
and
I
always
disable
them
and
they're
disabled
they're
enabled
by
default.
I
don't
know
if
I
haven't
really
noticed
that
huge
of
a
difference,
but
that's
something
else
to
try.
H
Well,
I
mean,
if
I
may
ask
something
else
related
to
gdk:
we
because
it
was
we
had
today
we
have
like
an
internal
meeting
with
the
open
source
and
enthusiasts
in
siemens,
and
there
was
talking
about
the
git
pod
and
we
have
seen
that
you
have,
or
somebody
is
working
on
udk
on
a
branch
over
that
so
just
want
to
get
your
feeling
about.
That.
Is
that
important
for
you
something
we
discuss
if
we
should
invest
some
time.
A
A
A
A
Okay,
so
so
you
could
cut
if
you
had
a
specific
topic
you
wanted
to
talk
about.
You
would
just
come
into
the
into
the
the
meeting
for
the
next
office
hours
and
just
put
in
your
question,
and
the
whole
meeting
could
center
around
one
question.
If
that
was
if
that
made
sense.
Of
course,
you
can
also
ping
us
at
any
time.