►
From YouTube: GitLab 16.2 Kickoff - Enablement:Gitaly
Description
The GitLab 16.2 release for Gitaly is primarily a catch-up release. The goal of this release is to devote time to the in-flight efforts, while adding minimal new work.
The release planning issue is - https://gitlab.com/gitlab-org/gitaly-planning/release-planning/-/issues/12
A
Good
day,
everyone
and
welcome
to
the
getaway
16.2
planning.
This
is
the
release
for
the
July
of
2023
getlab.com.
This
release,
the
Italy
team,
has
an
expected
capacity
to
be
pretty
much
normal.
We
know
there's
some
PTO
here
and
there,
but
nothing
out
of
the
ordinary
and
therefore
we
do
not
think
that
any
extended
planning
that
we
know
about
or
extended
PTO
that
we
know
about
will
impact
our
planning
as
far
as
planning
inputs
go.
This
release.
A
We
are
adding
just
a
very
small
quantity
of
bug
fixes
just
to
let
me
maintain
our
performance
on
those.
We
don't
want
to
fall
behind
or
Miss
SLO
on
those.
So
we
are
working
very
hard
to
just
sort
of
finish
up
what's
in
flight,
so
to
give
you
a
flavor
for
what's
going
on
and
what's
in
Flight
I'll
go
ahead
and
look
back
at
the
16-1
planning
issue.
A
We
are
currently
in
the
midst
of
implementing
right
ahead
logging
in
Italy.
This
is
critical
for
multiple
things
in
the
infrastructure
and
it's
on
an
ongoing
off
road.
So
we're
working
on
that
we're
also
making
some
dramatic
improvements
to
object,
pool
design
with
the
goal
of
improving
object,
pools
to
work
in
a
more
clustered
world.
Both
of
these
things
have
been
ongoing
and
as
such,
we
want
to
ensure
that
we're
giving
them
the
attention
they
deserve,
while
not
sort
of
filling
our
backlog
with
things
that
have
unrealistic
milestones.
A
So
that
is
our
plan
for
16.2.
I
will
also
note
that
there
are
a
handful
of
issues
shares
brought
up
through
our
quad
planning
exercise.
A
handful
of
these
bugs
are
already
in
16-2
and
the
items
that
look
to
be
missed.
Slo.
We
are
planning
on
implementing
in
16-2
as
well,
so
we
don't
fall
further
behind.
As
always.
If
there's
any
questions,
please
let
me
know
we're
excited
to
kind
of
catch
up
and
re-plan
for
16-3
we
have
some
exciting
functionality,
we're
looking
to
improve,
and
it's
right
now
going
to
land
in
16-3.