►
From YouTube: 2023 04 06 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
B
Hello,
welcome
to
the
Jenkins
documentation
office
hours
today
is
April
6th.
This
is
the
EU
US
edition,
and
today
we
have
myself
Mark
Waite
and
Bert
overactin
thanks
for
joining,
as
always
today
on
the
agenda,
a
couple
blog
posts
that
we
have
published
recently,
just
a
note
on
the
Jenkins
Awards
devox
France,
just
to
highlight
that's
coming
shortly.
B
Google
summary
of
code
is
been
making
lots
of
progress.
We
want
to
highlight
some
of
that,
some
of
the
improved
process
CI
process
for
jenkins.io
and
what
that
means
some
discussion
about
how
we
can
resolve
the
number
of
open,
pull
requests
or
at
least
track
them,
and
figure
out
what
to
do
what
we
can
do
to
help
that
the
Jenkins
weekly
and
yesterday's
LTS
release
are
using
new
pgp
signing
Keys
as
well
as
some
the
windows
MSI
installer
signing
certificate.
So
a
few
different
updates
there
we'll
talk
about
this.
B
The
LTS
was
released
successfully
I
just
the
other
day
submitted
some
additional
guidelines
for
the
contributing
guide.
Projects.Io
specifically,
this
was
for
images.
B
The
participation
and
engagement
with
Jenkins
just
I
thought
it
would
be
a
good
topic
to
talk
about
for
a
couple
minutes
and
then
provide
we
have
time
some
early
end
of
life
for
Centos
7
talk.
This
has
been
something
we've
been
discussing
for
a
while
and
then
the
end
of
life
notifications
in
Jenkins
core
again.
B
That
is
something
that
we
have
been
discussing
over
the
last
few
weeks
and
if
we
have
some
time
to
discuss
that
we
can
get
there,
is
there
anything
else
that
should
be
put
on
the
agenda
or
any
questions
or
concerns
before
we
get
started
all
right.
B
So
first
things.
First,
we
have
two
recently
published
blog
posts.
One
is
from
Mark
about
the
new
Linux
repository
signing
keys.
This
is
something
that
we
have
been
working
on
and
just
got
updated.
These
are
in
effect
as
of
weekly,
2.397
and
LTS,
2.3
and
7.2.
So
the
most
recent
builds
have
these
in
integrated.
In
already.
A
You
know,
with
sincere
apologies
to
those
that
we
disrupted,
because
we
didn't
detect
this
soon
enough.
It
would
have
been
much
better
if
we'd,
given
warning
months
previously
that
this
was
coming
and
we
would
have
changed
on
a
knife
edge.
We
didn't,
we
missed
it
and
we
left
people
on
the
LTS
broken
for
about
a
week.
So
unfortunate,
sorry,
we'll
fix
it
we'll
be
better
next
time.
B
And
we
have
a
whole
three
years
to
learn
from
that
mistake,
so
plenty
of
time
and
then
the
other
blog
post.
Oh
and
a
quick
note
on
this,
so
this
information
is
also
linked
in
the
changelog.
The
upgrade
guide
is
available
as
well.
That
contains
the
same
information.
So
we
do
have
this
available
in
several
different
points,
and
this
has
a
little
bit
more
information
and
background
as
far
as
what
happened
and
what
we
did
to
change
things.
B
The
next
blog
post
that
I
wanted
to
highlight
is
one
that
we
published
at
the
end
of
March
from
Bruno,
and
this
is
actually
starting
a
series
of
blog
posts
that
are
about
Android
and
Jenkins,
and
the
relationship
Bruno
has
started
by
giving
a
really
nice
background
about
Jenkins
and
Android
development
and
some
of
the
Intriguing
and
different
ways
that
he's
got
about
using
it,
which
is
really
cool
and
really
interesting.
B
Read,
definitely
got
me
thinking
about
alternative
methods
for
using
Jenkins,
it's
really
cool,
really
out
there
and
yeah,
and
it's
a
series
there's
one
that
we're
working
on
now
and
there
will
be
more
to
come.
So
big.
Thank
you
to
Bruno
for
the
blog
post
series
anything
else.
You
wanted
to
share
a
note
on
that.
For
now.
C
No,
you
did
fantastic
I
wouldn't
have
done
as
good
as
you
presenting
this
articles
so
yo
well,
thank
you.
I
even
want
to
read
it.
That's.
B
Good,
oh
and
fun
note:
this
is
an
AI
generated
image
that
Bruno
was
able
to
come
up
with,
had
AI
come
up
with,
so
it's
a
fun
little
bed
bug
looks
terrified
anyway.
So
moving
on
to
the
rest
of
the
agenda,
so
the
Jenkins
award
voting
period
has
officially
ended.
It
ended
on
March
28th,
thanks
to
everyone
who
participated,
voted
and
nominated
this
year.
B
We
couldn't
do
it
without
any
of
you
and
the
winners
will
be
announced
at
cdcon,
which
is
May
8th
through
9th
in
Vancouver
British
Columbia
Canada
this
year.
So
if
you're
curious,
be
sure
to
register
and
join
us
there.
B
Additionally,
devox
France
is
coming
up
next
week.
We'll
have
Jenkins
presence
there,
we'll
have
Bruno
and
I
think
at
least
one
or
two
other
people
will
be
there
with
Bruno.
C
B
Beautiful
and
then
Adrian
will
be
able
to
be
there
with
Bruno,
so
we've
got
the
Dream
Team
there
amazing.
Thank
you
very
much.
Bruno.
C
Appreciate
it
you're
welcome
it's
a
gift
to
me
being
in
devops
being
able
to
talk
with
Jenkins
users
and
so
on
and
being
with
the
best
of
them.
You
know
Adrian
and
Airway
will
host
aim.
Albert.
Ask
me
anything
about
Jenkins
and
I
hope
that
we
will
have
interesting
questions
and
we'll
give
stickers.
B
Stickers
are
always
fun,
it's
always
a
driving
point,
so
good
call
all
right
next
up
on
the
agenda,
so
quick
update
on
Google
summer
of
code.
So
at
this
point
in
time
the
proposal
submission
deadline
is
passed.
We
got
55
valid
proposals
submitted
this
year,
which
is
incredible
comparatively
to
the
last
handful
of
years.
B
This
is
an
outstanding
number
of
proposals
and,
more
importantly,
showcases
just
how
interested
people
are
in
joining
the
project
and
contributing.
This
is
a
fantastic
big
thanks
to
Jean,
Mark
Mason
who's
been
the
org
admin,
lead
for
this
project
and
is
helming
this,
along
with
Bruno
and
Alyssa
Tong
and
Chris
Stern.
B
Without
all
of
the
work
that
they're
doing
this
would
not
be
possible,
and
right
now
we're
going
to
have.
It
looks
like
we'll
have
four
projects
for
Google
summer
of
code
and
lots
of
work
to
do
with
those.
We
have
a
lead
Mentor
for
each
project,
which
is
fantastic.
B
Everything
is
just
shaping
up
to
look
really
good.
This
year,
it's
it's
a
little
bit
of
a
problem
that
we
have
too
much
interest
in
the
project.
You
know
it's
a
good
problem
to
have,
but
there's
a
lot
of
folks
out
there
that
want
to
contribute
and
be
part
of
it
and
we're
just
doing
what
we
can
to
make
sure
that
that's
that's
what
happens
and
more
details
come
on
Google
summer
of
code
there
we
are
getting
going
to
be
getting
into
the
initial
phase
of
community
building
and
interaction.
B
The
next
one
on
the
list
is
the
improved
CI
process
for
jenkins.io,
so
arabe
Limer
has
merged
change,
which
saves
time
in
disk
space
in
the
CI
jobs.
Ultimately,
this
means
36
gigabytes,
total
of
disk
space
freed
up
for
ci.jenkins.io,
which
is
massive.
This
also
means
that
there
is
20
seconds
saved
for
job
execution
due
to
the
not
wasting
disk
space,
so
around
four
percent
of
the
total
job
time
now,
I
didn't
have
as
much
Insight
personally
Mark
is
there
anything
else
you
wanted
to
share
about
this
topic.
A
B
Great,
thank
you
very
much.
In
addition
to
that,
we
have
a
talk.
We
were
talking
about
reducing
the
number
of
open,
pull
requests.
Obviously,
open
pull
requests.
We
want
to
have
closed
and
merged
people
are
working
hard
and
want
to
make
sure
they're
contributing
and
that
their
contribution
contributions
get
noticed.
B
So
the
idea
is
that
we
can
reduce
the
open
number
of
pull
requests,
and
this
will
also
help
with
disk
space
usage
on
ci.jenkins.io
and,
ultimately,
just
something
that
needs
to
happen.
We
were
at
roughly
30
or
so
last
year
it's
gotten
increased,
so
we
need
to
make
sure
that
we're
doing
better
about
reviewing
and
closing
out
pull
requests,
but
it
takes
a
village
community
process.
So
anyone
is
more
than
welcome
to
join
in
on
that.
B
The
idea
of
participating
and
contributing
in
Jenkins
is
not
that
you
have
to
make
code
changes
or
any
kind
of
grand
update
to
Jenkins
or
jenkins.io
testing
code
reviewing
code
reviewing
pull
requests.
Even
if
it's
not
code,
these
sort
of
things
go
a
long
way
with
not
only
participating
and
contributing,
but
also
making
sure
that
people
feel
their
work
is
appreciated
and
that
it's
engaging
with
others.
Nobody
wants
to
work
on
something
by
themselves
for
their
own
benefit
in
this
sort
of
Open
Source
Community.
This
is
the
idea
like
open
source.
B
Community
is
the
idea,
so
we
want
to
encourage
people
to
just
find
what
inspires
them,
what
they
find
they
want
to
work
on,
what
interests
them
and
work
on
that
and
take
those
small
steps
to
get
to
the
point
where
you
can
create
code,
changes
or
big
sweeping.
You
know
UI
ux
changes
or
anything
along
those
lines,
so
something
that
we'll
be
keeping
an
eye
on.
B
As
we
said
before,
the
Jenkins
weekly
release,
starting
with
2.397
and
the
LTS
release,
starting
yesterday
with
2.387.2,
are
using
the
new
pgp
signing
Keys.
There
is
a
blog
post
in
community
comments
for
these,
so
great
instructions
from
Mark,
as
we
said
earlier,
a
little
background
and
further
discussion
from
the
community.
This
is
great
wow,
so
this
is
directly
linked
to
the
discourse
site
that
we
have.
B
So
all
these
are
direct
from
users
based
on
their
findings
and
usage
of
this,
so
lots
of
great
info
there
and
a
great
interaction
from
the
community.
There
don't
know
that
these
two
I
don't
think
these
things
are
relevant
in
this
case,
obviously
rid
of
those
for
the
type
being
LTS
2.8387.2
released
yesterday
successfully,
a
user
did
point
out
that
the
change
login
upgrade
guide
had
the
incorrect
date,
so
we
fixed
that.
Thank
you
to
mark
for
catching
and
or
fixing
that
and
I
forget
who
the
user
is.
B
One
of
the
other
signing
updates
that
came
that
came
through
is
the
windows
MSI
installer.
This
was
not
available
prior
to
a
few
days
ago,
but
thankfully
Linux
Foundation
was
able
to
get
everything
resolved
in
terms
of
any
sort
of
legal
complications
or
any
other
concerns
they
have.
We
now
have
this.
It
is
designed
it's
ready
to
go
it's
in
it's
installed,
so
this
is
now
available.
C
They
said
no,
no,
not
today,
maybe
tomorrow,
yes,
lawyers
are
involved,
whoa
that
was
kind
of
scary
and
then
yes,
finally,
we
got
the
answer.
Everything
works
perfectly
and
windows.
Users
will
be
relieved,
I,
guess,
wow,
fantastic
work.
B
Yeah
and
and
I
just
thank
you
to
everyone
that
was
involved
in
getting
this
updated
and
fixed
and
changed
over
I
know
it
was
a
lot
of
work
behind
the
scenes
to
get
this
all
taken
care
of
and
in
such
a
short
time
period,
so
huge
and
yeah
and
everything's
signed.
So
there's
no
risk
or
concern
for
any
sort
of
you
know,
danger
there
or
unsecuredness
there.
So
big,
big,
big,
big,
big
win
for
Windows
users
in
particular,
so
fantastic.
C
B
All
right
something
that
we've
been
discussing
and
something
that
I
have
finally
been
able
to
get
some
pull
requests
put
in
for
and
making
a
lot
good
Headway
on
is
additional
guidelines
to
the
jenkins.io
contributing
guide.
So
my
main
focus
has
been
images
and
then,
after
that,
documentation
and
book
submissions,
so
I've
actually
submitted
the
image
guidelines.
So
that
pull
request
is
here.
B
It's
not
anything
groundbreaking.
It
is
not
anything
that
is
unexpected.
It
is
very
straightforward
stuff,
like
there's
a
lot
of
document,
just
documentation,
formatting
updates
I
made
as
well,
but
for
images.
It's
definitely
using
consistent
screen
sizes,
making
sure
that
the
area
is
focused,
making
sure
that
when
you
go
to
add
an
image
or
add
a
screenshot
that
it's
providing
the
right
content
and
context
for
any
surrounding
information.
B
So
just
really
simple,
straightforward
stuff
that
we
can,
you
know,
implement
or
set
as
a
guide
to
help
make
sure
that
things
are
aligned
completely
going
forward
or
that
our
accessibility
rating
can
go
up.
One
of
the
things
that
I've
been
more
concerned
with
in
this
is
making
sure
that
alt
text
for
images
is
used
to
its
fullest
extent.
Asci
dot
can
actually
handle
full
sentence
structure
for
all
texts,
so
for
screen.
Readers
for
the
anyone
with
accessibility
needs
that
stuff's
kind
of
really
important.
C
Yeah,
that
will
prove
handy
for
sure
when
I
first
started
to
interact
with
the
Jenkins
Community
I
started
by
making
a
few
screenshots.
You
know
because
the
UI
was
changing
and
I
made
a
lot
of
Errors,
because
a
lot
of
guidelines
were
just
implicit.
People
knew,
but
it
wasn't
written
anywhere.
So
I
had
a
lot
of
back
and
forth.
No,
it's
wrong.
Why
is
it
wrong?
Or
this
way
you
forgot
that
and
the
compression
and
the
odd
and
yeah
now
that
it's
written
newcomers
will
have
it's
easier?
C
B
And
I
I,
actually
I
forgot
to
put
the
compression
aspect
of
in
that
Bruno's
office.
Thank
you
very
much
for
the
reminder
on
that.
Yeah
screenshots.
Certain
images
are
an
easy
way
to
get
involved
in
making
suggest
a
change
or
contribute
something.
We
have
there's
a
new
contributor
right
now.
B
I'm,
sorry
I
forget
the
name
but
they've
been
working
on
the
UI
updates
that
came
along
with
2.395,
where
manage
Jenkins
naming
conventions
are
simplified
and
whatnot,
so
they've
been
just
doing
that
and
that's
a
fantastic
way
to
get
involved
and
get
some
low-hanging
fruit.
So
yeah.
C
Yep
and
you
know
what
with
gsoc
coming,
there
is
a
project
about
automating
screenshots
for
the
documentation,
and
that
could
help
if
this
project
is
still
with
us
in
a
few
months
from
now.
That
will
help
the
contributor
to
have
the
right
behavior
when
taking
screenshots,
because
everything
now
is
available.
You
know
how
you're
supposed
to
take
screenshots
with
that
guide.
B
Yeah
and
I
I
made
sure
to
include
the
responsive
design
mode
feature
that
most
browsers
have
so
that
we
can
make
sure
a
that
the
screenshots
are
all
using
roughly
the
same
size
range.
But
more
importantly,
so
we
can
take
a
high
quality
screenshot
that
is
going
to
render
properly
on
either
a
large
desktop
or
a
phone.
C
B
Why
so
yeah
I've
noticed
that
as
well
going
through
some
of
the
screenshots
and
Pages,
especially
like
I,
said
with
the
newer
contributors
adding
screenshots
and
stuff,
and
it's
it's
odd
that
it's
such
a
small
size,
but
it
still
is
displayed,
but
this
with
this
we
can
have
some
form
of
consistency,
and
that
makes
it
so
folks,
with
a
bigger
screen,
won't
be
able
to
take
an
image.
That's,
unfortunately,
scaled
more
towards
their
screen
than
other
people's
I
ran
into
that
when
I
was
first
starting
with
Jenkins
work.
B
So
it's
something
that
I
get
it's
an
implied
or
yeah
understood
thing
that
you
don't
necessarily
know
until
someone
tells
you.
So
let's
tell
people
all
these
things,
but
yeah
and
again
that's
I
wanted
to
get
the
image
guidelines
in
first,
because
I
have
seen
people
working
on
them.
B
The
documentation
is
already
laid
out
pretty
well
and
book
submissions
are
a
new
thing,
so
this
was
most
important
for
me
now
that
we've
gotten
this
in
there
once
I
have
seen
some
conversation
and
responses
happen,
I'll
be
far
more
inclined
to
merge
it
once
that's
accepted
and
then
add
the
other
guidelines
from
there.
I've
also
started
a
community
discourse
bed
for
this.
So
if
anyone
does
want
to
have
a
further
discussion
about
this
or
any
other
guidelines,
there
is
a
place
to
do
so.
B
I,
don't
think
I've
had
any
responses
yet.
So
it's
a
little
lonely
in
there
with
me
alone,
but
you
know
I'm
waiting
but
yeah,
so
plenty
of
places
to
talk
about
it.
The
pull
request
is
open,
so
it
can
be
reviewed,
suggested,
suggested
added
whatever
that
anyone
feels
like
so
yeah
just
keep
an
eye
out
for
more
on
that
and
then
the
next
thing
on
the
list
again
ties
back
into
the
idea
of
just
testing
trying
out
review,
reviewing
pull
requests
that
come
through
we've
had
I've.
B
It's
a
solidarity
feeling,
it's
a
matter
of
knowing
that
your
work's
noticed
and
and
appreciated,
which
is
really
really
huge
and
crucial
to
anyone
doing
open
source
work.
This
is
that
kind
of
appreciation.
Gratitude
acknowledgment
is
something
that
we
want
to
constantly
have
for
everyone
involved.
So
if
you're
not
feeling
confident
in
your
coding
skills,
like
myself,
there's
ways
to
review
and
test
documentation,
updates,
there's
ways
to
review
simple
code
changes
that
are
not
so
involved
that
it
can't
be
discerned
are
determined.
B
B
These
are
all
amazing
ways
and
really
accessible
ways
to
get
involved
with
Jenkins.
As
we
see
the
Google
summer
of
code
participants
ramping
up
as
we
start
seeing
more
people
becoming
involved,
you
know
this
is
the
kind
of
interaction
we
want
to
support.
It
can
feel
very
daunting
to
get
started
with
Jenkins,
if
you're,
not
sure
where
you
want
to
start
or
how
you
want
to.
You
know,
add
I've
seen
it
several
times
in
the
gitter
channels
of
people,
saying:
hey,
I,
I'm,
new
itching
and
I
want
to
get
started.
B
Where
can
I
start
and
nine
times
out
of
ten
I
feel
that
they're
they're
one
of
their
first
things
they
say,
is
it's
just
very
overwhelming,
there's
so
much
it's
a
big
big
big
big
project
like
no
one's
gonna,
sit
here
and
dispute
that
by
any
means,
but
if
we
can
give
folks
either
a
detailed
way
of
how
they
can
figure
out
what
they
want
to
do
or
Point
them
in
places
where
they
can
then
figure
out
what
they
want
to
do.
Yeah.
That's.
C
Just
when
I
hear
yeah
came
in
to
the
Jenkins
Community
I
just
had
to
look
at
the
repos
and
found
that
there
were
more
than
2.5
k,
repos,
so
I
was
I
was
freaking
out
here.
Where
should
I
start?
That's?
C
Well,
that's
quite
something
and
later
on
in
the
process,
I
was
kind
of
bother
because
I
had
missed
a
few
interesting
PR.
That
I
should
have
reviewed
or
participated
in
because
I
hadn't
put
the
notifications
on
so
I
put
the
notifications
on
and
then
I
was
overwhelmed
by
the
quantity
of
notification
that
was
I.
Couldn't
do
anything
with
them
just
pining
up
so
I,
don't
know
what
is
the
right
thing
to
do
with
the
Jenkins
repos
but
yeah
you
have
maybe
to
do
some
cherry
picking
every
day
or
something,
but
for
sure.
C
B
And
I
immersed
your
line
from
your
forthcoming
blog
post,
the
drink,
there's
Jenkins
has
some
way
to
fill
that
need
whatever
it
is.
Jenkins
has
a
way
to
fill
that
need
for
you.
It
might
be
a
specific
plugin
that
helps
you
do
your
job.
It
might
be.
You
feel,
inspired
to
make
a
new
logo
like
the
possibility
is
just
run
the
full
gamut
of
simple
to
complex.
B
I
can't
State
enough
that,
as
a
Newark
contributor
and
participant
of
Jenkins
that
it's
very
overwhelming,
if
you're
not
really
sure
where
to
get
started,
it
can
be
very
daunting
and
it
can
be
kind
of
scary
to
be
real.
Finding
that
one
thing
that
can
help
anchor
you
to
the
project
or
help
make
sense
of
a
part
of
the
project,
even
a
piece
of
the
project.
C
Yeah,
so
it's
also
very
rewarding
I.
Remember
at
the
beginning
of
my
journey
with
Jenkins
I
had
a
need
with
arm
32-bits
Docker
images
for
Jenkins,
so
I
made
one
and
I
made
my
first
PR
and
it
didn't
work
because
I
didn't
know
the
project
enough
for
it
to
be
an
effective
PR.
But
people
guided
me.
C
These
PR
got
abandoned.
We
don't
have
Docker
images
for
Jenkins
arm32
now,
but
it
will
come
in
a
few
months
from
now
anyway,
but
we
now
have
some
arm
64
bits
because
I
made
another
PR
and
then
got
objected.
The
community
globally
is
pretty
welcoming.
So
if
one
subject
does
interest
you
with
Jenkins,
you
should
find
mentors
people
willing
to
help
you
in
in
onboard
you
on
the
Jenkins
Community.
That's
something
I,
really
love
with
the
Jenkins
community.
B
Yeah
I've
had
the
same
experience
frankly
I
my
first
PR's
definitely
didn't
work.
I
was
not
sure
if
I
was
making
things
properly.
You
know
the
whole
nine
yards
and
and
the
community
stepped
up
I've
felt
more
welcome
and
engaged
with
the
community
than
anything
else
before,
and
it
really
does
make
a
difference
when
you're
trying
to
just
start
having
that
person
to
introduce
you
to
Jenkins
is
amazing
having
people
in
that
you've
never
met
and
might
not
ever
meet
thousands
of
miles
away.
B
Work
with
you
help
you
online
asynchronously,
regardless
I
mean
that's
a
really
neat
experience
and
something
that
not
everyone
can
say
frankly.
So
I
think
that
just
makes
this
a
lot
more
of
a
special
community
in
terms
of
the
Outreach
and
engagement
that
we
offer
for
new
and
returning
users.
Yes,.
C
Indeed,
I
won't
be
naming
names
of
all
their
open
source
communities,
but
I've
got
some
other
experience
with
other
open
source
community.
That
did
not
go
that
well.
B
B
On
that
note,
there's
a
couple
like
I
said:
there
was
a
couple
of
other
points
here,
so
just
really
quickly.
Early
end
of
life
for
Cento
7
is
something
that
Mark
has
been
pushing
for
it's
approaching
anyway.
It's
no
longer
the
Centro
7
is
no
longer
being
supported.
B
It's
been
in
maintenance
mode
since
2020,
and
there
are
plenty
of
alternative
options
and
recommended
options
that
we
have
like
all
the
Linux
Rocky
Linux
Oracle
like
there
are
several
choices
here,
we're
starting
to
incorporate
those
into
the
documentation,
but
this
is
something
that
we
have
been
discussing
and
considering
for
a
little
bit,
and
at
this
point
we
just
really
just
need
to
get
a
enhancement
proposal
going
for
it,
and
then
we
can
track
everything.
B
Have
those
conversations
there
and
work
on
that
so
more
to
come
when
we
get
that
JP
actually
set
up
and
something
else,
the
end
of
life
notifications
to
Jenkins
core
again.
This
is
something
that
we've
been
discussing.
We
want
to
find
a
general
solution
for
end
of
life
date
for
any
of
the
products
or
platforms
that
we're
using
so
the
center
seven
I
think
Debbie
in
the
older
Debbie
inversions
older,
like
just
any
older
version
of
stuff.
That's
coming
end
of
life.
B
We
have
there's
sites
like
end
of
life.date
that
have
an
API
we
can
interact
with,
but
ultimately
just
we
want
to
find
a
way
to
alert
users.
Let
users
know
that
this
end
of
life
is
coming
with
enough
time
and
Cadence
to
have
give
them
the
ability
to
update
or
find
that
other
solution.
B
You
know
we're
not
going
to
stop
supporting
things
on
the
drop
of
a
hat
this.
These
are
things
that
need
to
be
taken
consideration
and
worked
through
very
diligently.
So
Nothing's
Gonna
just
happen
in
that
sense,
but
we
do
want
to
give
that
courtesy
to
users
of
Jenkins
so
again
more
to
come
on
that
when
we
have
better
idea
of
what
the
output
will
look
like.
B
Is
there
anything
else
that
you
want
to
talk
about
Bruno
on
the
call?
No.
B
And
yeah
and,
like
I,
said
Mark
jumped
off
earlier
since
we're
doing
the
2.387.2
live
stream
between
him
and
Darren
Pope.
So
that's
gonna
be
available
on
YouTube
and
it's
happening
live
right
now
so
yeah.
If
you
want
to
go
check
it
out
by
all
means.
However,
that
is
the
end
for
our
session
today.
Thank
you
as
always
for
joining,
and
the
video
for
this
will
be
available
in
24
to
48
hours.
Thank
you
very
much.
Take
care.
Thank
you.
Kimmy.