►
From YouTube: GitLab 14.4 Kickoff - Release
Description
This video is the GitLab 14.4 Milestone Kickoff for the Release Group
Planning issue - https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/80
A
In
this
milestone.
We
have
four
things
across
different
issues
that
we
are
going
to
aim
to
deliver
number
one:
we're
gonna
resolve
all
existing
gitlab
database,
sharding
issues
that
the
release
group
is
responsible
for.
Second,
we're
going
to
add
some
limitations
to
gitlab
pages.
A
So
we
can
understand
better
how
our
customers
are
using
our
products,
let's
dive
into
the
details,
so
the
release
group
is
participating
in
a
gitlab
wide
initiative
to
make
our
databases
more
performant,
so
some
the
work
that
we're
taking
on
is
removing
cross
joints,
disallowing
the
possibility
of
having
orphaned,
ids
and,
lastly,
removing
cross
db
modification.
A
A
A
Some
of
the
bugs
we're
taking
on
includes
a
general
usability
improvement.
Sometimes
in
certain
cases
your
users
are
not
able
to
download
release
evidence.
Sometimes
the
release
asset
link
is
not
generated
when
certain
events
occur.
We're
going
to
remove
we're
going
to
try
to
address
all
our
all
of
the
highest
severity
issues
we
currently
have
in
our
backlog
in
the
sprint.
A
When
it
comes
to
instrumentation,
currently
we
count
the
release
groups
smell
or
stage
monthly
active
users
as
users
who
have
interacted
with
the
pipeline
that
has
an
environment
inside
of
it,
because
the
environment
is
a
proxy
for
a
user.
That's
using
gitlab
release
features,
while
this
is
a
good
starting
point,
it
under
counts.
A
Just
a
preview
here,
we're
going
to
show
the
most
pertinent
buttons
with
appropriate
context
right
from
the
get-go
for
capability.
That's
used
less
often
they're
going
to
be
hidden
behind
this
kebab
menu.
A
A
That
is
a
little
bit
dated
in
this
case,
despite
it
being
deployed
more
recently,
you
will
be
further
down
the
list,
so
we're
going
to
change
that
to
the
most
recent
deployment
as
a
default
sorting
option
looking
forward
a
bit
we're
going
to
continue
to
redesign
the
environment
page
to
make
it
more
user-friendly,
currently
oftentimes,
it's
really
difficult
to
see.
A
What's
what
on
the
environment
page
based
on
the
table
layout
that
the
environment
page
currently
has
we're
going
to
change
that
up,
make
it
useful,
no
matter
how
big
your
screen
size
is
other
improvement
that
we
have
coming
up
that
we're
designing
for
currently
is.
In
14.3
we
introduce
the
concept
group
level
configuration
for
protected
environments.
This
allows
organizations
to
separate
developers
from
operators,
so
developers
cannot
simply
easily
deploy
to
whatever
environments
within
the
single
group.