►
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
Hello,
everybody,
my
name
is
Roger,
and
this
is
the
application
performance
groups
16.4
plan.
A
issue
with
me
today
is
Paul
hello,
Paul,
hello,
cool,
so
we'll
just
go
through
really
quickly.
A
So
over
the
past
couple
Milestones,
the
application
performance
team
has
been
working
on
enabling
code
suggestions
for
self-managed
as
part
of
our
theme
to
bring
AI
related
features
to
our
self-managed
customers
through
a
cloud
connector
we're
going
to
begin
enforcing
Cloud
licensing
requirements
for
self-managed
instances,
starting
in
16.3
and
in
16-4,
we'll
continue
our
efforts
to
bring
in
coach
just
the
maturity,
as
well
as
spending
time
debugging
issues
and
supporting
issues
with
early
adoption,
customers
on
the
new
authentication
flow
and
finalizing
instrumentation
and
tracking
our
general
release
plan
over
the
next
several
months
is
to
finalize
work
on
code
suggestions,
followed
by
Vietnam
chat
and
then
suggested
reviewers
in
that
sequence
in
16-4.
A
We're
going
to
start
looking
at
some
of
the
work
required
for
gitlab
chat
as
the
efforts
for
code
suggestions
is
starting
to
becoming
more
and
more
crystallized
and
use
cases
are
starting
to
become
adopted
by
by
increasing
numbers
of
customers.
So,
specifically,
there
are
three
outcomes
that
we're
looking
for.
First
up,
we
want
to
improve
code
suggestion
metrics
for
self-managed
instances.
We
currently
have
some
tracking
information
via
system
logs.
However,
we
still
lack
alignment
between
how
to
track
this
data
consistently
between
SAS
and
self-manage.
A
So
our
goal
is
to
continue
working
on
this
and
make
sure
that
this
data
is
eventually
surfaced
within
slash
Tableau
for
business
Analytics.
Another
specific
outcome
we're
looking
for
is
to
deprecate
some
of
our
initial
iteration.
One
authentication
flow
16.3
supports
a
new
authentication
flow
and
it
is
also
the
only
release
where
we
will
support
both
the
Old
and
the
new
authentication
flow.
This
works
well
because
it
is
a
required
upgrade
stops
and
we
intend
to
advise
customers
to
use
16.3
to
transition
to
the
new
authentication
flow
in
case
any
actions
are
required
by
them.
A
As
a
result,
we
believe
that
in
16
4,
all
instances
and
users
will
be
on
the
new
offline
with
so
as
part
of
this
Milestone
we'll
be
removing
support
for
our
Legacy
iteration
one
authentication
and
cleanup
related
code
paths.
Lastly,
we
talked
earlier
about
supporting
gitlab
chat.
We
don't
really
know
what
this
means.
There's
a
lot
of
ambiguity
for
our
team
still,
so
our
goal
here
is
to
explore
and
formulate
a
plan
of
action
for
how
we
will
enable
gitlab
chat
for
self-managed
instances,
depending
on
what
we
think
the
effort
of
this
might
be.
A
We
might
actually
start
working
on
this
plan
in
16.4
and
we'll
start
taking
a
look
at
what
actual
signs
of
effort.
This
is
going
to
require
and
formulate
an
estimate
for
how
many
additional
Milestones
it'll
take
before
we
can
bring
gitlab
chat
in
a
beta
state
to
self-managed
customers.
Paul.
Is
there
anything
else
you
want
to
add
to
this
one
nope
I,
don't
think
so.
I
think
oh
good
great
job
Roger.
Thank
you
very
much
for
all
your
support,
all
right
cool.
Well.
Thank
you
folks.
This
is
our
planning
issue
for
16.4.