►
From YouTube: SIG Instrumentation 20220106
Description
SIG Instrumentation Bi-Weekly Meeting Jan 6th 2022
A
B
A
So
124
the
release
starts
next
week.
The
dates
are
not
final.
The
currently
the
only
dates
that
we
have
are
it
starts
on
monday
january
10th
and
the
tentative
release
date
is
april.
19Th.
We
expect
that
kept
freeze
will
probably
be
either
the
third
week
of
the
release,
or
maybe
the
fourth
week,
because
they've
been
getting
some
feedback
saying,
please
don't
have
it
on
the
third
week,
so
probably
either
the
last
week
of
january
or
the
first
week
of
february.
A
B
C
A
Yeah
thanks
so
via
sig
governance.
I
believe
what
we
actually
have
to
do
next
is
propose
this
to
the
mailing
list
and
also
open
a
pr
and
then
once
that's
done.
There
will
be
a
lazy
consensus
period
of
one
week.
We
wanted
to
wait
until
after
the
holidays,
so
people
could
actually
be
around
for
the
lazy
consensus
and
then
we
can
officially
welcome
you
as
our
new
tl.
So
thanks
so
much
damian
for
stepping
up.
It's
been
a
pleasure
working
with
you.
A
A
C
Yeah
just
a
bit
into
it
just
slightly,
but
I'm
wondering
still
like,
since
there
is
only
like
one
change
that
needs
to
be
done,
so
we
need
to
like
add
some
code
to
read
the
configuration
from
a
file,
I'm
wondering
if
it's
worth
like
creating
a
new
cap
just
for
that
or
if
we
can.
Oh
no.
No.
No.
I
won't.
A
Would
be,
I
think
it
would
be
too
much
work.
We
can
totally
update
the
existing
cap.
That
is
completely
reasonable.
If
we
want
to
bring
this
to
beta
this
release,
I
think
the
biggest
thing
is
that
there
might
be
some
prr
questions
to
fill
out,
but
those
are
pretty
straightforward
and
I'm
on
that
team,
so
I
can
help
you
with
them.
Okay.
A
A
I
will
leave
that
up
structured
logging.
I
haven't
had
a
chance
to
follow
up
with
the
release
team,
so
the
same
thing
here
at
the
end
of
the
year
and
I
figured
they
would
ignore
me.
There
is
an
enhancements
meeting
today
right
after
this
one
which
I'm
planning
on
attending,
because
I
think
that
they
were
talking
about
some
updates
to
the
enhancements
process,
and
I
want
to
voice
my
concerns
about
anything
that
will
add
more
process.
A
A
C
A
B
A
Yeah
so
anyways.
Well,
it's
not
super
high
priority.
I
did
talk
to
jordan
about
this
one
jordan
liggett,
and
he
said
you
know
it'd
be
good
to
like
do
it,
but
it
just
seems
to
be
one
of
those
tech
debt
things.
We've
had
a
hard
time
getting
resources
on,
so
we
just
want
to
make
sure
that
it
doesn't,
you
know,
fall
off
the
radar,
so
okay,
kubernetes
system
components,
log
sanitization!
I
have
kicked
off
the
depreciation
process,
so
there
is
a
pr
up
to
deprecate
this
release.
A
I've
gotten
some
feedback
from
sig
security
and
other
folks.
There
haven't
been
any
objections
thus
far
to
deprecating
this,
which
has
been
good.
So
I
have
the
pr
to
remove
the
code
and
the
feature
while
leaving
some
of
the
stuff
the
static
analysis
uses.
So,
if
folks
want
to
take
a
look
at
that,
I
guess
I
now
own
this.
Does
somebody
want
to,
on
the
instrumentation
side,
give
these
a
quick
look
over
and
lgtm.
D
A
C
A
E
A
C
A
A
F
Yeah,
the
enhancement,
I
think,
is
looking
pretty
good.
I
know
david
looked
at
it
recently.
I
saw
a
notification.
I'm
and
I've
been
meaning
to
get
back
to
working
on
like
the
the
code,
the
poc,
and
it
has
been
sitting
there.
I
just
didn't
get
to
it
before
the
the
break,
so
that
is
top
on
my
list
of
things.
I
would
like
to
get
done
sounds
good.
A
Okay,
well
then,
it
sounds
like
david's
looked
at
it,
so
I'll
mark
that
as
done
and
I'll
leave
that
action
with
you
but
yeah,
I
don't
think
we
have
much
change
now
in
terms
of
sort
of
our
question
marks
for
this
release.
If
we
end
up
graduating
or
pushing
a
lot
of
our
stuff
forward,
it
will
be
a
a
very
big
release
for
us,
so
that
will
be
cool,
but
it
will
require
lots
of
coordination
so
looking
forward
to
it,
hopefully
not
any
pain.
A
I
think
it
will
be
great,
so
we'll
see
we'll
see
how
it
goes
and,
oh,
I
just
wanted
to
double
check
and
make
sure
that
frederick
wasn't
assigned
to
approve
any
of
these
looks
like
no
so,
okay.
I
think
that
is
basically
all
I
have
for
that.
But
let
me
not
stop
sharing.
Let
me
instead
switch
over
to
the
agenda.
A
A
A
A
We
were
really
hoping
that
they
would
have
these
dates
finalized
before
we
actually
started
this
release
cycle,
but
I
think
they're
sort
of
a
race
condition
with
like
they
don't
want
to
do
that
until
they
have
a
release
team,
but
they
don't
tend
to
have
a
release
team
until
the
first
week
of
the
release.
So
so,
let's.
B
A
E
C
A
Yeah,
it's
not
quite
that
bad.
I
have
been
pushing
back
a
little
bit
since
we,
since
we've
moved
from,
like
three
month
releases
to
four
months
releases.
My
concern
and
the
reason
that
the
deadline
had
been
pushed
back
previously
was
because
we
didn't
even
have
eight
full
weeks
to
write
code
previously,
so
that
was
kind
of
a
problem
because
it
tended
to
not
be
long
enough
to
graduate
certain
features,
but
now
that
we
have
like
10
plus
weeks
or
whatever.
A
I
have
strongly
suggested
that
we
push
enhancements
freeze
back
to
week,
four
and
not
week,
three,
and
I
think
a
lot
of
people
have
been
giving
that
feedback
after
last
release
where
it
was
like
really
early,
and
I
think
there
was
cubecon
and
stuff.
So
I
think
that
we
will
be
okay,
this
release.
I
think
that
we
probably
have
a
full
month
right
now,
but
you
know
dates
creep
up
so.