►
From YouTube: GitLab Team Retrospective Summary 13.6
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
A
A
So
under
the
praise
for
this
retrospective
craig
gomez
from
the
memory
group
said,
the
memory
group
spent
a
very
focused
week
exploring
ways
to
drastically
reduce
the
memory
footprint
for
running
gitlab.
In
a
memory
constrained
environment,
we
had
daily
recaps
to
facilitate
a
quick
feedback
loop
and
to
determine
next
steps
for
more
information.
Refer
to
this
slide,
roman
cuba
said
we
did
an
excellent
job
around
helping
to
get
rid
of
the
ace
editor
in
all
of
git
lab.
It
took
months
of
hard
work
and
I
really
want
to
praise
them
for
that.
A
Cz
cz
from
the
global
search
team
said
that
the
team
produced
a
kickoff
video
collaboratively
thanks
to
john
who
organized
the
effort,
dan
or
john
under
from
plan,
said
participating
in
the
product
shadow
program.
Where
an
engineer
shadows,
a
pm
for
48
hours
was
a
great
experience
and
highly
recommended
for
the
different
perspectives.
It
gives
note
this
is
the
second
successful
run
for
the
program
which
was
initiated
by
charlie
abbott
abele.
This
mri
will
make
it
available
to
other
teams.
Sounds
like
a
really
good.
A
Results
cz
from
global
search.
Again
we
were
able
to
ship
a
few
features
successfully.
We
can
now
constrain
tests
to
run
in
a
specified
pipeline.
For
example,
this
elastic
search
test
only
runs
in
the
nightly
pipeline.
The
sidebar
on
the
search
results
page
has
been
completed
for
more
information.
Refer
to
the
slide,
john
hope
from
plan
said
the
team
took
pride
in
shipping.
A
A
What
went
well
with
iteration
cz
from
global
search
said
we
were
seeing
faster
code
review
and
reduced
review
to
merge
time
nick
from
geo
said
akriti
and
douglas
collaborate
with
sre
counterparts
to
complete
a
first
iteration
of
a
failed
over
test
to
the
geo
node
on
staging.
This
was
the
first
goal
of
the
disaster
recovery
working
group.
Congratulations.
A
A
Cheryl
from
verify
said,
a
qa
test
broke
on
master,
but
was
not
flagged
ahead
of
time
that
a
set
review
was
required
on
the
mr
prior
to
merging
the
tests
are
manually
run
so
we'll
look
at
ways
to
improve
failure.
Detection
of
qa
tests
affected
by
merged
future,
mrs
under
efficiency,
heinrich
from
plan,
mentioned
the
feature
flag.
Rollout
issues
are
adding
additional
overhead
that
feels
unnecessary
for
small
features
when
we
just
want
to
limit
risk.
A
Nicole
williams
from
release
said
that
the
team
realignment
occurring
midway
through
the
milestone
was
taxing
on
the
team
in
terms
of
transitioning
remaining
work,
while
picking
up
new
responsibilities.
That
being
said,
they
all
did
a
great
job.
Supporting
each
other
and
seeing
the
work
through
to
completion
as
much
as
possible,
how
can
we
improve
all
right
collaboration?
A
A
Craig
from
memory
said,
the
memory
group
is
discussing
how
we
can
introduce,
show
and
tells
to
our
weekly
cadence
and
lindsey
from
threat
management
said.
There
is
a
lot
of
interest
in
creating
more
opportunities
for
pair
programming,
both
within
the
team
and
with
community
contributor
contributors.
A
We
plan
to
create
a
spreadsheet
where
engineers
can
schedule
sessions
focused
on
individual
issues.
A
link
to
the
spreadsheet
will
be
shared
in
slack,
applicable
handbook
pages
and
on
our
threat
management.
Wiki
pages
information
about
individual
parent
sessions
should
also
be
communicated
directly
in
the
issue
results
craig
for
the
memory
team
said
memory.
Profiling
is
difficult
to
quote
mattias
a
lot
to
quote
matthias.
A
A
How
can
we
improve
from
david
on
efficiency
from
the
monitor
team,
as
we
now
have
a
large
amount
of
maintainers
on
our
team?
We
are
looking
into
a
better
method
for
handling
time
management
when
balancing
reviews
with
feature
deployment,
development
and
under
transparency
nick
said,
we
have
not
done
any
acceptance,
demos
for
a
while
and
plan
to
start
doing
them
on
a
more
regular
basis.
A
Our
in-progress
work
on
patrony
support
and
maintenance
mode
are
two
examples
where
the
increased
visibility
of
a
team
demo
would
be
very
helpful
thanks
for
your
time.
Please
join
us
for
the
retrospective
discussion
for
the
retrospective
discussion.
We
will
be
hosting
that
or
I
will
be
hosting
that
on
monday
december
7th
and
this
time
around,
I
used
polypole
to
gather
feedback
on
our
discussion
questions
I
decided.
A
Well,
you
all
decided
on
choice
three
and
four,
so
we
will
be
discussing
sharing
your
best
practices
for
creating
issues
that
appeal
to
community
contributors,
as
well
as
sharing
ideas
for
how
to
provide
ideas
for
strengthening
dip
values.
On
your
team,
please
refer
to
the
slide
for
additional
links.