►
From YouTube: GitLab 16.1 Kickoff - Enablement:Gitaly
Description
Kickoff Issue - https://gitlab.com/gitlab-org/gitaly-planning/release-planning/-/issues/11
A
A
This
Milestone
is
pretty
full
for
us.
We
have
standard
capacity,
but
it
is
a
full
Milestone
regardless
some
of
the
objectives
and
themes
that
are,
in
addition
to
the
ones
outline
in
our
Direction,
page
or
sort
of
in
conjunction
with,
are
to
improved
object,
pool
design.
This
is
a
long-term
goal
for
us
and
it's
to
allow
object,
pools
to
work
in
a
clustered
world
so
to
work
better
with
giddly
cluster
as
we're
moving
toward
a
better
implementation
of
clustering
through
a
raft-based
decentralized
architecture.
A
One
of
the
things
we
really
need
to
figure
out
is
how
to
improve
this
object,
pool
design
to
work
better
and
right
now
we
are
starting
in
this
work.
There's
two
items
scheduled
for
this
release,
both
of
which
should
get
us
the
first
steps
toward
improving
object,
pools
and
their
Design
Within
git
lab.
So
that's
pretty
exciting.
A
Now
the
second
objective
we're
looking
to
satisfy
is
to
implement
right
ahead
logging
in
giddly.
This
is
a
multi-milestone
effort.
We
are
working
on
support
database
for
storage
and
partition
manager.
That's
the
issue
we're
scheduled
for
this
release.
This
is
really
important
to
us,
because
not
only
does
it
move
toward
a
raft-based,
decentralized,
architectures,
I
discussed
above,
which
is
very
important.
A
Finally,
I
shouldn't
say
finally,
actually
next
we
have
the
Implement
better
secret.
Passing
to
prefect
giddly
already
supports
passing
Secrets
via
a
user
configuration
command.
However,
prefect
does
not,
which
means
that
TLS
certificates
currently
need
to
be
passed
to
pre-effect
and
plain
text,
we're
going
to
fix
that
you've
under
this
issue
here.
This
is
something
that
we've
been
meaning
to
do
and
we
are
planning
on
getting
it
done
this
release
and
now
finally,
we're
going
to
finalize
the
role
of
geometric
repacking.
This
is
a
really
exciting
feature
for
us.
A
The
team
has
worked
tremendously
hard
over
the
past
couple
of
releases
to
complete
this.
It
is
rolled
out.
All
that's
left
to
really
do
is
default.
The
feature
flag
to
enabled
so
we're
very
excited
for
that.
There's
a
couple
things
that
we
should
talk
about
here.
A
The
two
big
takeaways
here
that
we're
really
proud
of
is
there's
close
to
a
10x
Improvement
in
time
spent
optimizing
repositories
that
have
high
activity,
which
is
a
huge
performance
Improvement
for
us,
and
overall
there's
between
a
10
and
30
estimated
Improvement
in
time
spent
repacking
objects.
So
the
effort
done
by
the
team
here
has
really
done
gone,
a
long
ways
to
improve
performance
and
that's
something
we're
very,
very
excited
to
have
as
generally
available
in
defaulted
to
on.
A
So
that's
the
finalization
of
that
in
this
release
and
I
am
very
proud
of
this
team
engineering
priorities.
A
We've
noticed
there's
a
lack
of
improvements
in
our
documentation
around
the
gidly
rpcs
and
we've
we've
seen
several
sort
of
support
requests
to
the
team
for
this
we've
gone
ahead
and
created
an
epic
here
to
improve
documentation
around
the
geely
rpcs
and
that
epic
sort
of
goes
through
and
outlines
all
of
the
different
rpcs
we
feel
could
use
improved
help
in
doing
that,
we're
going
to
try
to
schedule
a
few
each
release
and
we're
looking
to
complete
these,
as
you
can
see
somewhere
around
August
time
frame.
A
So
for
this
current
Milestone,
we
are
looking
at
doing
the
following
three
improvements
to
our
documentation.
I
additionally
would
like
to
better
document
the
process
around
how
environment
variables
are
utilized
during
security
release
processes.
So
we've
got
that
on
our
plate,
as
well
as
an
additional
documentation
release
and
we're
also
looking
to
improve
structured
error
handling
for
some
of
our
rpcs.
So
this
is
all
maintenance
work,
that's
really
important
to
the
team
and
it
helps
us
to
make
our
product
better
and
easier
to
maintain.
A
Finally,
we
have
a
list
of
quality
priorities
here.
These
came
out
of
a
bug:
prioritization
science
dashboard,
which
is
internal
only
our
quality,
stable
counterpart,
has
done
an
excellent
job
of
prioritizing
things,
and
we've
chosen
these
five
items
at
the
top
of
the
list.
If
we
have
additional
time,
we
will
continue
moving
down
the
list.
However,
given
that
we
are
a
very
tight
release
and
with
a
lot
of
things
on
our
plate,
we're
setting
a
goal
to
achieve
these
five.
These
should
help
improve
customer
experience.
These
are
customer
tagged
and
they
have
higher
severity.
A
So
these
are
things
we'd
like
to
get
rid
of
out
of
the
backlog
and
get
done
and
fixed
and
move
on.
If
there's
any
feedback
or
questions,
please
don't
hesitate
to
either
leave
a
comment
on
this
video
or
to
come
to
this
planning
issue
and
leave
comments
here.
I
will
leave
a
link
to
this
in
the
planning,
video
or
in
the
video,
so
that
it's
easy
to
find,
and
we
welcome
your
collaboration.
Thank
you
so
much
for
your
time
and
please
enjoy
the
Gilly
16
1
release
with
us
as
we
go
through
this.