►
From YouTube: What is GitLab's Feature Deprecation Strategy?
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
I've
just
got
a
really
good
question.
What
is
our
deprecation
policy
for
features?
I
could
get
what
we
have
a
ton
of
features
to
our
product
and
it's
not
great.
If
you
don't
deprecated
any
of
them,
I
think.
What's
really
important
is
technical
debt
interest
rate
so
the
feature
that
is
in
there?
To
what
extent
does
it
prevent
future
features
from
being
added,
but
also
to
what
extent
is
it
affecting
new
features
and
existing
features
with
kind
of
code
that
could
be
cleaner?
A
Our
mission
of
gilt
lab
is
everyone
can
contribute
so
want
to
make
sure
that
every
time
we
you
make
a
feature,
it's
a
solid
base
for
people
to
build
on,
and
when
you
have
features
that
kind
of
are
widespread
in
the
code
base,
but
don't
have
a
lot
of
usage
that
whole
suspect,
I.
Think
the
most
from
memorable
one
for
me,
or
instance,
of
a
feature
who
deprecated
or
is
our
old
feature.
A
We
had
a
kind
of
chat
feature
we
can
post
messages
on
the
product
wall
wasn't
well
done,
but
it
was
very
prominent
in
the
interface
can
be.
You
can
have
code
that
boutique
no
code
also
kind
of
fqx,
that
we
decided
to
deprecated.
That
I
think
it's
a
great
idea
to
maybe
have
to
stay
for
you,
deprecated
things
and
I.
Think
when
we
do
that
we
should
kind
of
refer
to
our
definition
of
them.
For
example,
the
definition
of
done
we
say
features
should
be
orthogonal
to
other
features.
They
shouldn't
have
overlap.