►
From YouTube: GitLab 15.5 Kickoff - Enablement:Database
Description
Planning Issue: https://gitlab.com/gitlab-org/database-team/team-tasks/-/issues/269
A
Hey
everybody
welcome
to
the
database
group
15
5
kickoff.
A
You've
got
me
again
today,
because
our
acting
project
manager
gabe,
is
on
vacation,
so
yeah
here
I
am,
the
database
team
again
remains
at
40
capacity.
This
is
a
combination
of
both
plan
vacations
and
also
just
our
overall
capacity
issues.
So
our
head
count
is
supposed
to
be
eight
we're
currently
at
five,
which
includes
our
new
team
member
who
just
joined
so
I've
set
us
at
40
just
based
on
onboarding
and
other
things.
A
So
let
me
try
and
get
through
all
of
our
top
priorities
for
15.5,
so
we're
continuing
to
wrap
up
sort
of
the
end
bits
of
the
batch
background
migration
work.
Our
plan
is
to
finish
the
chat
ups
integration,
so
that
developers
internally
will
be
able
to
see
the
status
of
their
batch
migrations
and
understand
just
how
the
progress
is
going.
A
In
addition,
we've
got
a
couple
of
smaller
issues
around
batch
handling
and
then
some
final
issues
around
throttling
mechanics
and
then
one
bug
that
we've
we'd
like
to
address
this
milestone
around
which
schema
is
being
displayed
in
the
admin
panel.
On
the
ci
partitioning
support
side.
We
don't
have.
A
I
guess
oops
we're
picking
up
some
high
priority
issues
around
the
around
the
existing
migration
testing,
but
then
we
were
also
hoping
to
get
started.
Finally,
on
some
of
the
single
query:
testing
work,
which
we
believe
will
also
aid
the
ci
partitioning
effort,
so
that
we
can
identify
queries
that
lack
partitioning
keys,
not
just
ci
partitioning
everybody's
partitioning.
Well,
I
mean
everybody
who
wants
to
partition,
let's
see,
and
then
we
have
two
high
priority
issues
that
we're
hoping
to
look
at
this
milestone.
A
One
of
them
is
an
issue
where
database
migrations
in
production
are
failing
at
the
end,
due
to
a
failure
to
release
an
advisory
law,
so
we're
still
investigating
what's
causing
that.
But
it's
not
it's
not
causing
a
ton
of
problems.
Rerunning
the
job
seems
to
be
fine,
so
the
other
thing
we're
working
on
is
recording
alloy
db
usage
in
usage
pane
so
that
we
can
track
whether
or
not
we
have
customers
who
have
adopted
that
platform
yeah.
A
I
that's
that's
a
lot
of
stuff.
I
will
be
hopeful
that
we
can
get
to
a
larger
percentage
of
it,
but
we
will
see
thanks
everybody
and
have
a,
I
think.
That's
all
I
have
to
share
today
so
have
a
really
good
day.