►
From YouTube: 2022-12-12 meeting
Description
cncf-opentelemetry meeting-2's Personal Meeting Room
A
A
B
B
B
B
Foreign,
let's
get
started
so
starting
with
the
Sig
check-in,
so
for
the
spec
we've
got
spec
version
1.16.0
that
was
released.
I
think
we
discussed
the
contents
of
that
over
the
last
few
weeks
and
those
are
certainly
discussed
in
the
specs
Sig
moving
down
to
PHP.
We
have
version
one
beta
1
that
has
been
released
from
tracing
for
Java.
Similarly,
we
have
1.21.0
of
an
SDK
release.
B
Actually
sorry
circling
back
to
PHP
Bob.
This
is
the
first
beta
for
tracing
right.
That's
right!
We're
very
excited
for
it.
That's
fantastic!
That's
worth
celebrating
great.
C
C
So
essentially,
when
you
are
done
with
beta,
because
I
see
that
you
are
using
one
zero,
zero
beta
one,
would
this
be
named
one
zero,
zero
or
would
be
named
120
or
whatever?
It
is?
The
tracing
version.
A
C
D
B
Okay,
we'll
keep
moving
no
updates
for
JavaScript
for
python.
We
version
1.15
for
go,
looks
like
we've
released
1.11.2,
which
relies
on
0.34
0.35
is
16
done,
go
folks
and
apologies
first
to
the
question:
is
this
.35
the
version
that
contains
the
metrics
beta?
Are
we
just
think
we're
16
done
on
the
next
version?
Generally.
E
That's
that's
just
60
done
on
the
next
version.
I
don't
know
if
we
have
anything,
that's
going
to
spill
beyond
that
and
we've
got
a
separate
beta
Milestone
that
contains
largely
the
same
things.
E
16
done
yeah,
okay,
we're
looking,
though,
to
make
sure
that
we
get
regular
releases
out
so
that
we
can
continue
to
get
feedback
on
the
changes.
We're
making
and
we'll
call
it
beta
when
it's
ready
for
beta
makes.
B
Sense
to
me:
cool
no
updates
for
C,
plus
plus
review
Swift
for
The
Collector.
We
have
.67
that
was
released
last
week.
This
includes
the
P
data
module,
which
is
the
first
module
for
version
1.0
rc1
excellent
for
erlang.
We've
delayed
the
metrics
release
cut
while
deciding
what
to
do
with
value
type.
B
Erlang
folks
do
want
to
discuss
this
at
all.
Here.
D
I,
don't
know
if
there's
much
to
this,
maybe
just
I've
asked
you
know
python
like
what
they
do
with
value
type
I
thought
they
were,
which
in
metrics
the
value,
type
integer
or
float
useful
and
statically
typed
and
strongly
typed
languages.
Certainly
I
thought
there
would
be
optimizations.
We
could
do
in
erling.
I've
come
around
to
see.
D
That's
not
probably
going
to
be
the
case,
so
thinking
about
dropping
it,
python
doesn't
use
it
I,
don't
know
if
any
other
Dynamic
language
maintainers
in
here
have
any
did
anything
with
it,
removing
value
type
or
including
it.
If
there's
anything
useful
on
the
back
ends
to
know
because
a
metric
I
assume
the
name
could
come
into
a
back
end
as
an
integer
and
then
later
become
a
float.
So
it's
not
really,
but
that
even
back
end
can
rely
on
this
value
type.
Never
changing
so
I
think
we're
safe.
D
B
B
Thank
you
for
that.
The
first
topic
that
we
have
is
feedback
on
the
roadmap
PR.
So
we
discussed
this
briefly
last
week,
I
had
sort
of
collated
a
bunch
of
things
that
we
discussed
at
kubecon
and
various
Community
calls,
including
this
one
into
a
single
roadmap.
B
That's
linked
to
last
week,
and
it's
linked
to
also
in
this
comment.
From
this
week.
We've
had
some
feedback
looks
like
just
sort
of
grammatical
edits
from
drassi.
B
Ben
had
requested
that
we
could
do
this
or
add
some
kind
of
process
around
this,
so
I
think,
Ben
and
and
Daniel
had
suggested.
Perhaps
doing
this
quarterly
I
think
it's
a
very
good
idea,
and
then
it
also
just
requests
reformatting
to
the
table.
I
can
work
on
that
and
next
Daniel
said.
First
doing
this
quarterly
I
also
agree
Daniel.
B
B
B
F
Then
we
can
run
sorry,
sorry
go
ahead.
I
do
have
a
topic,
it's
just.
E
F
Sure
thing
so
in
Python
we
were
facing
some
issues
because
we
were
requiring
to
approvals
forever.
We
are
in
the
main,
repo
and
the
relatively
short
of
maintainers
right
now,
since
some
of
them
are
taking
time
out,
so
we
decided
to
lower
the
amount
of
approvals
required
for
that
time
being
at
least
during
December
to
only
one.
So
we
just
wanted
to
share
this.
In
case,
any
others
say
is
having
that
same
difficulty.