►
From YouTube: 2023 04 20 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
to
the
Jenkins
documentation
office
hours
today
is
the
April
20th
2023
Edition
EU
us
time.
Today
we
have
myself
and
Mark
White.
If
anyone
else
joins
us,
we
are
more
than
welcome
to
invite
them
in
on
the
agenda.
So
for
today,
we've
got
a
note
about
the
doc's
office
hours
Asia,
which
is
canceled
tonight.
Google
summer
code
update
next
LTS
release,
information
and
next
Baseline
selection.
A
A
We
actually
implemented
a
or
yeah
implemented
a
success
stories,
navigation
Link
in
the
top
menu.
So
thank
you
to
Gavin
Mogan
for
adding
that
to
the
components
and
header
alternative
ways
to
handle
stale
documentation
pull
requests.
This
is
something
we've
been
discussing
recently
and
of
Life
notifications
in
Jenkins
core
again.
A
Is
there
anything
else
that
needs
to
go
on
the
agenda
or
does
that
cover
everything
for
you
Monarch?
That's
it.
Okay,
so
first
thing
on
the
agenda,
so
tonight,
doc's
office
hours
for
Asia
is
canceled.
Mark
will
be
available
so
for
today
that
is
going
to
be
canceled.
A
Next
week
it's
going
to
be
back
to
normal,
though
so
Google
summer
code
is
really
coming
up
to
the
starting
point,
which
is
exciting
for
getting
going
and
socialization
and
everything
so
the
yimin
gong,
who
is
a
mentor
who's.
A
new
Mentor
this
year
returns
after
being
a
contributor
last
year,
which
is
really
exciting.
They
were
able
to.
A
They
were
working
on
the
Jenkins
file,
Runner
project,
so
great
to
have
them
back
and
in
a
different
role,
and
then
Google
is
going
to
announce
the
accepted
contributors
on
May
4th.
After
that,
we
will
share
posts,
tweets
LinkedIn
posts
regarding
the
accepted
applicants
and
the
announcement.
A
So
we
will
have
our
own
communication
there
and
then
the
next
day,
May
5th
is
going
to
be
docs
or
not
docs
gsoc
office
hours
to
welcome
the
accepted
applicants,
so
in
the
next
couple
weeks
we'll
be
really
getting
down
to
what
this
is
going
to
look
like
who's
going
to
be
involved
and
we're
very,
very
excited
to
enter
that
period.
A
Next
up,
so
we
have
LTS
2.387.3
coming
out
on
May
3rd,
so
Chris
Stern
has
sent
out
the
release
candidate
email
as
of
Tuesday,
so
it
is
ready
to
test
and
download
if
you
can
spare
some
time
and
do
that,
please
do
so
provide
any
feedback
and
the
change
login
upgrade
guide
has
been
created
and
added
to
the
checklist,
SO
waiting
on
back
ports
and
anything
else
that
might
come
up.
A
So
that
is
not
a
final
product,
but
a
work
in
progress
for
the
time
being,
I'll
be
keeping
an
eye
out
for
any
changes.
Hesitations
delays,
anything
else
that
might
come
up
and
we'll
take
it
from
there
on
the
LTS
topic.
So
the
Baseline
selection
was
actually
due
yesterday,
but
we
are
now
we're
aware
of
it,
and
this
needs
to
be
decided
in
the
developer.
A
Mailing
list
so
expect
communication
for
that
really
really
really
soon,
if
not
today,
so
we'll
get
that
communication
out
there
keep
an
eye
on
the
developer
mailing
list
and
the
Baseline
selection
will
be
figured
out
next
thing
on
the
agenda.
Here
is
the
Java
updates,
so
within
the
last
week,
or
so
maybe
the
last
couple
days,
it
looks
like
actually
timarin,
open,
jdk
and
Oracle
have
posted
updates
for
their
Java
version.
A
So
Tamarin,
for
instance,
is
on
Java,
has
Java
11.0.19
Java
17.0.7
and
to
run
20,
which
is
really
exciting,
so
open,
jdk
and
Oracle
have
had
similar
updates.
Timaran
just
happens
to
be
a
really
positive
experience,
which
is
why
we've
got
them
listed
here,
but
all
three
of
these
links
lead
to
release,
notes
and
updates
for
all
of
the
different
Java
versions
that
are
being
provided
by
each
company.
A
So
right
here
at
the
top
11.0.19,
so
downloads
are
available
and
release
notes
as
well
same
thing
for
open
jdk
and
they
have
all
their
information
here,
release
notes,
downloads
and
Oracle.
A
Where
again
they
have
all
the
different
release
notes.
So
we
can
go
into
any
of
these
c1707
and
actually
get
the
release
notes,
and
you
can
see
here-
this
is
just
April
18th
so
this
week
important
to
note.
Obviously
we
want
to
make
sure
everyone's
up
to
date
and
make
sure
that
not
only
the
documentation,
but
all
users
are
as
Upstate
as
can
be,
make
sure
that
there's
no
issues.
A
A
Not
only
is
that
going
to
be
a
wonderful
opportunity,
an
event
to
just
meet
up
and
appreciate
continuous
delivery,
but
there's
also
going
to
be
where
the
Jenkins
Awards
winners
are
presented
with
their
Awards.
That
will
also
happen
for
any
other
Awards
winner,
so
CDF
techton
et
cetera
Etc,
but
it's
going
to
be
an
exciting
time
and
we
did
publish
a
blog
post
recently
from
the
CD
Foundation
sharing
Jenkins
themes
sessions.
A
So
a
handful
of
really
nice
sessions
and
Keynotes
to
check
out
some
are
clearly
Jenkins,
like
the
testing
hundreds
of
os
images,
but
everything
is
going
to
focus
on
continuous
delivery
and
Jenkins
to
that
extent
and
Mark's
also
going
to
be
giving
a
keynote
panel
or
part
of
the
keynote
panel
and
sharing
a
different
talk
entirely
as
well.
So
amazing,
fantastic.
Thank
you
very
much
Mark
for
stepping
up
and
being
part
of
it
and
representing
Jenkins
thanks.
A
A
I've
created
a
GitHub
issue,
so
we
can
track
this
and
I've
gone
through
and
explained
the
background
of
what
we're
looking
to
do.
Java
17
is
fully
supported
by
Jenkins,
so
what
we
want
to
do
is
transition
the
documentation,
such
as
installation
and
usage
and
Java
requirements
stuff
like
that
to
use
Java
17
as
opposed
to
Java
11,
and
this
is
strictly
because
Java
17
provides
more
functionality,
better
testing
and
just
overall
support
for
development.
A
Job
11
is
still
supported,
100
for
ijakins
by
Jenkins
for
the
foreseeable
future,
and
when
that
comes
time
to
discuss
end
of
life,
then
we'll
figure
that
out,
but
this
is
not
taking
anything
away.
This
is
just
in
reassuring
people
that
using
Java
17
is
the
way
to
go
it's
the
way
of
the
future.
That
is
going
to
be
what
we
should
be
on
soon
enough
anyway.
A
So
the
idea
is
that
we
can
transition
and
make
this
hat,
make
this
visible
and
known
to
people
before
that
that
end-of-life
approaches
people
can
migrate
transition
at
their
own
speed,
and
we
don't
have
to
worry
about
rushing.
A
This
is
inspired
by
the
fact
that
Debian
12,
when
it
does
release,
will
not
ship
with
jdk
11.,
regardless
of
when
the
release
for
that
happens
and
regardless
of
what
they
do
complete
end
up
doing
with
it.
The
idea
for
us
to
transition
to
documentation
is
gonna.
This
is
still
happening,
regardless
of
that
time
frame
for
them.
A
This
is
around
the
time
that
we
had
described
and
decided
upon
the
April
May
area,
so
we're
going
to
commit
and
go
through
with
that
and
here
in
the
issue,
I've
found
a
few
links
that
do
have
Java
information
that
can
be
updated
to
use
Java
17..
A
lot
of
it
is
the
installing
information
and
documentation,
but
these
are
things
that
I
have
been
I've,
been
going
through
the
documentation
to
try
and
find
any
other
areas.
A
There
was
one
that
I
found
for
the
assist
managing
system,
D
services
that
we
can
also
include
in
there.
I
just
need
to
put
that
link
in
this
issue,
so
Mark,
where
what
is
there
anything
that,
like
I,
haven't
covered
or
mentioned,
or
anything
here
that
you'd
like
to
make
sure
we
have
either
in
the
issue
or
on
in
the
notes
here.
No.
B
A
Thank
you
very
much
appreciate
it
and
yeah,
and
this
is
something
that
I'll
be
working
on
continuously
until
we
get
this
all
taken
care
of
so
I'm
open
to
question.
Support
suggestions,
anything
like
that
whatsoever.
A
Yeah
and
yeah,
we
still
have
to
get
to
the
nitty-gritty
of
it
and
figure
out
how
we're
going
to
go
about
that,
but
the
important
things
here
are
making
sure
that
everything
is
tested
and
verified
and
that
we're
not
providing
any
misinformation
when
doing
this
update
so
yeah,
we'll
figure
that
part
out
Mark
I'm
sure
it's
not
as
difficult
as
making
it
sound
right
now.
A
Thank
you,
yeah.
Thank
you.
Next
thing,
I
wanted
to
bring
up
on
the
agenda
is
that
we
now
have
a
navigation
Link
in
the
jenkins.io
header
for
success
stories,
which
leads
to
the
stories.jinghens.io
site.
This
is
something
very
recently
implemented.
A
Thank
you
again
to
both
Alex,
Brandeis
and
Gavin
for
getting
this
implemented
and
suggesting
this
is
great
and
something
that
we
are
really
proud
to
share
and
want
to
make
sure
that
people
can
see
that
and
know
it
so
putting
it
up
in
the
header
is
just
fantastic
and
it
makes
it
front
and
center
for
people.
A
So
that's
just
something
new.
Just
keep
an
eye
out.
More
we've
been
like
I
mentioned
previously,
we've
been
discussing
alternate
ways
to
handle
stale
documentation,
pull
requests.
Now.
This
is
a
little
more
involved
because
we
do
have
to
take
a
look
at
the
pull
requests
themselves.
Make
sure
that
the
information
is
either
valuable
or
not,
and
then,
depending
on
what
that
result,
is
we
can
kind
of
address
things
from
there.
A
If
the
pull
request
is
valuable,
we
want
to
make
sure
that
that's
not
lost,
so
Mark
has
gone
through
and
put
a
handful
of
thought.
Labels
on
the
older
pull
requests
in
the
jenkins.io
repo.
So
here
we
have
page
one
there's
nothing
clear
or
there's
nothing
solid
there,
but
when
we
look
at
the
second
page
and
we
go
down
to
the
low
the
older
dates
such
as
2019
2020,
we
can
see
the
stalled
label
here
applied.
These
are
all
really
valuable
and
necessary
pull
requests.
A
However,
they
haven't
been
worked
on
and
they
need
more
time
and
changes
and
edits
made.
So
we
do
not
want
to
lose
that
they
are
stalled.
We
we've
been
discussing
various
ways
to
make
sure
that
that
doesn't
get
lost
and
is
visible,
so
I
was
thinking
something
along
the
lines
of
maybe
making
them
into
an
issue
and
linking
back
to
the
pull
request
or
just
copying
the
information
over
to
provide
that
you
know
these
are
very
much
in
progress
and
need
some
assistance
from
the
from
whoever
would
like
to
take
a
look
at
them.
A
It's
a
great
starting
point
for
a
lot
of
documentation,
and
you
can
also
see
here
that
a
lot
of
these
are
also
Wiki.
Migration
pull
requests.
So
again,
this
is
information
we've
had.
We
need
to
verify
that
it's
up
to
date
and
correct
for
now,
but
there
there's
ways
that
we
can
do
that
without
having
to
you
know
hold
on
to
these
older
ones.
A
Jenkins
core
is
using
a
stalled
label
just
like
that
for
their
own
pull
request.
So
this
is
something
that
makes
us
a
little
bit
more
aligned
and
honestly
just
makes
sense.
So
this
is
great
to
have-
and
this
is
a
good
practice
to
continue
on
doing
if
the
request
is
not
valuable,
we'll
just
close
it
out.
If
there's
been
no
action,
no
response
from
the
contributor
and
something
else
that
we're
considering
is
proposed
for
clothes.
A
That
is
a
label
that
Jenkins
core
uses
that
would
be
for
stuff
that
we're
just
not
going
to
accept
or
stuff.
That's
becomes
inactive
so
again
a
way
to
navigate
those
pull
requests
that
maybe
aren't
worth
it
or
that
have
been
there
for
so
long
that
maybe
it's
not
correct
anymore,
because
it's
a
little
out
of
date,
those
things
can
still
be
updated
and
changed
and
added.
But
for
the
pull
request
itself,
we
can
consider
a
few
different
options.
A
On
the
end
of
live
notifications
in
Jenkins
core,
first
of
all,
thank
you
to
both
Alex
brandes
and
Chris
Stern,
who
have
been
incredibly
helpful
as
providing
Insight
opinions
and
just
being
a
sounding
board
for
this
idea.
This
is
something
that
we're
really
adamant
about
getting
figured
out
working
on
and
applying
so
first
thing
is
figuring
out
whether
or
not
we
can
do
this
with
the
administrative
monitor
should
be
pretty
straightforward
and
should
be
possible.
A
No
real
issues
there
that
I
could
see,
but
they've
we've
they've
we've
been
able
to
compile
a
really
nice
example
of
what
the
message
can
look
like
what
kind
of
information
it
can
contain,
what
things
it
should
be
checking
for
and
how
it
could
be
displayed
Mark.
Is
there
anything
that
you'd
like
to
add
in
on
this
just
I'm
being
I'm
being
a
very
high
level
overview
right
now?
So,
if
there's
anything
more
detailed,
you'd
like
to
share
no.
B
Well,
so
the
the
the
details
that
are
there
are
a
result
of
the
conversations
there
are
still
some
gaps.
There
are
some
things
that
this
couldn't
do
for
us
and
we'll
have
to
I
hope.
Someone
will
have
a
bright
idea
as
to
how
to
how
to
allow
it
to
do
it
for
us
or
to
do
something
extension
of
it
to
do
it
right
now.
For
instance,
when
we
end
support
for
Java
11
someday
in
the
future,
let's
say
we're
in
October
we're
in
late
2024
and
we're
declaring
the
end
of
life
for
Java
11..
B
That's
not
a
file
based
end
of
life,
so
we
can't
detect
that
we're
running
on
Java
11,
based
on
a
file.
It's
easy
to
detect
that
we're
on
Java,
11.
Jenkins
knows
very
well
what
Java's
run
version
it's
running,
but
it,
but
in
the
context
of
this
concept,
of
using
an
administrative
monitor,
that's
based
on
a
file,
it
doesn't
work
here
and
so
I'm
I
think
this
is
valuable.
I
think
it's
useful
and
I'll
I'm
going
to
continue
with
it.
A
Great
awesome,
thank
you
very
much
Mark
that
helps
up,
clarify
and
explain
a
little
bit,
and
that
makes
absolute
sense
as
to
why
it
would
not
be
able
to
necessarily
determine
the
Java
version
in
that
case,
so
yeah.
Thank
you
and
again.
This
is
something
that
will
need
a
jab
or
a
pull
request
or
something
to
submit
so
that
we
can
follow
it
and
keep
any
feedback
in
or
worked
on
tied
to
it.
A
So
do
come,
and
then
the
last
thing
that
I
had
on
the
agenda
today
was
just
discussing
the
intended
early
end
of
life
for
Centos
7
for
Jenkins.
This
is
something
that
we've
been
discussing.
There
are
lots
of
reasons
to
move
forward
with
this
end
of
life
for
Centos
7,
namely
it's
relying
on
a
lot
of
older
versions,
and
just
you
know
from
the
details
here.
It's
missing
things.
It's
just
not
the
optimal
way
to
go.
A
A
So
this
will
be
a
J
Jenkins
enhancement
proposal
that
will
be
created
and
again
will
tie
work
to
it
and
connect
any
suggestions,
feedback
or
discussions
to
it.
For
right
now
there
have
been
a
couple
updates
already
made
in
the
documentation
to
utilize
Alma
and
Rocky
Linux
over
the
Centos
7
image,
so
it
is
being
implemented.
It's
just
a
matter
of
finding
all
those
little
Corners
that
it's
hiding
and
updating
them.
Accordingly,.
A
And
that
comes
to
the
end
of
our
agenda
today.
Mark
did
you
have
anything
else
that
you'd
like
to
share
or
any
comments
or
anything
like
that?
Nothing.
A
Sounds
good.
Thank
you
very
much
all
right.
So
then
we'll
call
it
there
nice
smooth,
quick
today.
Thank
you.
Very
much.
Recording
will
be
available
in
24
to
48
hours.
Maybe
a
little
bit
longer.
Mark's
got
a
lot
of
stuff
going
on
this
weekend,
so
lots
of
fun,
can't
kids
camps,
stuff
and
then
yeah
all
sorts.
All
sorts
of
cool
stuff
so
might
be
a
little
bit
delayed,
but
it
will
be
available
until
then.
Thank
you
very
much
for
joining.
Take
care.