►
Description
A
A
Okay,
if
no
announcements
we'll
go
to
the
issues
tag
with
the
TC
agenda,
the
first
one
is
rep
ol,
amid
uncaught
exception.
2803
I
see
in
the
discussion
that
you
know
the
the
tag
has
been
removed
from
the
agenda.
I.
Think
technically
we
have
to
talk
about
it
anyway,
as
per
our
governance,
but
as
long
as
we
all
agree
that
you
know
there
was
no
specific
question.
A
I
think
it
was
just
really
a
call
for
more
TSE
remembers
to
review,
because
it's
mber,
major
and
needs
help
to
you
know
needs
approvals
to
be
able
to
land.
So
unless
anybody
else
has
some
specifics,
they
want
to
dive
in
on
that,
one
I
think
we
can
move
on
to
the
next
issue
that
sound
good
to
everybody.
A
Out
there,
okay,
so
moving
on
to
the
next
one.
The
next
issue
that
it
was
tagged
is
node
module
version,
4,
electron,
major
releases,
number,
651
and
I.
Think
in
this
case
we
just
need
to
you
know
we
need
to
decide-
or
at
least
maybe
not
decide
since
we
don't
have
enough
people
necessarily,
but
you
know,
try
and
get
us
on
a
path
to
where
we
know
what
the
short
term
and
long
term
approach
is
going
to
be
to
unblock
the
particular
issue.
That's
that's
right.
There,
there
where's
there
Gabriel
I,
know
you've.
B
Yeah,
so
basically,
my
understanding
is
that
there
are
times
when
the
the
module
version
announced
by
the
add-on
matches
the
module
version
expected
by
nodejs,
and
yet
there
are
ABI
mismatches
because
in
addition
to
v8,
the
module
uses
other
nodejs
api's,
which
are
a
bi
mismatched,
depending
on
whether
the
nodejs
version
is
one
that
is
shipped
by
us
through
our
official
channels
or
whether
it's
built
by
others
from
source
and
and
so
we
need
to
distinguish
between
those.
And
we
can
do
that
by
giving
everybody
a
unique
node
module
version.
B
B
So
if
we
start,
if
we
start
changing
the
node
module
version
because
of
open
SSL
and
because
of
other
like
libuv
for
example,
then
then,
then
you
know
people
who
don't
use
any
of
those
will
have
to
now
ship
multiple
binaries
for
multiple
version
numbers.
Even
though
a
single
binary
would
work
so
so
I
don't
care
about
other
api's
scenario:
I,
don't
believe,
can
be
addressed
using
a
single
number.
That
is
my
understanding
right.
A
So
I
I
guess
the
you
know
it
seems
like
it
seems
to
me
that
that's
a
good
discussion
to
have,
but
that
might
take
longer
and
I
guess.
The
question
in
my
mind,
is
like
do
we
want
us
enable
in
the
meantime,
while
we
figure
that
out
projects
to
just
grab
a
version
number
or
do
we
think
we
need
to
you
know,
figure
out
the
best
solution
before
we
do
that,
there's
Pete!
A
B
Well
happening,
you
know,
increasing
the
node
module
version
or
lowering
the
bar
for
for
increasing
the
node
module
version
is
not
a
bad
idea.
In
any
case,
it's
just
it'll
create
a
you
know.
It
might
increase
the
maintenance
burden
for
those
module
owners
which,
which
you
know
don't
care
about
the
reasons
why
it
was
increment,
that's
all,
but
but
in
the
meantime
you
know
avoiding
mysterious
crashes
and
stuff
because
of
API
breaks
is
definitely
a
worthy
goal
which
can
be
achieved
by
by
a
more
liberally
increasing
the
node
module
version.
C
A
A
A
A
A
A
B
D
B
Yeah
yeah,
basically
or
or
like
a
PR,
which
just
increments
the
node
module
version
and
doesn't
do
anything
else,
and
it's
it's
one
that
is
obviously
semver
major
and
then
that
would
be
it
right.
Because
then,
then,
on
master,
the
node
module
version
would
would
increase,
but
that
that
new
number
would
not
appear
in
any
in
any.
C
B
Compare
symbol
table
says:
Jeremiah
yeah,
no
I,
don't
think
so,
because
that's
the
in
order
to
come
I
mean
okay,
yes,
I'm
sure
it
can
be
done,
but
it
would
be.
Super
super
duper
platform-specific
how
to
how
to
retrieve
symbols.
I
mean
the
only
thing
that
is
relatively
platform-agnostic
is.
If
you
know
the
symbol
name,
then
you
can
check
whether
you
can
retrieve
the
symbol
and
if
you
get
non
null,
then
you
have
this
similar.
You
get.
No,
you
don't
that's
about
it,
and
so
so
you
know
I
mean
to
do
that.
B
B
B
We
would
want
to
have
a
way
to
to
check
the
entire
API
signature
before
loading,
the
module
and
yeah.
There's,
there's
no
there's
no
good
way.
I
I
do
have
a
PR
for
like
a
proof
of
concept
where,
where
the
module
declares
an
ABI
signature,
but
but
that's
that
needs
buying
from
the
module,
so
we
cannot
statically
analyze
the
module
at
load
time.
As
far
as
I
know,.
A
A
Just
trying
to
fix
it,
okay
I've
said
discussion
in
the
meeting
is
that
we
just
need
a
PR
to
bump
the
API
number
in
master,
but
Gabriel
volunteered
in
quotes
to
confirm,
process
and
comment
in
651
and
specifically
what
to
do
and
then
I
said.
Gabriel
will
also
create
a
new
issue
to
continue
the
discussion
on
whether
we
want
to
assign
bits,
etc.
A
A
B
A
B
D
A
Was
a
specific
request
for
to
solve
a
problem
right
if
I'm,
remembering
correctly
so
I'm?
Almost
thinking
like
we
should
take
the
meta
discussion
out
of
that
issue,
so
we
can
come
to
a
resolution
which
is
basically
like.
Okay,
here's
you
know
do
this
to
get
your
node
major
version.
Okay,
that
issues
closed.
Now,
if
you
know
we're
gonna
continue
the
discussion
over
here
that
met
the
meta
discussion.
A
A
A
C
Basically,
I
think
we
we
depend
on
Python
2
for
our
fill
and
Python
2
is
not
going
to
be
supported
anymore
by
2020,
so
we
have
one
year
to
migrate
with
Python
3.
That
is
our
initial
goal
raffle
and
the
Christian
class.
They
would
have
been
working
on
this
for
the
past
few
months
and
we're
in
good
shape,
reflect
ruffles,
give
they
will
be
working
in
lab
reference
dip
repo.
So,
as
first
step,
we
are
migrating
all
the
way
been
actually
making
the
Python
scripts
in
node
repository
compatible
with
the
country
so
yeah,
that's
that's.
A
A
In
terms
of
the
other
initiatives
napi,
I
think
the
key
thing
we're
working
on
is
to
get
the
TFS
n
functionality,
not
non-experimental,
I'm
gabriel,
you
already
landed.
I
think
that
in
yes,
I'd
already
landed
a
master
I
see
you
have
PR
to
get
it
back
to
ten,
and
we
need
to
flow
that
back
in
time
in
term
in
time
for
a
planned,
8x
sunburn,
minor,
release,
I
guess
the
other
related
thing
I
would
say.
A
Is
there
some
text
that
I've
have
peered
into
the
release,
readme
sort
of
it
around
our
processes,
which
is
kind
of
an
allowance
for
bringing
things
into
releases
that
are
in
maintenance
for
napi?
You
know
acknowledging
that
we
need
to
keep
things
consistent
and
you
know
so
we
may
have
a
you
know.
There
may
be
things
that
we
want
a
back
port
to
maintenance
releases,
even
though
you
know
we
might
not
otherwise,
because
it's
important
to
make
sure
you
can
run
those
modules
across
all
the
LTS
releases.
D
B
A
A
Rich
who
just
joined
has
any
no
okay,
so
I
think
that's
it
for
the
strategic
initiatives,
any
other
comments
or
discussion
on
that
front.
Before
we
move
on
you,
if
not
we're
at
the
Q&A
section.
So
let's
flip
over
and
see
if
we
have
anybody
on
the
YouTube
channel
with
a
question.
So
if
you
have
a
chat
question,
please
post
it
now
or
wait
a
minute
or
two
there
I'm
just
trying
to
flip
back
to
see
if
I
can
find
that
tab.