►
From YouTube: Release - Milestone Kickoff 14.3
Description
This is the Milestone overview for the GitLab Release Group.
Planning Issue - https://gitlab.com/gitlab-com/Product/-/issues/2947#note_649031493
A
B
All
right
so
for
design
work
in
this
milestone.
The
first
order
of
the
day
is
to
keep
working
on
the
problem:
validation
for
the
environments.
Page,
that's
a
survey!
That's
going
live
really
soon
within
the
environments
page
and
will
give
us
direct
user
feedback
on
how
users
are
interacting.
With
that
page.
It
falls
in
line
with
the
broader
team
that
we're
working
towards
of
environments
management
to
improve
the
environments
page.
B
While
that's
not
finished,
we'll
also
work
on
approval
actions
for
for
manual
actions
on
the
environments
page
as
well,
letting
users
know
they
have
excessive
stale
environments,
an
ongoing
problem.
We
have
and
a
smaller
issue,
to
make
the
deploy
to
button
more
clear
on
the
environments.
Page
there's
a
few
stretch
goals
if
we
manage
to
run
through
these,
but
essentially
the
continued
team
is
to
keep
improving
the
environments
page.
So
this
first
issue
with
the
feedback
will
be
really
important
for
us
moving
forward.
A
The
page's
migration
and
the
architecture
work,
and
also
we
are
really
focused
on
sas
reliability
and
scalability,
so
you'll
see
in
our
p1
or
top
priority
work.
Most
of
it
is
to
complete
pages
migration,
such
as
removing
support
for
disk
configuration
as
a
source,
removing
the
logic
that
was
previously
in
there
for
the
legacy
architecture.
A
We
are.
We
also
have
some
top
priority
issues.
Getlab
is
going
through
some
database
re-architecture
work
so
that
we
can
shard
our
databases
more
effectively
and
the
release
group
is
participating
in
that
effort.
So
you'll
see
these
two
issues
associated
to
that
effort
when
it
comes
to
p2,
we
have
some
feature
work
now,
the
first
of
which
is
enforcing
the
execution
order
of
resource
groups.
So
resource
groups
are
a
really
useful
feature
in
that
they
guarantee
that
different
jobs
can't
work
on
can
work
simultaneously.
A
A
Next,
we're
working
on
an
issue
that
changes
how
releases
are
used
by
guest
users,
so
releases
can
be
really
useful
for
guest
users,
who
are
not
part
of
a
project,
but
who
wants
to
understand,
what's
coming
up
next,
what's
being
released,
all
the
information
pertaining
to
pertaining
to
a
release
could
be
interesting
across
the
board,
not
just
to
users,
not
just
to
users
who
are
actively
working
on
a
project.
Currently,
this
is
not
possible
because
tag
names
are
treated
as
code
and,
since
guests
can
access
these
tag
names.
That
means
they
can't
access
releases
period.
A
A
A
Instead
of
letting
those
environments
sit
around
and
take
up
space
take
a
memory
when
it's
being
executed,
you
can
lead
to
problems
down
the
line.
So
we're
going
to
add
this
page
when
we're
going
to
add
this
button
to
clean
up
environments
when
people
click
on
that
clean
up
environment,
spot
button,
they're
going
to
see
the
option
to
clean
up
old
environments
or
deploy
environments
without
deployments,
and
when
the
user
clicks
clean
up,
those
environments
will
be
removed.