►
From YouTube: 2022-03-10 meeting
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).
D
B
A
C
Anybody
wants,
let
me
check
the
milestone.
A
Okay,
I
tagged
a
couple
things
just
yesterday
that
looks
like
those
all
went
in
so
if
there's
anything
else
that
you
want
in
the
release
tag
it,
and
I
will
make
a
attempt
to
merge
it
before
cutting
the
release.
Otherwise
I'll
probably
start
I'll.
Do
the
release
notes
today
and
get
everything
queued
up
and
either
hit
the
button
later
today
or
tomorrow,.
A
I'm
just
lori,
I'm
really
thrilled
by
this
helper
class
injection.
A
A
A
Oh
yeah,
just
in
case
other
folks,
didn't
catch.
I
think
the
micrometer
honorable
proposed
moving
micrometer
to
the
core
repo.
So
we
chatted
on
tuesday
and
I
think.
A
Agrees-
and
so
I
think
he
just
put
in
a
pr
today-
to
put
it
into
the
core
repo
and
then
we'll
we'll
keep
it
in
the
instrumentation
repo
and
in
1.13,
we'll
deprecate
it
and
then
in
114,
we'll
remove
it,
because
we
didn't
want
to
deprecate
it
until
we
can
point
people
to
a
the
new,
a
new
released
version
from
the
core
repo.
A
D
Yeah
that
I
that's
true,
I
mean
I
I've
been
sort
of
following
it,
but
not
really
reviewing
that
that
much
we've
got
some
metrics
prs
for
you
to
look
at
when
you're
ready.
D
Yeah-
and
I
just
realized
like
a
minute
ago
that
micrometer
we're
going
to
have
micrometer
to
0
version
soon.
I
think
in
like
a
matter
of
months
or
two
probably.
D
So
we'll
probably
want
the
micrometer
2.0
shin
too,
and
I
don't
think
we
have
any
like
to
put
mentioning
version
and
artifact
name
and
concept
in
sdk
yeah.
E
That's
true
we
should
maybe
we
should
actually
could
if
you
could
comment
on
autorox
pr.
That
would
be
great.
I.
F
E
Probably
want
to
get
the
name
of
the
artifact
right
before
it's
too
late
yeah.
My
committee
want
my.
D
I
have
just
taken
a
quick
look
at
both
of
them,
but
I've
been
meaning
to
review
them.
Once
I
find
a
little
bit
of
free
time
to
focus
on
these
two,
I
think
that
the
one
that
you
have
opened
right
now
is
probably
a
bit
nicer,
because
it
it
allows
you
to
configure
any
resource
property
or
just
the
service
name
on
the
other.
E
A
This
one
seems
really
straightforward.
I
like
this
one,
it's
very
straightforward:
it's
you
know
it's
how
it's
just
a
continuation
of
how
we
provide
other
components.
A
Okay,
well,
we
should
yeah
I'll
I'll
mark
I'll
I'll.
Take
a
another
pass
at
this,
but
this
basically
looks
good
to
me.
So
my.
A
Oh
yeah,
so
I've
been
having
like
eye
strain
stuff,
so
I've
been
messing
around
with
different
views.
I
tried
to
go
all
dark
for
a
week
and
now
I'm
trying
other
light
again,
but
I
found
this
one:
no,
not
profile.
A
Yeah
yeah,
it's
in
it's
right
in
here
light
high
contrast.
A
I
think
this
starts
to
get
on
rog
head
I'll.
Ask.
Let
me
add
this
to
the
notes
that
I
can
discuss
with.
We
can
discuss
with
iraq
today.
A
Because
he's
mentioned
this
before
sort
of
of
what
our
plans
are
and
what
are
our
plans
in
the
spring
auto
configuration
area.
A
A
And
I'm
not
sure
we
want
to
have
two
different
configuration
mechanis
two
different
sort
of
like
it
would
be
nice
if
the
spring
auto,
configure
environment,
property
support
basically
flowed
from
the
sdk
properties
or
in
the
future.
The
sdk
yaml
configuration
file
or
something
like
that.
The
names
structure.
D
C
A
C
A
E
Yeah
spring
auto
configure
is
a
little
different,
though
right,
because
there
there's
like
a
standard
format
for
spring
like
the
spring
properties.
I
don't
remember
what
it
looks
like
but
like
it
feels
like,
if
you're
doing,
if
you're
trying
to
integrate
with
the
spring
ecosystem,
then
it
won't
look
like
what
the
like
the
standard
environment,
rail
variables
will
look
like
for
hotel,
it'll,
look
like
spring
stuff.
A
This
could
be,
this
could
look
like
I
mean
if
we
had
this
support
in
the
sdk.
E
E
And
I
think
this
this
gets
to
the
always
being
kicked
the
can
being
kicked
down
the
road
around
a
comprehensive
configuration
language
for
for
hotel
right.