►
From YouTube: GitLab 11.2 Retrospective
A
So
the
first
question
is:
why
are
we
doing
this
on
Google
Hangouts,
the
the
question?
Oh
the
exact
reason,
but
people
ops
has
asked
us
to
use
Google,
Hangouts
and
YouTube
instead
of
zoom
for
or
retro
zemerik
and
of
the
retros
retrospective
and
the
kickoff
every
month.
So
if
there's
any
further
questions
or
why
we're
doing
this,
please
directly
to
that
selectional
or
create
an
issue
I
think
that's
the
best
place
to
immediate
that
I
believed
that
there
were
some
problems
with
streaming,
but
I
can't
beat.
A
It
can
be
totally
certain,
so
I
don't
want
to
misspeak,
but
please
go
ahead
and
enter
your
questions
and
comments.
There.
Sean
has
posted
a
link
to
this
retrospective
for
the
plan
team,
so
he's
encouraging
other
folks
to
do
the
same
and
I
believe
that
there
is
a
handbook
process
that
all
teams
should
be
doing
that
anyways.
So
if
nothing
else
in
terms
of
housekeeping
I
will
turn
it
over
to
Eliseo.
B
Thanks
Victor,
so
previously
the
respective
improvement
task.
We
had
a
problem
with
the
server
get
0
3,
which
was
breaking
all
the
production
deployments.
Last
month,
I'm
had
find
out
that
it
was
a
zero
extension
called
Linux
and
Gnostic.
That
was
constantly
installing
this.
This
broken
package,
but
yeah.
Now
we
move
to
GCP.
So
this
is
no
longer
a
problem,
but
it
was
fixed
even
before
moving
to
GCP.
So
next
point
is
Robert.
Thanks.
C
Leslie,
oh
not
too
much
to
take.
Here's
work
on
this
kind
of
got
sidetracked
during
the
summit.
We're
still
working
towards
adding
feature
flags
for
pretty
much
all
new
features
is
the
plan
eventually
we're
going
to
start
with
the
bat
commenting
feature
as
a
testbed,
which
is
now
scheduled
for
10.4.
C
A
A
D
So
this
is
what
we
well
this
route
that
a
month,
but
for
the
last
year
I
guess:
we've
been
working,
two
works
using
no
more
Ana
fests
for
get
access,
and
today
we
unmount
it
most
NFS
drives,
which
is
a
huge
milestone,
at
least
for
to
get
any
team,
but
I
would
say
for
the
whole
kid
lock,
as
one
NFS
drive
used
to
be
able
to
take
the
whole,
get
that
down
and
I
wanted
everyone
to
be
aware.
This
will
also
impacts
our
customers
from
the
next
release
forwards.
E
Thanks
CJ
and
that's
that's
a
huge
milestone,
no
more
effort.
Nfs
is
great.
So
my
item
was
just
to
kind
of
celebrate
that
we
took
a
learning
from
the
Crete
summit
2017
and
applied
it
to
this
2018
summit.
We
did
some
pre-release
city
planning
to
take
into
account
the
lower
bandwidth
that
all
teams
would
have.
This
happened,
I
believe
back
in
July
and
that
seemed
to
have
a
positive
impact.
E
There
were
less
fire
drills
and
there
was
less
to
sort
of
trade
off
because
it
wasn't
a
fully
packed
release
to
begin
with,
and
that
we
want
to
make
sure
to
do
this
going
forward
for
future
summits
or
future
events,
where
you
might
have
dramatically
less
capacity
to
go
so
I'm.
What
went
wrong
Bob
is
not
on
the
call
James
if
you're
there.
Maybe
you
want
to
speak
to
this
I.
F
So,
yes,
we
had
a
security
patch
that
we
couldn't
release
in
all
of
DRC,
so
we
had
to
keep
do
doing
post
deploy
patch
patches,
which
was
not
ideal.
So
some
questions
there
should
we
have
take
off
apply
post
deployment
patches.
Actually,
we
probably
should
want
to
consider
how
we
can
change
our
processes
to
not
have
to
do
any
sort
of
post
deployment
patches,
because
that
has
been
proven
to
be
problematic,
but
we
are
moving
towards
more
of
deploying
with
with
chat
up
soon,
so
we'll
see
how
that
will
go
further.
F
E
F
E
Thanks
this
is
a
really
minor
thing,
but
we
didn't
bump
the
the
version
number.
So
production
read,
RC
I
think
it
was
10
or
11
for
about
a
week.
So
bookkeeping
was
something
that
we
want
to
make
sure
we
do
well.
There
was
a
proposal
to
a
hot
passion,
but
we
did
make
the
call
to
just
manage
risk
that
we
weren't
going
to
do
another,
deploy
with
people
getting
on
airplanes
just
for
a
version.
Number
I
think
that
was
the
right
call,
but
something
minor
that
we
should
be
able
to
take
into
account
next
time.
G
A
G
Where
do
we
start
I
get
to
go
back
to
the
I'll
just
start
with
what
went
wrong.
Yeah
I
think
the
two
main
things
is
that
LDAP
Wan
was
annoying.
People
were
not
able
to
clone
with
LDAP
enabled
because
it
was
a
regression
in
there
and
everybody
was
on
a
plane,
I
think
at
that
time,
and
then
the
second
one.
It
was
just
a
bug
that
was
around
for
two
weeks
and
then
we
had
I
think
mark
Fletcher
triage,
like
ten
other
issues
that
people
was
at
hey.
G
This
is
a
problem
but
and
basically
closed
all
these
other
issues,
but
nobody
I
was
able
to
fix
it
in
time.
So
again,
this
happened.
I
think
that
the
the
the
second
problem
happened
two
weeks
before
in
an
RC
and
just
and
I,
don't
think
anybody
had
got
around
to
fixing
it
I
mean
part
of
it
lends
itself
to
the
capacity
that
we
be
released
on
the
22nd,
and
then
we
had
no
nobody
really
around
for
that
to
kind
of
fix
support
issues.
So
that's
all
I
wanted
to
bring
up.
G
But
what
went
well
I
want
to
go
talk
about
dodgy
speed.
Migration,
I
think
generally
went
well,
I
think
you
know
we
rehearsed
over
and
over
and
found
a
lot
of
issues
and
in
the
end
it
went
smoothly.
There
were
a
bunch
of
things
that
didn't
get
migrated
over
after
the
Geo
migration,
but
we
were
addressing
those
in
11:3.
G
So,
for
example,
like
the
default
branch
for
repositories,
we
had
about
200,000
depositors
that
didn't
have
if
somebody
changed
the
default
branch
from
one
thing
to
another,
it
wasn't
replicated,
but
we
went
back
and
just
resync
them.
So
I
think
that
is
solved
and
we're
pushing
out
a
fix
from
11:3
to
handle
that.
D
Yeah
so
somewhat
obvious,
I
guess,
but
just
just
to
mention
it's
not
everyone
that
wants
to
talk,
join
the
call
or
some
dropped
out
and
couldn't
rejoin,
because
we
hit
the
limits
or
15
participants,
apparently
well,
I'm,
not
sure
if
we
can
either
like
pay
Google
to
have
more
participants
or
if
we
refer
it
back
to
zoom
or
what
the
reasons
were
to
use
hangouts.
But
it's
something
we
should
investigate.
E
The
victor
is
this:
something
you'd
be
able
to
work
out
with
with
people
ups
I
mean
we
tried
this
experiment.
It
seems
like
the
the
live
stream
is
presumably
working,
but
we're
not
able
to
collaborate
effectively.
So
maybe
you
could
work
out
with
them
defaulting
going
back
to
zoom
or
maybe
raising
the
limits
in
hangouts.