►
From YouTube: GitLab 15.6 Kickoff - Enablement:Gitaly
Description
Gitaly team kickoff for GitLab 15.6.
- Link to Planning Issue - https://gitlab.com/gitlab-org/gitaly-planning/release-planning/-/issues/4
A
A
Just
to
let
everyone
know
under
capacity,
the
Italy
team
has
officially
been
broken
down
into
two
sub
teams,
which
we're
really
excited
about.
One
team
called
get
team
and
one
team
called
the
cluster
team,
and
the
intent
of
this
is
to
allow
the
get
team
to
focus
solely
on
the
implementation
of
git
Upstream
changes
that
we
can
contribute
back
into
the
broader
git
community
and
changes
in
our
architecture
to
allow
better
performance
and
better
bug
fixes
for
gitlab
utilizing
giddly
the
project.
A
One
of
the
big
things
we're
looking
at
working
on
and
this
sort
of
fits
with
the
clustering
I
was
talking
about
above,
is
the
decentralization
decentralized
architecture
for
Ghillie
cluster.
Well,
there's
an
epic
linked
here
in
this
issue
that
I'm
showing
right
now
the
planning
issue
which
will
be
linked
below
this
video.
We
have
completed
an
architectural
review.
We've
had
staff
engineering,
take
a
look
at
it.
We've
had
multiple
other
independent
reviewers.
Take
a
look
at
it.
We're
really
excited
that.
Overall,
we
received
some
really
good
feedback.
A
There
are
some
areas
of
risk
that
we're
looking
to
remediate
and
that's
very
good
news
for
us.
We
also
know
there's
some
architectural
fixes
needed
to
move
toward
this
decentralized
architecture.
We
have
an
epic
about
that
right
here
and
we're
trying
to
schedule
these
fixes
in
immediately
starting
in
15-6.
So
some
of
the
cluster
teams
work
in
15
6
will
be
helping
to
burn
down
some
of
this
or
technical
debt.
We
need
to
complete
prior
to
moving
to
a
more
decentralized
architecture.
A
I've
listed
a
few
specific
issues.
We
intend
to
work
on
this
release
and
perhaps
more
will
fit
in
the
release
as
well
as
far
as
features
and
improvements.
The
get
team
is
really
anxious
to
optimize.
Our
repository,
optimization
schema.
There's
been
some
good
discussion
around
this
in
our
off-site
meeting
about
a
month
and
a
half
ago
and
we're
anxious
to
sort
of
see
how
this
will
help
optimize
the
repositories
we
store
for
all
of
our
customers
and
how
our
self-managed
customers
store
their
repositories.
A
This
is
going
to
go
into
15
6
as
the
plan
and
there'll
be
more
information,
as
we
understand
better
how
this
impacts
our
customers,
but
for
right
now
it
should
allow
us
to
have
the
Run
housekeeping
tasks
run
in
a
more
consistent
manner.
That
is
more
understandable.
So
this
will
also
allow
eager
repacking,
which
is
a
really
good
thing.
A
Also,
we're
really
excited
that
we
can
contribute
to
Upstream
kit.
This
is
sort
of
the
charter
of
our
git
team
is
to
continue
that
Upstream
get
contribution
Trend
to
broaden
and
improve
the
overarching
product.
We
have
three
things
that
we're
looking
to
do
from
an
upstream
get
contributions
perspective.
Now
these
don't
really
follow
our
standard
Milestones,
so
git
is
released
on
its
own
release
cycle.
A
However,
we
plan
on
working
on
them
during
this
Milestone,
which
is
why
I'm,
including
them
here
in
the
planning
one
of
the
most
exciting
ones,
is
to
help
us
Upstream.
The
blame
tree
I've
heard
that's
been
ongoing.
This
was
an
effort
that
was
started
by
multiple
gig
contributors
and
multiple
areas,
and
it's
something
that
we
get
lab
are
hoping
to
sort
of
get
on
board
with
help,
with
reviews
help
to
continue
the
upstreaming
of
this
and
to
better
the
overall
get
product.
There
are
also
two
other
aspects
to
this.
A
One
is
we're
looking
to
set
up
some
gitlab
CI,
and
this
is
to
help
us
during
our
contribution
phase
to
Upstream
git.
This
is
more
of
an
internal
issue
to
to
allow
us
to
contribute
in
a
better
manner,
we're
also
looking
to
enable
get
repack
to
filter
objects,
which
is
another
ongoing
thing,
that's
being
done
in
the
get
lab
mailing
or
the
get
mailing
list.
A
There's
also
a
list
of
bugs
scheduled
for
this
release.
I
can
open
this
up
and
show
you.
This
is
a
filtered
list.
These
bugs
were
planning
on
fixing
this
release
as
well.
We've
worked
in
collaboration
with
our
software
engineer
and
test
to
come
up
with
this
list,
hoping
to
burn
down
these
bugs
and
ensure
that
we're
meeting
SLO
on
every
available
opportunity.
A
These
are
all
different
priorities,
but
in
general
we
have
no
Priority
One
severity,
One
issues
right
now
we
do
have
a
handful
of
priority
two
severity.
Two
and
those
are
the
ones
we're
taking
care
of
at
the
top
of
this
list,
and
as
you
go
down,
you
see,
we
also
are
taking
care
of
some
priority
and
severity,
three
bugs.