►
From YouTube: Support Release Review Party - 12.10
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
B
B
B
B
B
B
C
You
guys,
like
the
on
track
attention
yeah,
so
this
is
actually
the
new
feature
that
application
every
and
each
without
checking.
So
what
I
have
here
is
an
epic
and
then
I
have
a
static
as
well.
So
this
is
a
Saturday
and
then
these
are
issues,
so
you
can
see
that
for
each
epic
you
have
like
some
statelessness
as
well
and
for
each
even
for
stop
a
picture,
those
incidents
and
then
these
videos,
which
are
actually
activated
from
the
issue
itself,
so
that
help
it
yourself.
C
C
So
you
just
edit
and
they
can
choose
no
status
on
track
these
attention
at
risk,
so
yeah
I
think
that's
all
to
it.
So
just
a
bit
on
the
new
station
I'm,
actually
using
this
to
sort
of
well,
as
it
looks
like
track,
which
items
I
think:
okay,
which
I
don't
need
attention
which
items
probably
in
a
state
where
no
one
knows
how
to
do
it.
It's
like
I'm,
getting
the
actual.
C
Use
case
they
our
customers
might
have
all
users
might
have
to
differ
from
case
to
case,
because
these
are
just
basically
a
kind
of
labor
and
then
it's
up
to
the
project
manager
or
the
user
to
actually
people
need
what
they
want.
The
levers
to
actually
mean,
as
far
as
I
can
tell
there's
no
other
related
functionality
to
this.
Yet
so
it's
fairly
informational
for
project
managers-
or
you
know
he
uses.
E
Was
reading
Chloe
and
the
documentation
for
this
and
there's
a
note
in
the
documentation
saying
that
so
this
feature
is
under
the
feature
flag
at
the
moment
and
if
we
go
to
the
documentation
and
in
the
documentation,
well,
it's
enabled
by
default,
but
the
documentation
says
in
some
cases
this
feature
is
incompatible
with
all
configuration.
I
have
no
idea
what
this
means.
There
is
no
description,
so
if
you
go
to
the
bottom
there,
however,
in
some
case
a.
E
C
E
C
C
C
E
C
E
G
G
So
basically
the
first
is
is
quite
simple:
all
you
need
to
do
is
click
this
import
from
genre
and
start
process.
So
let's
do
that
you
need
to
create
a
new
project
or
you
can
use
an
existing
project
if
you
wish,
but
you've
got
a
nice
import
issues
button
here
now,
if
you
haven't
previously
set
up
the
gyro
integration,
you'll
need
to
do
that
first
and
likely
for
me,
I'm
prepared
so
I
have
all
the
settings
relevant
to
this
right
here.
G
G
Things
like
comments
was
the
first
thing,
I
noticed
wasn't
being
pulled
through,
but
things
like
climb
tracking
labels
whose
assign
to
it-
that's
not
all
true,
as
you
can
see
here,
but
it
does
pull
through
some
of
the
metadata
here,
which
is
which
is
good
and
I.
Think
it's
a
good
start
to
importing
Java
issues
and
of
course
you
can
click
here
and
it
goes
through
to
the
actual
Shiro
issue.
So
that's
quite
a
nice
little
thing
to
have
that's
basically
that
employed
in
a
nutshell.
G
G
So
you
can
see,
there's
a
lot
terms
or
here
so
feel
free
to
have
a
surf
through,
but
you
can
see
that
the
majority
and
the
Minimum
Viable
Product
was
introduced
into
our
team
and
this
graph,
the
features
being
introduced
in
gilead
13,
mainly
others,
things
like
setting
up
user
mapping
importing
comments
from
juror
I
think
I
saw
one
about
labels.
Earlier
today,
so
that's
all
in
the
works.
So
yeah,
that's
basically
the
feature
in
a
nutshell.
So
does
anyone
have
any
questions.
I
B
E
What's
the
difference
because
I
feel
like
we
can
import
JIRA
issues
previously
right,
but
I
think
the
difference
now
is
that
we
can
do
it
for
a
DUI
instead
of
an
API
is
that
is
that
what
the
improvement
actually
is?
I
was
always
I
was
going
through
this
and
I'm
like
I,
feel
like
we've
done
it
in
the
past.
Right,
like
customer,
can
actually
import.
Jira
issues
really
does
anyone?
Yes,.
G
Andrey
I
think
you're
correct,
so
ok
I
actually
read
through
this
your
overview,
just
before
the
call
and
I'm
glad
I
did
you
as
I
prepare
for
your
arm
question
there.
There
is
a
blog
post
from
get
lab
that
details
important
JIRA
issues
via
the
API,
so
what
I'll
do
is
I'll.
That's
just
give
me
a
moment.
I'll
add
that
to
the
document,
so
that
was
back
in
2017,
but
I
think
you
know.
G
E
Yeah
well,
I
think
maybe
the
thing
that
well,
this
is
the
first
iteration
or
the
built-in
feature
for
the
import
right
and
I.
Think
you
mentioned
about
there's
an
epic
with
a
list
of
different
things
that
it's
not
important
just
yet
right,
because
it's
like
ongoing,
so
development,
yeah,
I,
think
if
there
it's
like
a
customer
asking
or
like
I
want
to
do
it
right
now,
it's
they
still
probably
can
do
it
via
the
API
side
of
things.
G
Yeah,
the
other
thing
that
I
was
thinking
of
doing
after
this
core
was
actually
add
to
the
documentation
that
these
are
the
limitations
of
the
importer
at
the
moment
and
here's
a
link
to
the
epic
and
also,
if
you
want
to
use
the
API
method,
then
I'll
link
to
the
blog
post
as
well
and
I.
Think
they
at
least.
C
Cool
so
I
I
do
see
her.
Another
question
there,
which
is
wonder
where
we
are
going
after
this
I
can
provide.
I,
can
provide
a
very,
very
high-level
overview
of
what's
actually
happening
there,
because
last
night
I
spent
a
bit
of
time
reading
report
from
our
pricing
consultants.
I,
don't
think
this
is
confidential
because
it
is
purely
real
to
the
products
trilogy
and
not
to
pricing,
so
I
will
share
it.
So
what
happens?
C
Is
that
we've
we
found
out
through
some
casting
interviews
that
the
price
of
gala
of
Tina
actually
takes
up
most
of
most
engineering
departments,
tooling
budget
and
guess
what
it
also
takes.
That
budget
is
JIRA.
So
the
idea
is
that
you
want
to
get
our
own
plan
features
to
be
as
much
as
possible,
so
they
can
tell
these
customers
that
hey
you
no
longer
need
JIRA,
don't
pay
them
the
exorbitant
fees
that
they
are
charging.
You
use
awesome,
State
and
get
ultimate
so
and.
E
Met
a
bunch
of
friends
who
are
developing
like
stuff
and
they
using
JIRA,
and
they
do
mention
to
me
as
well
like
I,
want
to
move
to
get
lab,
but
I
got
so
much
things
going
on
in
gear
on
right.
Now,
it's
just
really
hard
for
them
to
move
me
show
us
I
mean
this
is
obvious,
like
need
or
just
friends
right.
So
it's
interesting
that
you
get
that
sort
of
not
you'll,
be
dead,
nuts
and
spin,
which
all
these
things
that
I
wrote
and
all
this
question
that
I
have
on
that.
E
I
wrote
on
the
on
my
overview.
That's
just
like
my
question
in
my
head.
So,
like
you
don't
have
to
answer
it.
It's
just
like
me
being
curious,
while
I'm
reading
this
and
just
writing
things
down,
if
I
would
have
write
it
somewhere
else,
so
I
just
might
as
well
write
it
here.
So
you
don't
have
to
answer
all
of
this.
It's
just
me
talking
to
myself
really
but
you're.
Anything
thanks,
I.
J
This
is
because
we
heavily
use
both
in
my
previous
company,
so
I'm
interested
in
how
it
love
integrated
circuit
wall
and
I'm
I'm
underwhelmed
with
the
feature,
because
it's
not
as
integrated
as
I
thought.
So
this
is
an
example.
Pipeline
I
did
where
I'm
getting
the
variables
from
both
and
if
you
can
see,
we
still
need
to
manually
run
work
demands
so
I
took
the
get
lab,
will
do
it
behind
the
scenes,
but
you
would
need
to
configure
your
get
lab.
J
See
Ida
PML
to
manually
get
the
variables
you've
set
in
the
poll,
and
the
initial
setup
is
also
quite
cumbersome.
So,
first
you
will
need
to
create
a
secret
where
you
will
store
the
password,
then
you
will
need
to
create
a
policy
that
has
read
access
to
the
secret,
then,
after
that
you
will
have
to
configure
a
role
for
the
JWT.
J
In
this
case,
I
limited
the
get
lab
to
only
access
to
be
able
to
access
this
password
when
the
branch
is
mastered,
is
the
master
branch,
so
I
have
to
run
so.
This
first
run
is
the
master
branch,
so,
as
you
can
see,
it
managed
to
get
the
password
successfully
and
in
this
one
it's
running
on
a
different
branch
and
it
didn't
manage
to
get
the
password
because
of
the
different
bound
claims.
So
behind
the
scenes
get
the
pieces
in
GWT
and
it
also
cost
a
regression
in
the
12.10.
J
So
I
will
just
like
to
share
this
to
you.
Some
of
our
customers
doesn't
have
the
Open
ID
key,
say,
and
if
it
doesn't
exist
there,
no
jobs
would
be
able
to
run
because
gitlab
will
fail.
With
this
error,
there's
already
a
emerge
request
for
this
and
I
think
they're
planning
a
patch
release
for
this
book.
So
if
you
enter
the
customer
with
this
error,
the
reason
is
that
they
probably
didn't
have
the
open,
Ida
connect
key
set.
E
J
C
J
H
J
E
Nothing
I
would
say
that
from
get
calm,
the
potential
problem
if
they
bring
their
own
Runner,
but
if
they
have
their
own
runner
and
the
own
runner
doesn't
have
the
open,
idk
I,
don't
know
how
many
people
actually
bring
their
own
Runner
and
get
calm.
But
if
that's
the
case,
there
would
be
the
same
problem.
Is
any
children,
I.
J
K
D
H
H
A
J
There's
already
a
fix,
so
I
think
they're
preparing
it
for
the
next
batch
release.
So
this
is
the
open
I'll,
be
connect,
signing
key,
that's
missing,
so
they
probably
generate
generating
the
secrets
to
be
used
since
I.
Think
Omnibus
will
automatically
create
this
since
I
didn't
have
to
do
anything,
don't
figure
the
both
integration.
H
J
L
E
Have
some
technical
question
that
I
don't
know
if
this
is
gonna,
be
too
long
or
this
particular
call
it?
I
was
just
trying
to
figure
out
how
the
the
whole
vault
secret
actually
works.
So
based
on
your
example,
just
now
you
were,
you
were
saving
a
secret
variable
called
password
with
be
a
dollar
sign.
Dollar
sign
word
right,
so
that
was
the
secret
that
you
kept
right.
Yeah
I
said
that
yeah,
that's
the
secret
okay
and
then
you're
creating
a
role
and
that
particular
role.
E
J
E
J
E
E
So
said
so,
and
when
you
introduce
the
policy
to
begin
with,
there
is
some
sort
of
configuration
where
yeah
it's
basically
I
got
two
FA
conformation.
Basically
right,
that's
pretty
cool,
that's
pretty
cool,
okay!
Okay!
Now
it
makes
sense.
I
was
like
when
I
read
that
I
was
trying
to
make
sense
like
wait.
You
can
just
like
that
but
pay
the
JSON
payload,
but
okay.
This
is
five
minutes.
Then
I
guess
you
can
configure
that
for
like
I,
don't
know
a
minute
or
whatever
timeframe
you
need
it
right:
yeah,
okay,
so
yeah!
E
Okay,
now
the
time
name,
it's
interesting
all
right!
Yeah
again,
this
is
like
a
very
detailed
thing
that
I,
probably
outside
the
context
of
this
call
I
was
just
wondering
like
so
what
happened?
If
you
have
like
say
this
is
five
minutes
right
like
the
default
is
five
minute.
So
if
you
run
the
pipeline
for
half
an
hour
and
you
needed
the
password
later
on
after
after
five
minutes
in
in
the
10th
minute
or
the
15
minute,
would
that
still
work
actually.
E
What
I
meant
this?
It's
not
about
the
education,
it's
about
the
token
expiry
right.
The
token
expires
five
minutes.
So
again,
this
is
a
very
detailed
like
we're.
Looking
for
how
we
implement
how
we
actually
draw
the
password
from
because,
like
is
the
place,
is
the
secret
stuff
was
drawn
in
the
beginning
of
of
the
job
yeah,
which
you
draw
it
in
the
beginning
of
the
job?
The
variable
will
be
available
throughout
the
Troy.
M
M
M
M
M
M
M
M
E
H
Yep,
so
we
have
an
interesting,
really
interesting
feature.
That
is
another
step
towards
of
providing
a
complete
order.
Web
solution,
that
is
the
Club
Status
page.
So
if
you
all
aware
that
we
do
have
a
Status
page
from
the
club.com,
that
is,
that
shows
the
current
status
of
all
the
nodes
and
also
talks
about
any
incident
that
happens
so
instead
of
relying
on
any
third-party
tool,
the
clap
has
developed
its
own.
That
is
get
lab,
Status
page.
H
What
it
does
is,
basically,
you
have
to
enable
that
get
lab
status
paste
feature
for
a
specific
project,
and
once
it
is
done,
you
can
publish
those
issues
directly
from
the
issue
tracker
to
a
static
website
that
will
tell
the
users
about
the
status
updates.
So
basically
it
is
for
users
to
how
it
works.
It's
fairly
simple.
H
There
is
great
lab
instance,
a
project
enabled
with
status
update
and
that
will
trigger
a
background
job
whenever
a
new
issue
is
created
within
that
project
and
that
will
publish
that
on
your
s3
bucket
and
s3
bucket
is
currently
by
default,
enabled
with
serving
static
website.
So
currently
this
is
only
supported
with
AWS.
So
no
other
tool
I
figured
out
a
couple
of
things
that
are
not
that
mysterion
the
documentation
I'll
make
an
update
on
that.
H
So
what
you
need
to
do
is
UniFirst
need
to
create
a
bucket
on
s3
and
you
need
to
supply
some
policies.
This
is
not
fairly
like
fairly
simple
documented.
Then
we
have
to
come
to
the
Status
page
project.
What
you
can
do
is
you
can
create
clone
the
current
status
page
project
that
we
have.
You
can
simply
mirror
that
on
your
instance
and
start
using
it
once
done,
you
need
to
configure
your
CIC
variables.
H
I
have
done
that
everything,
so
I
am
NOT
going
to
take
much
of
your
time
and
you
can
it's
pretty
straightforward,
so
I'm
just
going
to
the
documentation,
and
once
done,
you
just
need
to
activate
the
status
page,
how
this
active.
Once
you
have
activated
the
status
page,
you
can
simply
create.
Let's
say:
I,
have
this
status
page
project
and
in
the
operation
side
you
can
see
there
is
a
tab
called
status
page.
All
you
need
to
set
up
is
make
it
activate
and
provide
your
AWS
access
key
and
secret
key.
H
Once
this
is
done,
whenever
you
are
publishing
any
issue,
it
will
directly
get
published
on
your
status
page.
That
is
there
on
s3,
so
you
can
also
see
the
full
report.
So
let's
say
you
are
working
on
an
issue
and
you
have
date
made
for
the
customer,
so
you
can
simply
push
mic
button
and
you
can
push
a
mic
button
to
a
comment
and
that
will
get
deployed
on
the
static
side
too.
So
this
is
a
step
towards
going
to
a
complete,
auto,
develop
solution.
J
H
H
H
E
But
I
was
about
to
comment
that
this
is
I
think
this
is
like
new.
This
is
the
first
time
they
released.
This
particular
feature
right.
The
status
page
yeah,
yep
I'll,
give
it
I'm
looking
forward
until
we
don't
put
this
because
I
can
see
that
status,
that
Keep
Calm
is
still
using
something
else
right.
Yeah.
H
This
is
just
released,
so
they
there
is
still
a
lot
of
work
needs
to
be
done,
because
this
is
not
just
a
crud
application
that
you're
just
posting
something
on
a
static
website.
So
this
still
in
lot
of
workings
to
done
on
this
side.
It's
just
it's
just
that
it's
the
first
iteration
you
can
say
yeah.
B
B
We
are
just
saying
that
hey
create
some
objects
in
AWS,
but
here
we
have
detailed
steps.
What
should
be
done,
so
that's
really
cool
and
I
think
it
will
be
so
when
it's
merged
it
would
be
a
great
guide,
so
I
would
advise
you
to
go
through
it
and
use
our
AWS
shared
accounts
too,
to
try
this
new
type
of
runner,
not
runner,
but
custom
executor
that
is
deploying
to
AWS
for
gate
and
I.
B
E
Already
not
maintained
by
the
doctor,
we
have
a
fork
because
we
we
needed
a
few
feature.
Doctor
machine
is
still
used
by
get
lab,
calm
and
there's
something
that
we
need
to
fix.
The
upstream
doesn't
fix
it,
so
we
we
kind
of
work.
It
yeah.
Is
that
actually
mentioned
specifically
about
going
to
replace
I.
B
Don't
think
so,
at
least
for
now
it's
not
mentioned
in
the
documentation,
and
is
this.
This
teacher
is
better
now,
so
it's
I
think
it's
not
supposed
to
be
used
in
production,
but
I
guess
it
will
be
rather
popular
because
many
people
are
using
other
skilled
and
using
docker
machine,
and
they
probably
would
like
to
move
to
four
gates.
I.
E
E
B
E
B
E
E
E
Yeah
say
that
you,
so
you
need
to
use
koneko,
that's
interesting
and
I
was
actually
wondering.
Also.
This
is
again
more
discussion
than
anything
it's
using
custom
executor,
but
rather
than
set
up
AB
as
its
own
executor,
which
is
kind
of
interesting.
It's
something
that
I've
never
kind
of
look
into
deeper
custom
executives
and
then
yeah.
This
is
using
custom
executor.
So.
J
J
B
E
Have
that
as
sub
projects-
and
you
can
hear
it
is
interesting,
like
I
I,
never
put
too
much
attention
to
custom
executives
until
this
particular
release
and
when
they
use
it
for
their
service
target
and
which,
which
make
me
yeah.
That's
what
I'm
asking
this
question
I
mean
thanks
Julian
for
for
telling
us
about
it.
M
B
B
B
B
Its
so
we
introduced
the
possibility
of
running
various
type
of
secure,
related
jobs
in
offline
environment.
So
the
idea
is
that
before,
if
you
want
to
run
saat
DASD
license
compliance
dependencies
can
in
containers
tenon
you,
you
need
its
external
connection
and
that
causes
a
lot
of
problems
for
customers
who
are
using
bit
less
in
air-gapped
environment.
Over
there.
We
are
trying
to
do
some
workarounds,
but
right
now
we
have
some
documentation
about
how
to
configure
it's
in
offline
environment.
Well,
I
haven't
tried
it.
B
E
Features
I'm
not
gonna,
talk
about
everything
and
I
think
that's
a
sign
of
get
like
awesomeness,
because
every
release
I
think
we
need
a
few
hours
to
just
go
through
a
lot
of
the
details.
But
I
just
wanna
highlight
a
few
things
and
I'm
trying
to
highlight
things
that
I,
maybe
might
be
missed,
and
it's
not
like
a
big
release
already.
L
A
E
And
if
I
open
this
then
you'll
see
this
right,
yeah,
okay,
cool!
So
a
lot
of
business
details
that
I
was
just
looking
into
it,
so
you
can
ever
rate
if
you
want
I
highlighted
a
few
things.
So
that's
probably
one
of
the
things
that
I
want
to
focus
right
now,
user
statistic
improve.
So
this
is
a
fairly
simple
addition,
but
it's
gonna
be
really
useful,
especially
when
there's
like
issue
it
like.
Why
am
I
my
license?
Blah
blah
blah?
E
E
E
I
think
it
might
be
back
the
details
of
the
active
user
and
maybe
like
this
little
like
this-
is
the
billable
user,
not
everyone.
It's
because
there's
like
block
users
and
the
number
of
user
might
be
higher,
but
the
active
user
is
the
one
that
actually
available
license
wise
yeah,
I'm,
not
exactly
sure
what
was
before,
though,
but
this
is
the
first
time
I
look
into
this
page
and
I'm
like
okay.
This
is
handy
the
fact
that
we
actually
have
this
page.
E
If
anybody
know
more
about
this
anyway,
that's
just
a
little
feature.
I
noticed
that
it
can
be
really
handy
for
us
if
there
is
like
tickets
came
in
another
thing
that
I
found
pretty
cool.
Is
this
issue
our
discussion?
Reverse
order?
Have
anyone
notice
that?
So
if
we
go
to
any
issues,
we
had
lots
of
discussion.
Let's
take
this
one.
It's
26
here
taken.
E
So
this
is
this
is
the
the
default.
If
you
change
that
the
news
first
it'll
be
a
reverse
order.
So
this
is
the
new
update,
so
you
don't
have
to
scroll
down.
I
feel
like
it's
gonna
save
a
few
hours
of
my
time
or
a
few
days
of
my
time
over
a
period
of
every
month
or
something
just
to
scrolling
up
and
down
so
yeah.
This
is
just
a
little
feature
that
they
release
and
I
think
it's
gonna
be
really
useful
for
a
lot
of
us
yeah.
E
E
It
is
another
level
this
one
group
level
container
registry,
again
very
small
release,
but
I
find
is
really
cool
because
yeah
previously,
when
yeah
we
don't
have
to
previously,
when
you
have
registry,
you
can
only
look
at
it
on
the
project
level.
Now
you
can
do
get
the
name
group
level
again,
not
a
big
release
or
anything.
It's
not
any
feature
or
anything,
but
just
pretty
handy.
E
E
Yeah
boom,
our
default
13.0
I
think
we
all
know
about
this
another
one
which
is
might
be
handy
for
a
lot
of
self
manage
user
customer
as
well,
there's
a
new
rapist
to
to
clean
up
dangling
LFS
files.
So
we
do
get
a
few
tickets
every
now
and
then
asking
like
hey
I,
love
elephants
to
s3,
and
you
know,
files
in
the
local
file
system
and
all
that
having
an
issue,
but
this
one
specifically
talking
about
LFS
file
that
orphans
that
there's
no
reference
to
it.
E
H
E
We
can
we
can
look
into
this
further.
That's
not
the
point.
Another
thing
elasticsearch
indexing
is
change.
I'm,
not
exactly
sure
what
the
changes
are
supposedly
better
performance
and
all
that
50%
reduction
for
our
production.
A
fixation
index
make
it
easier
to
get
started
again.
I,
don't
know
if
that
means
that
they're
gonna
have
different
data,
there's
something
that
expecting
that
was
there.
It's
not
there
anymore,
I'm,
not
exactly
sure,
but
it's
something
to
be
aware
of
I.
Think
and
there's
a
change
in
this
and
if
there's
a
ticket
we
upgrade
something
happen.
We
can.
E
E
If
you
go
to
the
get
the
code
base
you'll
see.
The
link,
though,
is
there
and
yeah
there's
a
lot
of
improvement.
I
haven't
mean
I,
haven't
finished,
reviewing
the
release
notes.
To
be
perfectly
honest,
so
there's
a
lot
of
like
improvements
and
all
things,
but
one
thing
that
I
wanna
highlight
is
the
deprecation
notes.
E
E
E
L
E
D
O
M
O
Various
case-by-case
so
it
takes
kind
of
like
an
effort
to
review.
There's
a
ya
know
file,
and
you
know
there
are
some
customers
having
special
cases
where
they
needed
to
implement
special
triggers
and
the
use
of
only
an
accept
and
rules
really
kind
of
go
into
play.
So
the
pipeline
really
like
breaks-
and
you
just
have
to
like.
H
E
The
other
thing
that
my
understanding
is
that
they
can
still
use
only
except
normally
another
again
I
haven't
look
into
details
on
this.
It
says
removal
date
on
the
22nd
of
May,
but
I,
don't
think
they're
gonna
remove
only
accept
altogether.
Would
they
I,
don't
know
yeah,
and
that's
why
I'm
trying
to
bring
this
up
in
the
call
just
people
are
aware.
This
is
this
is
coming
up.
E
I
G
All
right,
I'll,
just
one
more
note,
I
think
over
the
next
month.
It
might
be
a
good
approach
for
us
to
be
proactive
and
if
we're
working
on
NEC
I
tickets
they'd
have
only
and
accepts
and
there
we
should
let
the
customer
know
when
they
upgrade
to
get
led
through
team,
that
there
is
this
duplication.
Just
so.
E
K
G
E
So
I'm
like
when
I
read
this
out,
like
oh
my
god,
so
many
it's
also
because
also
well
spoiler
alert.
The
next
night
I
was
like
major
release.
Thanks
module
to
remember
that,
but
anyway
yeah
there's
another
one.
That
I
was
sleep.
It's
snippet
content
search,
removal,
I,
don't
know
if
that
I,
don't
even
a
lot
of
people
use
that
but
I,
don't
think.
There's
a
lot
of
people
that
using
that.
K
E
E
I'm,
hoping
the
error
message
would
be
fairly
clear,
but
that
could
come
up
it's
pretty
yeah.
It's
not
it's
not
a
big
sort
of
thing,
I
guess,
but
their
upgrade
might
not
go
through
if
they
still
using
the
old
configuration
they
do
upgrade
and
they
upgrade
trying
to
direct
configure
and
you
wouldn't
recognize
it
so
yeah
yeah.
That's
that's
really.
It
I
think.
E
Okay
at
the
important
to
know
web
is
forecasting
that
they
can
update
the
Postgres
without
upgrading
ticket
life
instance
say
if
they're
running
it
like
instant,
is
withdrawing
just
fine
and
it's
using
the
older
version
of
Postgres.
They
can
just
upgrade
it
to
post
race
11
and
then,
when
they
upgrade
13,
they
don't
need
to
update
the
database
at
the
same
time
so
yeah
anyway.
That's
all
I
have
any
last
thoughts
comments.
Why
not.
H
E
Yeah
I
think
I
think
it's
just
the
nature.
I
think
we're
hiring
so
many
engineers
and
we
have
we
increase
the
team
in
the
past
year
or
so,
and
they
starting
becoming
super
productive.
Now,
if
you
like
ramping
up
time
and
all
that
and
the
release
notes
just
getting
heavier
and
heavier
to
consume,
which
is
good
and
that,
but
mostly
good
I
guess
so,
yeah.