►
From YouTube: Support Release Review - 13.1
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
A
B
B
A
Okay,
we
are
two
minutes
past
the
start
time,
so
I'm
gonna
kick
this
off,
so
welcome
everyone.
It's
another
monthly
release
review
party.
Thank
you
to
everyone!
That's
here!
Thank
you
to
everyone
that
has
volunteered
to
go
over
some
of
the
new
features
that
are
in
13.1,
I'm.
Gonna
start
us
off
today
by
passing
across
to
Mike,
who
has
the
first
few
points.
Mike
take
his
way
aim.
C
C
C
True
did
everybody
notice
the
issues
sticking
at
the
top
of
the
page
when
you
scroll
down
I,
found
that
really
really
helpful,
because
I'm
flipping
between
different
issues
and
used
to
have
to
scroll
top
to
see
what
it
was,
because
the
title
bars
usually
say
small
when
you
got
dabs
and
I
haven't,
played
with
the
editor
config
in
the
web
IDE.
But
it
sounds
cool
if
it's
there.
C
Especially
for
Yama
files,
cuz
I'm,
terrible
with
EML
files
and
getting
the
spacing
all
wrong,
and
the
last
one
I
think
is
a
gotcha
that
we
should
watch
out
for
for
clients.
Who've
got
multiple
kid
giddily
clusters,
because
at
the
moment,
if
it
detects
that
one
of
the
nodes
in
the
cluster
doesn't
doesn't
keep
up,
it'll
turn
the
whole
cluster
into
read-only.
A
I'll,
take
that
as
No
thank
you.
Mike
get
any
clusters
really
exciting
because,
as
with
deprecating
NFS
support,
that
is
going
to
be
the
future
for
anyone
that
needs
some
kind
of
scalability
in
there
get
the
environment.
So
that's
awesome
and
thank
you
for
having
a
bit
of
a
play
around
with
that
up.
Next
is
Alex.
D
D
Unfortunately,
I
don't
have
a
demo
for
you
today,
but
I
would
advise
you
to
go
through
the
docks
and
overall
it
looks
like
a
pretty
big
feature.
The
idea
is
that
now
you
can
configure
alerts
from
third-party
services
for
from
get
replenished
Prometheus
and
from
external
parameters
on
project
level,
so
it's
available
from
operations
alerts
yeah.
D
So
any
details
can
be
found
in
the
attached
dock
I
haven't
yet
seen
any
tickets
regarding
it,
but
we'll
see
if
it
looks
like
a
pretty
big
one,
a
lot
of
a
lot
of
work
was
done
in
this
direction
seems,
and
the
next
point
is
about
audit
events
of
improvements.
I
think,
from
time
to
time,
we
have
seen
that
your
new
staff
is
added
to
the
audits
event
section
and
right
now
we
can
see
that
if
SSH
key
was
created
using
API.
B
D
A
B
So
I
have
taken
some
easy
ones,
but
pretty
cool
ones,
I
would
say.
I
was
expecting
these
features
to
make
developers
like
easy.
So
first
it
starts
with
the
design
management
that
we
have
added
recently
earlier.
What
we
used
to
have
is
like
we
can
simply
add
it
up
comment
and
we
can
have
a
chain
of
threads,
but
now,
as
like
issues,
we
also
have
the
option
of
marking.
The
thread
is
resolved,
so
basically
a
discussion
that
stays
can
be
marked
as
resolved.
B
B
It's
like
any
other
way
of
resolving,
or
you
can
say,
could
be
better
and
I
can
simply
state
it's
all
trend
and
that's
it
voila.
You
have
a
cleanest
way
of
issue
management
in
designs
now
so
yep,
that
is
about
a
unique
feature
for
designers.
I
see
designers
using
it
pretty
heavily
internally,
and
it
helps
them
a
lot.
B
So
this
is
design
management
issue
resolve
them.
For
you,
makhani
design
thread
is
resolved
any
questions
on
this
one
going
one
twice.
Alright,
next
one
is
cold
intelligence
again
to
make
developers
life
pretty
easy.
Cold
intelligence
has
been
involved
in
13.1,
so
what
it
basically
does
is
it
basically
creates
a
drop-down
or
you
can
say,
an
auto
suggest
where
it
talks
about
the
definition
of
of
the
code.
B
It
basically
uses
an
external
library
called
source
draft.
The
implementation
is
pretty
simple.
All
you
need
to
add
is
snippet
water
doesn't
talk
about,
is
it
requires
go
so
basically
we
do
in
needs
to
have
go
installed
on
your
other
runner
or
or
if
they
should
have
go
image
included
to
get
it
working.
A
simple
working
example
could
be
this
where
I
can
have
run
this
pipeline,
and
if
you
look
at
any
of
the
code
definition,
it
gives
you
the
entire
definition
about
the
code
and
where
is
it
coming
from?
B
It
can
take
him
to
that
result.
So
this
particular
code
definition
is
coming
from
Prometheus,
so
this
is
pretty
cool
and
pretty
handy,
if
you,
if
you
are
and
look
at
the
code,
the
browser
that
is
really
helpful.
So
yeah
yeah
do
you?
Did
you
mean
to
share
your
screen?
Oh
damn
it
I
was
not
sharing
my
screen
mode
in
that
time.
Oh
my
god!
So
sorry,
you.
C
B
I'll
start
again:
:
televisions,
simple
snippet,
add
this
snippet
to
your
code
include
a
gold
package
as
well
image
as
well.
If
you
want
to
get
this
running,
if
you
don't
have,
it
will
fail,
it
will
ask
for
the
scry
for
the
go
image
not
available
on
your
machine.
So
first
you
need
to
do
run.
This
snippet
add
this
snippet
in
your
pie,
cime
file.
It
basically
uses
a
third-party
application
which
supports
only
currently.
B
It
only
supports
go
java
screen
type
scripts,
and
it
also
has
an
indexers
for
a
couple
of
other
languages
which
covers
almost
all
of
them,
but
yeah
there
are
fumes
still
remaining.
So
take
a
look
of
that
you,
after
you
run
a
simple
snippet.
All
you
can
see
is
underlined
dots
on
all
the
metal
definitions
and
when
you
click
it
will
talk
about
that
method
that
what
this
method
is-
and
you
can
go
to
the
definition
of
the
method.
B
This
project
requires
golang
and
because
to
get
it
compiled
it
is.
It
has
a
dependency,
because
if
you
look
at
the
school
definition,
it
says
that
it
requires
LSI
of
go
so
I'm,
assuming
that
and
it
is
compiling
a
go
package.
So
no
like
what,
if
you
use
like
the
type
script
of
the
Java
Script
I,
think
in
that
case
you
would
just
need
to
I,
don't
know
if
that's
also
go
package
or
not
I'm,
just
looking
at
the
dogs.
B
So
if
you
look
at
this
particular
code,
definition
I'm
just
going
by
the
definition
what
they
have
mentioned
because
I'm
doing
it
I
believe
what
I'm
doing
is
I'm
just
calling
a
go
package
and
that
I'm
compiling
so
maybe
yeah
I
haven't
tried
that,
but
definitely
I
give
this
a
try.
And
let
us
know
if
you
find
any
cool
stuff.
C
Do
you
know
if
the
L
SIF
is?
This
is
the
same
thing
that
is
used
by
intellisense.
B
B
A
No
okay,
like
we're
going
to
have
a
very,
very
quick
release
review
party
in
this
week,
especially
after
last
month's
epic,
which
was
$13.
Does
anyone
have
anything
else
that
they'd
want
to
go
over
today?
Anything
else?
They
want
to
call
out
anything
that
maybe
didn't
make
it
into
the
agenda
doc.
But
you
want
to
take
a
few
minutes
now
to
to
review.
C
Okay,
so
satisfy
requirements
from
a
CI
job.
I
didn't
really
understand
the
demo
video
here
cuz,
it
seemed
like
they
were
just
maybe
they
were
just
using
dummy
tests,
but
this
is
about
requirements,
management
in
github
and
being
able
to
mark
off
the
requirement
as
satisfied
based
on
the
outcome
of
a
job
I
think.
C
But
what
I
didn't
understand
was
how
is
the
job
actually
determining
whether
the
requirement
is
satisfied?
It
looked
like
it
was
just
a
manual
step
for
the
reviewer
to
say:
yep,
cool
and
I
wondered
if
anyone
knew
if
there
was
any
more
smarts
behind
that
or
if
it
was
just
basically
putting
a
manual
review
into
a
pipeline
I.
B
Did
it
a
little
bit
go
through
on
this
one
I'm,
not
hundred
percent
sure,
but
this
is
something
that
if
you
want
to
test
your
pipeline
for
some
things
and
it
is
requiring
an
extra
external
dependencies,
you
can
mark
that
dependency
as
solved
and
you
can
say
a
satisfy
requirements,
and
so
it
will
skip
that
part
and
just
run
that
particular
code.
So
that
is
what
I
am
standing,
but
yeah
I
always
need
to
give
this
a
try
and
eat.
C
Mic
no
I
was
just
hoping
somebody
understood
it
better
than
I
did
fair.
A
A
Okay,
I
think
that's
it.
We're
done
very
quickly
twenty
minutes
today
and
we're
done.
Thank
you
very
much
to
those
that
presented.
Thank
you
very
much
to
everyone
else
that
came
along
to
see.
Some
of
the
highlights
of
the
new
release
have
a
great
rest
of
your
days
wherever
you
are,
and
we
will
catch
up
in
the
course
of
the
week.
Take
everyone.