►
From YouTube: 2023 01 05 Docs Office Hours
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
Okay,
welcome
everyone
to
Jenkins
doc's
office
hours,
EU
US
edition.
It
is
the
first
edition
of
2023,
so
happy
New
Year
to
everyone
so
happy
to
have
you
joining
us
again
today
and
hope.
The
new
year
was
wonderful
for
you
as
well.
Today,
we've
got
some
action
items
still
talking
about
the
our
docs
mailing
list
being
archived
and
some
blog
posts
that
were
recently
published,
just
a
quick
check
on
Pipeline
Docker
plugin
deprecation.
A
There
is
another
topic
of
when
wmi
Windows
agents
deprecation
that
Mark
wanted
to
share
and
just
talk
about
when
we
get
to
that
point.
This
was
an
action
item,
but
I've
changed
it
to
a
regular
item
of
archiving.
The
website
tickets
that
are
on
jira,
so
I've
gone
through
the
list
and
there
are
some
that
still
just
need
to
be
discussed.
A
We
do
have
the
next
LTS
changelog
and
upgrade
guide
submitted
as
a
pull
request
so
check
out,
as
well
as
the
web
components
that
Gap
have
been
Mogan
has
been
building
for
building
lately
and
how
they're
actually
in
place
now
pull
request,
backlog,
quick
note
and
the
December
newsletter,
which
we've
been
talking
about
and
we'll
be
being
published
soon.
So
anything
else
that
I
missed
here
or
any
other
items
that
we
want
to
add
on.
A
No
all
right.
So
first
thing
on
the
list:
archiving
the
docs
mailing
list
and
switching
to
community.jenkins.io
for
the
doc
Sig
mailing
list.
This
is
something
that
I'll
be
working
on
with
Mark
and
we'll
start
working
on
that
shortly
sometime
this
month
to
get
at
least
going
on
that
and
more
details
to
come,
and
then
the
blog
post
I
wanted
to
share.
A
So
we
previously
had
basil,
Pro
and
John
marknson's
blog
post
in
December
for
Jenkins
plugin
development
requiring
Java
11
and
the
Google
summer
of
code
mentorship
respectively,
quick
note
on
Google
summer
code,
mentorship
we're
actually
at
50
to
70
mentorship
right.
Now,
it's
a
wonderful
change.
From
the
last
time
we
met.
So
a
lot
of
people
have
stepped
up
and
signed
up
to
be
mentors.
Thank
you
to
all
of
the
people
that
have
you
know
inquired
signed
up
volunteered.
Everything
can't
do
it
without
you
and
Dave.
A
Are
people
have
already
started
submitting
new
author
files
and
everything
which
is
great
so
really
just
excited
to
see
all
the
new
contributors
joining
up
and
mentors
wanting
to
help
and
then
most
recently
Bruno
Bruno's
blog
post
on
running
your
Jenkins
agent
as
a
service?
This
was
just
published
last
week,
but
it's
a
great
overview
and
tutorial
of
how
you
would
create
a
new
Jenkins
node
and
run
your
Jenkins
Service.
A
As
the
title
says:
great
instructions,
a
very
nice
personal
feel
to
it
and
personal
examples
and
yeah
Bruno.
B
C
C
B
So
so
the
the
technique
is
valid.
There
are
inbound
agents
like
this
one
is
describing
and
outbound
agents
inbound
agents.
The
benefit
of
an
inbound
agent
is
the
agents
own
system
controls
the
start
and
stop
of
that
agent
right.
So
if,
if
you've
got
someone
who's
donating
capacity,
an
inbound
agent
is
a
perfect
way
to
do
it,
and
and
the
the
Jenkins
project
has
a
thing
called
the
Swarm
plug-in
that
sort
of
makes
that
even
systematic,
where
you
could
have
a
group
of
20
or
30
people
who
donate
sporadically
their
capacity.
B
Oh
I'm,
going
home
for
the
night
I'm
going
to
turn
on
the
Swarm
agent.
You
can
use
my
computer
overnight
and,
and
that's
that's
an
inbound
agent
very,
very
good
use
case.
The
other
use
case.
The
outbound
agent
use
case
is
it
allows
the
controller
to
decide
when
it
starts
and
stops
the
agent
and-
and
so
it
just
depends
where
you
want
the
control
to
be
many
windows.
B
Users,
for
example,
choose
to
use
an
inbound
agent
because
they
need
a
Windows
desktop
and
if
they
need
a
Windows
desktop,
it's
really
tough
from
the
outside
of
a
Windows
machine.
To
log
in
remotely
to
the
Windows
machine
and
start
the
desktop,
that's
that's
really
done
by
a
user
on
the
desktop
itself.
So
inbound
agent
works
really
well
for
Windows
agents
that
need
control
of
a
desktop
or
for
people
who
want
to
donate
capacity.
Outbound
agent
for
oh
I've
got
a
cloud.
I
want
the
cloud
to
do
the
work.
C
B
Right
right-
and
that's
that's
a
good
one
where,
if
you,
you
might
say,
oh
I,
want
to
donate
an
ex
executor
to
to
A
A
system
that
is
global,
right,
I'm,
there's
something
sitting
on
the
public
internet,
the
controllers
on
the
public
internet,
but
I
want
to
donate
resources
that
are
inside
my
private
Network
that
public
internet-based
controller
correctly
cannot
see
inside
your
private
internet.
So
that's
that's
a
really
good
use
case
for
an
inbound
agent.
B
A
You
thank
you
very
much,
Mark,
wonderful
explanation
and
Bruno
again.
I
super
appreciate
the
the
post
itself
and
additional
Insight
that
you
also
have
so
you're
welcome.
This
is
this
is
wonderful.
Thank
you
so
much
for
going
through
and
creating
this
and
what
a
great
addition
and
thank
you
Mark.
A
Okay,
great
so
next
on
the
list
is
the
pipeline.
Docker,
plugin
and
potential
future
deprecation.
A
It's
very
widely
used,
and
this
needs
a
lot
of
discussion
to
determine
what
that
effect
is
going
to
look
like
if
it
is,
if
and
when
it
is
deprecated.
So
this
needs
to
be
discussed
and
we
need
to
find
out
just
you
know
what
kind
of
far-reaching
effects
this
could
have,
so
we
can
make
sure
to
try
and
avoid
those
and
just
resolve
everything
properly.
So
TBD.
B
But
no
the
the
plug-in
is,
is
up
for
adoption,
and
so
that
means
that
that
the
current
maintainers
have
said
look.
This
is
not
high
on
our
list
of
Maintenance
and
and
so,
but
it
is
not
deprecated
and
the
the
challenge
for
us
in
the
docs
team
is
if
it
were
to
be
deprecated
many
of
the
tutorials
that
we
have
no
longer
work.
Many
of
the
the
big
documentation
flows
that
we
have
of
this
is
how
you
work
with
Docker,
don't
work,
and-
and
in
that
case
then
we
need
a
better
way
to
do
it.
B
But
I
think
the
reality
is
that
workflow
is,
is
so
common
that
it
won't
be
deprecated,
but
there
may
be
changes
to
that
plug-in
to
make
it
so
that
the
less
attractive
pieces
of
it
are
somehow
disabled
or
or
removed,
because
there's
there's
the
simple
way
that
the
tutorials
use
and
the
simple
way
works
and
the
maintainers
of
the
previous
maintainers
of
the
polygon
were
willing
to
support
that
simple
use.
There
are
complicated
and
exotic
use
cases
that
the
maintainer,
the
previous
maintainers
say
absolutely
not.
B
I
am
unwilling
to
support
that
sort
of
strange
use
case
and,
and
the
challenge
is,
how
do
we
get
people
to
stay
away
from
the
strange
ones
and
stay
in
the
nice
mainstream
ones?
We've
we've
taught
them
the
mainstream
ones
in
the
tutorial,
but
we
haven't.
We
haven't
limited
the
use
of
the
plug-in
to
only
those
mainstream,
really
well-defined
cases.
B
B
A
Gotcha
and
and
there's
not
really
a
way
to
put
like
horse
blinders
so
to
speak
on
people
so
that
they
don't
see
those
questions.
B
There
is,
but
it
involves
there.
There
is
the
technique,
though,
is
you
split
the
plug-in
into
two
parts,
the
good
parts,
the
parts
you
want
to
preserve
you?
You
leave
un
untouched
Etc,
the
bad
parts
you
mark
As
deprecated,
and
you
you
deprecate
the
plug-in
that
you
just
spun
out
brand
new
and
say
this
plug-in
is
deprecated
switch
to
this
other
one
and
but
but
that's
a
lot
more
involved
and
it
requires
serious
development
effort
on
the
plug-in
to
do
that
kind
of
a
partitioning.
A
Yep
yeah
that
sounds
like
a
little
bit
more
work,
I'm
sure.
Well,
thank
you,
Mark
for
explaining
clarifying
that
that
helps
a
lot
and
I'm
now
more
up
to
speed.net.
Thank
you
and
then
next
up
on
the
list,
Mark
is
the
wmi
windows
agents
deprecation.
So
would
you
like
to
share
what
this
one
is
about
and
what's
going.
B
On
here
yeah,
so
the
the
story
here
is
is
there's
a
there's,
a
concept
in
Jenkins
of
well,
the
history
of
Jenkins
is
that
it
started
as
an
a
monolithic
application
with
optional
plugins,
but
the
there
were
certain
things
that
were
inside
the
core
that
ultimately,
the
the
developers
of
it
realize
this
doesn't
belong
in
core.
It
needs
to
be
a
plug-in
and
for,
for
example,
one
of
those
was
how
do
I
start
an
agent
on
a
Windows
computer.
B
Originally
that
was
inside
core.
It
was
a
core
function,
you
couldn't
opt
out
of
it,
you
couldn't
remove
it.
It
was
always
there
and
that's
unhealthy
so
early
on
in
the
Jenkins
life
cycle,
about
Jenkins,
1.400
or
1.500.
That
was
split
out
from
Jenkins
core
to
be
a
separate
plugin
good
thing
right
that
that's
healthy.
B
However,
any
plug-in
that
was
written
to
depend
on
a
Jenkins
version
before
the
split
might
have
expected
those
Java
classes
to
still
be
there,
and
thus
there
is
this
implied
dependency
that
is
created
because
the
plug-in
says
the
the
controller
correctly
says.
I
can't
promise
that
you
don't
depend
on
some
API.
That
was
in
this
plug-in
that
was
in
this
component.
That's
now
split
to
a
plug-in
in
this
wmi
Windows
agents
case.
B
The
split
was
fairly
early
in
Jenkins
life
cycle
400
to
500,
and
there
are
over
300
plug-ins
that
depend
on
a
Jenkins
version
earlier
than
that,
and
thus
have
an
implied
dependency
on
this
wmi
agents.
With
that
implied
dependency,
it
means
they
can't
get
rid
of
this
deprecated
plugin
and-
and
that's
not
a
great
experience
for
them.
However,
Jesse
Glick
did
a
little
bit
of
investigation
and
realized.
In
this
specific
case,
the
implied
dependency
is
actually
misleading.
B
There
are
only
two
plugins
in
those
300
that
really
depend
on
the
plug-in,
all
the
others.
It's
in
fact
not
a
dependency,
so
he
suggested
a
very
a
much
more
lightweight
technique
than
update
all
300
plugins.
His
suggestion
is:
look,
let's
fix
Jenkins
core,
so
that
this
particular
thing
is
not
listed
as
a
source
of
implied
dependencies.
B
Now
it
needs
a
lot
of
testing.
I've
got
to
do
some
better
pull
requests
Etc,
but
the
challenge
is
the
concepts
and
maybe
Kevin
I'm,
going
to
put
a
link
to
the
bug
report
where
the
the
concepts
are
described
because
I
I
spent
the
time
to
describe
the
concepts
in
a
in
a
bug
report,
and
maybe,
if
you
can
open
that
bug
report,
what
what
this
gives
is
a
a
tutorial
on
okay,
what
does
deprecation
mean,
and
why
is
this
specific
plug-in
deprecated?
B
So
why
is
technical
reasons,
blah
blah
blah?
What's
an
implied
dependency?
That's
what
I
described
earlier.
Why
does
it
exist
again?
That's
what
I
just
described
earlier?
Hey!
It
was
split
out
of
Jenkins
core
in
1.547.
That's
a
long
time
ago,
right
I
mean
we're
now
at
2.370
385.,
with
about
One
release
a
week.
So
we
are
a
long
ways
since
1.547.,
but
that
that
implied
dependency
is
there
and
then
now
the
next
piece
is
okay.
How
do
you
remove
it?
B
B
The
the
reason
this
is
relevant
for
the
bigger
picture
is
because
there
are
some
other
plug-ins
like
this
that
were
split
out
one
in
particular
the
Oracle
jdk
installer
plug-in
that
may
in
the
future,
be
deprecated,
and
it
would
have
this
same
kind
of
pattern.
So
so
we
may
choose,
we
may
choose
to
document
this
thing.
A
little
wider,
I,
don't
know
it's.
It's
still
a
thought
process.
Any
questions
about
what
I
just
described.
A
No,
that's
pretty
clear
for
kind
of
a
high
level
overview,
Mark,
I,
think
and
the
bugs
there
the
bug
issues
there
I.
Can
that
mean
that
thing
I
can
read
through
that
and
I
forget
some
more
sense
of
it,
but
yeah
and
I
saw
my
main
question
was
going
to
be?
Is
it
just
kind
of
if
you
modernize
and
improve
the
plugin
like
we
have
in
the
tutorial?
That
should
be
enough
to
remove
that
dependency
at
this
point,
because
it's
going
to
update
it
to
the
latest
version
of
Jenkins.
B
It
it
is,
and-
and
that
was
Jesse
glick's
point-
he
said-
hey
systematically
for
high
volume
plug-ins.
We
should
be
updating
their
dependencies
anyway,
but
but
then,
but
his
point
was
of
this
set
of
300,
plus
only
about
15
of
them
have
more
than
2
000
installations
and
and
in
a
system
like
Jenkins,
where
there
are
three
hundred
thousand
controllers,
if
you're
only
installed
on
2
000
of
them
you're,
actually
a
very
small
subset
of
the
total
Jenkins
community.
A
Got
it
okay
and
then
would
there
be
something
coming
up
like
potentially
a
blog
post
to
share
that
or.
B
Sorry
we're
or
you
must
yourself
keep
this
plugin
installed
because
we're
not
going
to
take
care
of
it
for
you
and
and
that
that
will
work.
They
could
do
it.
It's
it's,
and
it's
not
actually
that
painful.
So
it's
just
a
matter
of
of
got
to
be
sure
that
I've
done
through
the
the
right
testing
the
proper
due
diligence
to
be
sure
that,
yes,
the
change
that
he's
suggested,
works
and
works
well
and
is
good
enough
to
make
users
the
user
experience
good.
A
Got
it
great?
That's
that's
extremely
clear
now.
Thank
you
very
much
Mark
for
explaining
and
sharing
all
that
any
other
thoughts
or
items
on
that,
or
is
that
everything.
A
Great,
thank
you
so
much.
The
next
thing
on
our
agenda
is
the
website
tickets
that
I'm
going
through
in
either
closing
out
if
we
have
already
taken
care
of
them
or
if
we
just
like
documentation,
evolves
naturally
over
time.
So
a
lot
of
these
things
have
been
taken
care
of
just
by
virtue
of
doing
the
work
normally
so
I've
gone
through.
A
Most
of
them,
I
have
a
few
that
I
would
like
to
discuss
and
determine
whether
or
not
we
need
to
migrate
those
to
GitHub
or
if
they
can
be
closed
out
or
what
and
I've
linked
the
sheet
here.
So
once
we
finish
up
the
last
couple
items
here,
we'll
go
back
and
take
a
look
through
that
list
and
see
what
makes
sense
to
keep
and
what
makes
sense
to
close
yeah.
B
I,
like
that,
so
Bruno
are
you,
okay.
If
what
I
was
suggesting
to
Kevin
earlier
was
in
an
earlier
session,
he
and
I
were
talking
that
we
actually
spent
some
time
here
in
office
hours
to
look
at
these
issues
he's
we
he's
removed
most
of
the
most
of
them
from
the
list,
but
we
look
at
the
few
that
he
hasn't
removed
and
say
yeah,
that's
a
that's
one.
We
should
keep
or
no
close
it
out.
Yeah.
A
Okay,
great
yeah
and,
like
I,
said
we'll
get
into
that
as
soon
as
I
finish
up.
We
finish
the
rest
of
the
agenda
just
so
we
can
have
time
yeah
pull
requests
of
note
again.
We
have
the
changelog
for
an
upgrade
guide
for
the
next
LTS,
which
is
January
11th
so
next
week
and
that's
been
submitted,
everything's
ready
to
go
there.
A
The
back
porting's
all
been
taken
care
of
at
this
point,
so
it's
ready
for
review
and
merge
and
then
the
other
pull
request
to
note
here
is
the
web
components
that
Gavin
mogan's
been
building
and
creating.
This
has
actually
been
merged.
So
though,
jenkins.io
site
now
has
these
applied
to
it
and
looks
great.
B
B
C
B
A
Of
course,
and
I
think
this
too
actually
is
one
of
the
other
updates
that
he
just
dealt
with.
The
Highlight
now
covers
the
list
items
in
the
categories
here,
the
oh,
the
sub
links
yeah
before
it
was
just
you
just
click
on
it,
but
now
it
actually
has
a
highlight
to
show
that
you're
looking
at
the
right
thing,
just
kind
of
neat.
So
little
things
are
big
difference
makers,
but
yeah.
So
a
big
big
huge.
A
Thank
you
to
Gavin
Morgan
for
doing
all
that
for
his
continued
work
on
that
for
making
these
part
of
the
jenkins.io
experience
and
the
and
I
know
that
there's
more
to
come
to
so
for
all
the
continued
work
that
will
be
done,
we
do
have
a
backlog
of
pull
requests
right
now.
I
think
we're
at
about
40
to
43
is
the
highest
altogether.
So
we're
obviously
planning
on
going
through
those
and
making
sure
that
we
reduce
that
number
as
much
as
we
can.
A
There
will
be
more
contributions
coming
in
throughout
the
year.
So
if
we
can
make
sure
that
we're
laser
focused
on
the
things
that
are
coming
up
and
relevant,
then
we'll
be
in
good
shape
so
again
similar
to
the
archiving.
But
since
these
are
actually
in
GitHub,
they
are
more
likely
most
likely
more
recent
and
therefore
we
can
take
a
time
and
discuss
those
things.
A
And
then
Less
on
the
agenda
is
just
a
quick
note
on
the
December
newsletter,
so
that'll
most
likely
be
published
here
early
next
week.
We
are
working
on
the
draft
we
have
updates
from
folks
coming
in
and
we
are
working
on
several
parts.
It's
going
to
be
a
big
newsletter,
because
we
have
to
celebrate
all
of
2022
and
highlight
all
the
cool
things
that
happened,
all
the
wonderful
projects
and
effort
and
work
that
was
done.
A
So
it's
going
to
be
longer
than
the
usual
newsletter,
but
expect
it
sometime
in
the
next
week
and
then
the
list
of
topics
and
stuff
are
available
in
the
previous
meeting
notes.
So
if
you're
our
curious
to
see
what
we
are
talking
about
or
what
we're
going
to
highlight,
it's
all
listed
here,
so
you
can
check
and
share.
If
you
have
Suggestions
by
all
means,
share
them
and
yeah
keep
an
eye
out
now
with
that
being
said,
I'm
gonna
go
ahead
back
to
the
website
issues
list.
A
So
these
are
all
the
ones.
I
clearly
got
Mark
done,
and
then
these
20
or
so
18
are
the
ones
that
I
wasn't
100
sure
on
and
wanted
to
get
a
second
opinion
on
just
to
make
sure
that
I'm
not
totally
off
and
saying
I'm,
not
sure
if
this
apply
still
so.
B
Could
you
paste
the
link
to
that
sheet
so
that
I
could
open
on
my
on
my
machine
as
well
yeah,
it's
it's
in
the
document
right!
Oh.
C
A
Much
easier,
sometimes
but
yeah
so
like
and
there's
stuff
here,
like
update
to
jam
info
and
I-
think
this.
This
actually
kind
of
is
more
relevant.
Now
that
there
was
a
discussion
earlier
about
Jam
setup
and
organizing
and
stuff
like
that.
A
So
maybe
that's
something
to
update,
but
I
don't
know
if
this
is
necessarily
something
we
need
to
update
for
sure
there
are
several
code
link
tickets
and
some
of
them
are
most
of
them
are
done
some
a
couple
of
them
aren't,
but
this
is
also
from
2020,
so
yeah
I
wasn't
really
sure.
I
wasn't
sure
how
relevant
this
would
be
considering
it
was
updated
before
the
world
changed.
C
B
A
So
the
so
I
guess
this
is
where
some
of
the
challenges
come
for
me
like
this
was
Co.
This
was
linked
in
the
comments
of
the
ticket
and
it's
already
been
merged.
B
A
B
B
A
Yes
and
then,
as
far
as
because
I
didn't
realize
it
was
an
epic
prior,
then
Mark,
so
what,
as
far
as
the
Epic
goes,
should
we
just
leave
it
alone?
I.
A
Yeah
and
I
mean
this
one's
gonna
get
moved
over.
This
doesn't
seem
like
it's
necessary
anymore,
so
yeah,
okay,
great
okay,.
A
And
then
there
was
oh
I
know
that
I
did
that
the
detached
plug-in
documentation
so
I
know
that
we've
had
some
recent
developments
with
the
detached
plug-in
from
basil.
Well,.
B
A
B
The
the
wmri
windows
agent
deprecation
is
exactly
this
thing,
create
a
placeholder
on
jenkins.io
for
this,
and
this
one
can
be
closed
out
when
the
when
the
placeholder
on
jenkins.io
is
available,
because
that
one
that's
very
much
a
hey.
We
just
we
just
spent
time
where
you
had
to
listen
to
me
droning
on
about
it,
and
that
exactly
is
what
what
I
was
just
what
I'd
been
describing.
A
Great
I
can
take
care
of
that
using
API
token,
with
GitHub
instruction.
A
I
couldn't
find
that
on
jenkins.io
as
far
as
what
they're
looking
for
since
they
only
have
it
in
the
repository
I
wasn't
sure
yeah
I
just
wasn't
sure
about
this.
One.
A
Cool
yeah
there
was
this
here.
This
is
about
linking
to
the
oh,
that's,
not
the
right
one.
This
one
is
about
linking
to
the
Chinese
translation
or
essentially,
if
someone
were
to
go
to
this
page
specifically
and
then
click
what
they
said,
something
specifically
yeah.
This
looks.
B
Like
I,
you
know
continue:
I
I
hope
this
one's
fixed,
because
we've
we've
tried
diligently
to
fix.
Oh
no
interesting,
okay
go
back
yep,
so
this
is
a
specific
example
of
a
more
General
case.
Okay
and
the
more
General
case
is
that
we
want
all
links
in
the
jenkins.io
site
to
be
site
relative
to
be
site
site
local
right.
We
don't
want
them
to
include
the
www.jenkins.io
URL
in
the
hyperlink,
because
then
they
they
complicate
things.
B
And
if
you
were
to
look
at
that
page
on
on
that
page,
wherever
the
clicked
link
was,
if
you
hover
over
it
notice
that
its
link
goes
to
www.jenkins.io,
not
to
slash
sigs,
okay,
yeah,
I,
see
and
and
there's
actually
a
you
can
close
this
one
and
say
that
it
is
a
duplicate
of
another.
So
because
it
is
it's
a
duplicate
of
a
request,
that's
already
open
on
jenkins.io.
B
A
Thank
you
very
much,
and
then
we
are
over
time.
I
could
I
have
one
last
one
that
I
just
wanted
to
check
in
about
because
it's
more
of
a
I
don't
even
know
what
they're
talking
about
thing,
but
they
were
curious.
If
you
wanted
to
add
Sig
subproject
metadata
to
the
jenkins.io
participate
pages
and
I
wasn't
sure
why.
B
If
it
would
be,
oh
okay,
I
see
right,
so
the
the
idea
here
was
to
consider
updating
the
automated
Matic
page
generator
so
that
the
format
of
the
pages
has
more
information
in
it.
I'd
close
this
one
we'll
add
the
information.
If
we
need
it
it's
now,
three
years
old
yeah
and
with
that
much
age,
there
hasn't
been
enough
interest
for
anyone
to
do
it.
So
just
close,
it.
A
Okay,
great
yeah
and
I'll
check
in
with
I'll
check
in
about
the
rest
of
them,
but
that
takes
care
of
most
like
the
ones
that
I
really
wasn't
sure
about
and
there's
a
couple
other
that
need
a
little
bit
more
discussion,
but
we'll
get
to
it
anyway.
That
takes
care
of
everything
that
I
had
on
the
agenda.
I
want
to
say
thank
you
again
for
joining
us
and
welcome
back
Happy,
New
Year
I
appreciate
it
I'm
glad
everyone's
here
again
and
I
look
forward
to
next
week.
A
So
we'll
see
you,
then
the
video
will
be
available
in
24
or
48
hours.