►
From YouTube: GitLab 13.0 Kickoff - Enablement:Distribution
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
Hi
and
welcome
to
the
13-point
kickoff
for
distribution,
I'm,
Larissa,
Lane
I'm,
the
product
manager
for
distribution.
We're
really
excited
about
this
release,
it's
one
that
we've
been
waiting
on
for
a
while.
It
allows
us
to
add
some
big
new
features
that
will
be
unlocking
even
more
improvements
that
we'll
be
making
over
the
coming
months.
So
13
point:
oh,
it's!
A
Our
annual
major
releases
get
lab
and
we
have
a
lot
of
little
things
going
in
that
require
a
major
release
and
also
a
handful
of
big
things
that
I'm
going
to
focus
on,
and
so
the
first
thing
I
want
to
talk
about
is
we
will
be
minimally
requiring
PostgreSQL
11
as
of
get
eleven.
Thirteen
point-
oh-
and
this
is
very
exciting
for
us,
because
it
means
that
we
can
start
building
on
some
of
the
features
that
were
added
in
PostgreSQL
11.
A
That
will
lead
to
some
fairly
significant
performance
improvements
in
the
database,
so
the
database
team
is
going
to
be
picking
up
a
lot
of
that
work
and
you'll
be
hearing
about
that
in
the
coming
few
months,
as
they
start
to
make
progress
on
that.
It
does
mean
that
we're
removing
the
older
versions
of
Postgres,
so
9.6
and
10
will
be
removed
in
get
lab
13.
A
That
means
that
you
need
upgrade
to
Postgres
11
before
you
can
upgrade
to
13
point.
Oh,
so
we're
focusing
on
writing
some
really
good
documentation
on
how
to
do
that.
In
1210
we
defaulted
to
PostgreSQL
11,
so
providing
that
you're
not
using
high
availability
or
geo.
You
would
have
been
auto
operated
to
Postgres
11
in
1210.
If
you
are
using
a
che
and
geo,
there
are
some
manual
steps
involved,
and
so
we
documented
those
in
the
1210
release
post
to
give
us
some
guidance.
There.
A
So
the
next
big
thing
that
13-point
Oh
brings
us
is
defaulting
to
Puma
as
the
web
server.
We
have
been
doing
a
lot
of
testing
of
Puma,
mostly
on
the
memory
team,
and
have
seen
some
significant
performance
improvements
from
the
multi-threading
that's
available
in
Kumar,
and
we're
really
pleased
to
be
able
to
make
the
switch
from
unicorn
to
PMI
in
this
release.
A
Unicorn
will
still
be
available,
but
we
will
be
defaulting
to
P
long
and
then
we
have
been
working
on
some
testing
around
adding
Patroni
as
a
different
third-party
tool
for
managing
replication
and
failover
in
a
high
availability,
install
of
gate
lab
we're
going
to
continue
to
do
more
testing
of
Patroni
and
13.0.
So
we'll
be
testing
things
like
what
is
the
migration
path
from
our
existing
tool,
which
is
recommended
to
move
across
chip
attorney?
A
Patroni?
We're
really
happy
to
be
adding
this.
It
does
allow
us
to
start
building
our
cascading
replication,
which
is
a
great
thing
for
geo
for
using
geo.
It
allows
you
to
have
high
availability
on
your
post
coast,
databases
on
your
geo
secondary
because
it
supports
replicating
from
a
read
only
database
to
your
standby
databases
on
the
secondary.
A
A
Our
current
version
of
rep
manager
that
we
have
been
using
doesn't
support
PostgreSQL
12,
so
we
either
had
to
upgrade
rep
manager
or
switch
over
to
Patroni
because
of
some
other
advantages
we
get
with
Patroni.
We
decided
to
make
that
switch,
and
so
it
won't
be
available
for
use
quite
yet,
but
we're
getting
very
close
and
then
finally,
we've
been
doing
a
lot
of
work
on
the
orchestrator
tool
and
the
orchestrator
is
a
tool
to
help
you
automatically
deploy
and
configure
the
nodes.
A
You
need
for
high
availability
for
scaling
out
from
single
node
to
multi
node
and
for
configuring
geo.
It's
going
to
be
a
huge
time.
Saver.
We're
all
really
excited
about
it
and
we're
starting
to
see
some
really
good
progress
being
made
on
that
tool.
One
of
the
things
that
we
have
scheduled
for
13.0
is
to
record
some
demos
of
the
tool
on
YouTube
and
we
hope
that
you
check
them
out
and
give
us
some
feedback
we're
really
looking
forward
to
getting
that
out
into
the
world.
So
thank
you.