►
From YouTube: GitLab 13.0 Kickoff - Configure:Configure
Description
Read more at https://gitlab.com/gitlab-org/configure/general/-/issues/48
A
Oh,
hello,
my
name
is
Victor
Nutt
and
I
am
the
product
manager
of
the
configure
group.
You
are
currently
watching
the
13.0
release
kick-off
video
for
the
configure
group.
Let's
the
start,
we
have
three
goals
in
this
release.
Our
primary
top
goal
is
to
get
the
breaking
changes
that
we
would
like
to
introduce
into
the
next
release.
A
Why
it's
important
for
us
for
several
reasons
every
year
this
is
the
only
occasion
man
we
can
introduce
these
changes,
and
we
have
a
few
developments
that
we're
already
asking
for
these
changes
for
a
while,
and
we
have
a
few
developments
as
well
ever
before,
say
needs
to
be
necessary
to
add
to
the
product
in
order
to
allow
us
to
move
forward
in
the
next
year.
What
are
these
staged
changes.
A
First
of
all,
we
have
a
new
version
of
the
Piscataqua
chart
in
our
code
base
for
a
while
and
in
the
next
release
we
are
going
to
deprecated
our
previous
chart.
This
might
affect
you.
If
you
are
using
the
previous
positive
sequel
versions,
we
are
trying
to
move
quite
a
few
checks
around
this,
that
it
should
affect
people,
and
you
should
be
able
to
use
the
previous
version
or
you
should
be
warned
if
you,
if
you
want
to
use
the
new
version
as
well
at
the
same
time,
but
in
either
case.
A
A
A
A
The
final
breaking
change
we
have
is
rated
to
our
two
deployments
to
Cabana
tees
that
we
use
right
now
even
also
develop
some
other
parts
of
the
code
base.
Right
now
we
use
the
deployment
API
version,
extensions
beta
one,
and
we
are
going
to
move
this
to
deployment
API
version
XV
one.
Why
are
we
doing
this?
First
of
all,
we
would
like
to
add
comment.
This
1.16
support
to
get
lab
and
increment
this
one
to
16.
The
previous
beta
api
is
deprecated.
A
So
in
order
to
support
the
new
cuentas
version,
we
want
to
duplicate
the
old
version
as
well.
This
will
affect
you
if
you
are
either
using
Aventis.
Compare
this
version
doesn't
support
this
version,
which
is
pre
unlikely,
because
the
apps
v1
version
was
introduced.
Increment
is
1.9,
and
even
today
the
get
lab
requirement
is
1
to
12,
but
it
might
affect
you
as
well.
If
in
any
place
in
your
code
base,
you
are
actually
using
the
the
extensions
beta
1
api,
we
recommend
you
to
upgrade
to
the
apps
v1
in
this
case
as
well.
A
These
were
our
breaking
changes.
Our
second
goal
is
related
to
our
generic
kubernetes
management
and
integration.
We
think
that
our
current
solution
shows
very
well
small
businesses
and
companies
who
are
just
starting.
They
commented
journey.
On
the
other
hand,
it's
not
suitable
for
large-scale
serious
enterprise
usage.
They
would
like
to
change
this,
and
for
that
we
are
going
to
run
a
design
sprint
inside
the
company.
If
you
would
like
to
have
an
influence
on
this,
please
reach
out
to
me.
A
A
A
A
These
were
the
developments
that
are
straight
related
to
our
goals
in
the
configure
group,
and
we
have
one
more
deliverable
development
for
you
as
part
of
the
many
features,
the
18
features
that
are
being
moved
to
get
LabCorp
from
the
Enterprise
Edition.
We
are
moving
deploy
boards
to
core
and
we
plan
to
do
is
in
13.0
as
well.
A
If
you
look
at
our
planning
issue,
you
might
see
a
few
more
items
here
as
well.
Some
are
just
the
breaking
down
the
previous
issues,
I
described,
but
a
few
others
to
those
others
are
definitely
stretch
goals
for
us.
They
are
related
either
to
the
upgrade
of
ham
to
two
hand
free
in
our
stack
and
two
minor
kubernetes
UI
improvements
all
around
the
each
lab
UI.
Thank
you
very
much
for
attention.