►
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
All
right,
happy
wednesday,
so
everybody's
week
is
going
well
we'll
go
ahead
and
get
into
the
announcements
when
we're
announcement,
heavy
and
we'll
and
then
we'll
we'll
get
into
the
agenda
so
I'll
cover
for
thiago.
Since
this
is
not
his
his
normal
meeting
iteration
to
attend,
there's
an
epic
that's
worth
reading
by
everyone,
we're
in
the
middle
of
we're.
I
mean
it's
14,
it's
a
major
release.
A
B
That
sure,
I'm
just
showing
broadly
a
match
request
to
our
and
book
to
clarify
the
sub
department,
division
about
the
consistency
and
the
distinguish,
the
the
distinction
we're
making
between
ux
consistency
and
implementation.
Consistency
so
feel
free
to
have
a
look
at
the
merge
request
or
the
book
page.
A
This
is
something,
and
so
it's
just
async
activities
throughout
the
day.
So
please
join
if
you're
interested,
and
if
you
have
any
questions,
please
don't
hesitate
to
ask
moving
on
highlights
from
the
engineering
week
in
review.
There
were
a
few
that
I
thought
are
worth
noting
on
call
schedule
from
this
was
from
john
that's.
That
process
is
iterating
so
that
the
weekday
signups
are
no
longer
needed.
We
can
rely
on
pager
slack,
so
the
there
will
still
need
to
be
signups
for
coverage
on
weekends
as
well
as
public
holidays.
A
So
more
information
is
available
in
the
emr.
If
you
want
more
want
to
know
what's
coming,
this
is
a
change.
That's
coming
in
starting
in
september
database
load
balancing
it's
a
feature
has
been
moved
to
core
that
has
that
put
some
constraints
on
how
we
wield
it.
So
some
guidelines
are
available
that
are
listed
here,
as
well
as
a
link
for
more
information
about
about
this
particular
feature
within
the
rails.
A
So
as
far
as
what
databases
we
use,
this
is
important
because
it
speaks
to
test
suites
and
test
coverage
that
are
run
on
a
nightly
basis
related
to
that,
for,
if
you're,
introducing
or
removing
a
feature
flag,
there
is
updated
guidance
on
what
should
be
in
the
mr
titles.
So
that's
from
remy
more
information
is
a
bit
about
this
particular
change.
A
It's
available
at
the
other
end
of
that
link
and
last
but
certainly
not
least,
engineering
allocations,
so
we're
trying
to
get
more
feedback
about
about
projects
where
this
is
a
or
proposals
that
could
be
part
of
this
particular
program.
So
if
you
have
some
ideas,
these
are
not
features.
These
are
more
along
the
lines
of
scalability
and
availability,
or
at
least
that's
the
way
I
interpret
it.
So
if
you
have
any
ideas
for
for
proposals
for
this
particular
for
this
particular
project
or
group
of
projects,
please
please
submit
them.
C
A
Okay,
thank
you
yeah.
I
yeah
I
had
a
different
twist,
but
I
appreciate
that,
with
the
redirect
all
right,
all
right
and
last
but
not
least,
features
and
high
priority
bugs
have
been
closed
in
the
past
seven
days.
Here's
our
list,
if
you
want
more
information
about
what
was
closed
and
how
it
was
closed.
Please
click
through
for
anything.
You
want
more
information
about
and
and
see
what
happened,
any
questions
or
commentary
on
the
announcements
before
we
move.
D
A
And
how
it
might
be
a
good
idea
for
us
to
start
checking
the
feature
categories
that
are
assigned
to
different
parts
of
the
rails
platform,
because
those
roll
up
to
our
individual
groups,
something
that
we
learned
earlier
this
week-
is
that
when
we
make
updates
to
those
feature,
category
updates
to
the
rails
platform,
the
errors
reported
are
not
retroactively,
updated.
And
so,
if
you
see,
if
you're
paying
attention
to
those
particular
dashboards,
it
takes
28
days
for
previously
reported
errors
that
should
go
to
other
groups
to
move
off
of
your
particular
error
budget
dashboard.
D
C
Yeah,
I
I
just
wanted
to
call
out-
and
I've
talked
to
a
few
of
my
my
manager
staff
around
this
as
well.
The
the
numbers
that
are
assigned
to
to
these
values
might
not
make
sense
in
all
cases,
meaning,
so
we
we've
got
this.
You
know
99.95
percent
threshold
that
was
that
was
generically
set
for
for
all
pages.
However,
there
are
I,
I
believe
there
are
certain
pages
and
instances
where
you
know
that
99.95
is
based
on.
C
I
believe,
a
one
second
response
for,
for
the
pages,
there's
there's
going
to
be
some
pages
that
just
aren't
going
to
load
in
one
second
and-
and
so
I
I
think
we
should
call
these
pages
out
and
and
work
with
the
the
owners
of
the
reports,
and
let
them
know
that
maybe
these
don't
make
sense
for
us,
or
perhaps
they
need
to
be
tweaked
to
something.
That's
more
realistic
for
for
the
information
that
we
provide.
E
E
D
But
I
know
that
that's
been
something
that
we
have
discussed
in
the
past
or
like
if
we
want,
if
certain
customers
are
treated
as
priorities
for
resolving
errors,
it's
a
bit
difficult
for
us
because
we
have
things
like
15
megabytes,
sas
reports
in
core
and
then
we
have
like
smaller
ones
for
different
customers.
So
I'm
just
curious.
If
that's
been
a
discussion.
E
In
product
that
hasn't,
but
a
couple
of
their
product
managers
basically
talk
to
a
bunch
of
customers
and
if
you
can
actually
interview
customers
and
say
that
as
long
as
the
page
like
what
is
a
honest
threshold
of
users,
and
so
if
you
interview
a
bunch
of
people-
and
I
think
one
of
the
groups
did
like
they
expect
x
percent
of
the
page
to
all
load
within
a
certain
time
period.
But
maybe,
if
there's
a
more
verbose
table
or
something
they're
willing
to
wait
longer,
you
can
give
a
longer
threshold
to
that
table.
E
A
So,
on
that
I'll
speak,
what
I
just
wrote,
I
wouldn't
be
shocked
if
bifurcating
along
licensed
levels
is
the
next
iteration
of
these
particular
dashboards
right
now,
I
think
it's
about
establishing
dris
over
portions
of
the
rails
platform.
Next,
I
think
it's
going
to
be
about
licensed,
tiers
and
I'll
admit
my
that
I
don't
know
if
we
have
differing
slas
of
support
depending
upon
the
licensing
that
folks
get
as
far
as
availability
is
concerned.
E
A
A
I'll
take
silence
as
a
queue
to
move
on
to
item
number,
two
so
related
to
the
first
announcements
that
we
had
we're
talking
about
14-0
and
what
to
expect
there
is
an
announcement
that
has
been
shared
far
and
wide
through
many
slack
channels,
but
it's
worth
repeating
here
as
well.
Release
candidates
for
14
0s
platform
are
already
being
cut.
It's
early
for
this
particular
release,
but
that's
because
that's
how
big
this
one
is.
A
So,
if
there's,
if
we're
aware
of
breaking
changes
that
have
not
been
merged
into
product,
yet
we
got
to
get
loud
now.
There's
there's
guidance
on
what
needs
to
happen
within
the
as
far
as
what
issue
needs
to
be.
What
issue
needs
to
this
needs
to
be
put
on,
as
well
as
who
needs
to
be
pinged
within
said
issue.
A
There's
also
a
note
about
which
commit
specifically,
is
the
last
commit
guaranteed
to
be
as
part
of
the
release
on
the
22nd.
So
these
are
things
to
be
aware
of
we're
running
if,
if
there
are
breaking
changes
or
items
that
we're
trying
to
get
into
the
platform
of
14
0
we're
running
out
of
time.
So
this
is
this:
this
is
a
call
to
action
to
make
sure
we're
getting
loud.
There's
stuff,
that's
missing,
so
any
questions
or
commentary
on
this.