►
From YouTube: 12 3 Kickoff for Release
Description
12.3 Release Kickoff: Release
Release Direction: https://about.gitlab.com/direction/release/
Kickoff Document: https://docs.google.com/document/d/1ElPkZ90A8ey_iOkTvUs_ByMlwKK6NAB2VOK5835wYK0/edit#
Issues:
Add feature flag permissions* https://gitlab.com/gitlab-org/gitlab-ee/issues/8239
Improve pages load wait time experience https://gitlab.com/gitlab-org/gitlab-ce/issues/65304
Allow milestone(s) to be associated with a release* https://gitlab.com/gitlab-org/gitlab-ce/issues/62402
Speed up Pages initialization time by using configuration API* https://gitlab.com/gitlab-org/gitlab-ce/issues/61929
A
So
the
first
item
that
we
would
discuss
is
adding
feature
flag
permissions
in
version
12.2,
we'll
be
releasing
%
rollout
and
or
enabling
feature
flag
for
a
specific
user
ID
or
several
IDs.
Now
the
next
phase
would
be
to
enable
feature
flags,
/
environments,
and
this
basically
means
that
whoever
has
permission
to
deploy
to
an
environment
will
now
have
the
permission,
also
to
turn
on
and
off
feature
flights
to
that
specific
environments.
A
If
we
drill
down
into
protected
environments,
where
we're
very
scared
that
a
user
would
not,
that
shouldn't
be
able
to
deploy
that
environment,
we
don't
want
them
messing
around
with
our
feature
flags.
So
the
way
that
it's
going
to
look
and
I'll
show
you
a
sneak
peek
into
the
UI
is
basically
now
when
you
edit
a
feature
flag.
You
can
see
that
environments
below
where
they
were
enabled,
and
if
you
have
permissions
you
can
toggle
them
on
or
off
you
can
edit
the
name.
A
A
In
addition,
if
you
were
to
try
to
edit
or
rename
the
name
of
description,
you
would
see
the
following
banner
and
says:
they're
not
allowed
sighted
in
because
you
don't
have
the
appropriate
permissions.
And
finally,
if
you're
a
user
that
doesn't
have
permissions
and
you
attempt
to
delete
a
feature
flag,
you
would
not
be
able
to,
and
you
see
an
additional
pop-up
that
says
you're
not
allowed
to.
Of
course,
if
you
do
have
the
appropriate
permissions,
you
will
be
enabled
to
delete
the
feature
flag
from
your
specific
environment.
A
Our
next
item
is
improve
page
load,
wait,
time,
experience
and
basically,
we've
been
receiving
lots
of
complaints
from
the
community,
but
also
internally,
that
working
with
pages
is
very
confusing,
especially
if
the
first
time
you're
you're
working
with
it.
Sometimes
it
can
take
up
to
30
minutes
for
the
page
to
load
without
the
user,
getting
any
indication
of
what's
going
on
at
the
end
of
the
day,
but
get
congratulations
message
when
when
it
goes
live,
but
up
until
that
face
there's
you
have
no
idea
what's
going
on,
so
what
we
did.
A
The
next
item
would
be
to
allow
milestones
to
be
associated
with
a
specific
issue,
so
something
that
we've
been
dealing
with
also
internally
and
get
that,
but
something
that
we've
also
heard
from
the
community
is
that
sometimes
there
are
several
milestones
that
are
associated
to
a
specific
release.
So
we're
now
giving
you
the
capability
to
connect
a
milestone
or,
more
than
one
mile,
stop
to
a
release
and
again,
we'll
show
you
a
sneak
peek
to
the
UI.
We're
going
to
be
adding
this
to
several
different
pages.
A
We
believe
this
will
help
release
orchestration
and
give
you
some
clarity
about.
What's
going
on
on
and
release,
the
last
item
that
we
are
going
to
discuss
today
is
feeding
pages
initialization
time
by
using
configuration
API,
if
you
recall
and
12.2,
are
going
to
be
releasing
this
new
api,
which
should
basically
speed
up
the
pages
performance
substantially.
We
mentioned
that
the
pages
could
take
up
to
30
minutes
to
load.
This
will
kind
of
change
this
to
work
instant
statements
continuously.
A
A
In
any
case,
those
are
the
four
items
that
we're
going
to
be
releasing
in
the
release
stage.
Please
feel
free
to
comment
on
any
of
the
items
in
the
lab
or
that
are
connected
to
this
depth
to
the
kickoff
document.
If
you
don't
feel
free
to
comment
directly
on
the
issues,
please
email
me
directly
at
Pogo,
Lewinsky
and
calm
and
I'd
be
happy
to
take
it
one
on
one
with
you.