►
From YouTube: 2023 08 10 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
A
Today
we
have
myself
and
Mark
White
Bruno
is
taking
some
PTO,
so
he
won't
be
with
us
this
week
and
if
anyone
else
joins
up
while
we're
discussing
things
we'll
whip
them
in
today
for
the
agenda
notes
about
just
the
one
blog
post
we
had
published
last
week
was
our
July
newsletter,
the
weekly
2.418
release
and
upcoming
2.414.1
release
notes
on
the
Google
summer
of
code
and
where
things
are
going,
there
updates
and
progress
made
there
the
topic
of
potentially
moving
some
documentation
to
make
it
more
easily
accessible
in
terms
of
finding
it
and
housing
it.
A
A
couple
open,
pull
requests
of
Interest,
and
then
this
is
a
discussion
that
we've
been
having
now
for
some
time,
Mark's
proposed
the
proposal
for
how
we
go
about
supporting
Java,
1117
and
21
going
forward.
A
The
devops
world
tour
and
Mark
is
going
to
be
out
of
office
for
for
some
time
and
then
I'll
be
out
of
office
at
the
end
of
August,
so
we'll
discuss
those
once
we
get
there
and
yeah
so
Mark.
Just
to
make
sure
anything
else
to
add
to
the
agenda
or
does
that
cover
everything
for
us
today.
A
Great,
so
starting
us
off,
so
that
the
Jenkins
July
newsletter
was
published
on
August
2nd.
You
know
what
the
deal
is
at
this
point,
our
monthly
newsletter.
We
got
it
out
really
early
this
time
around,
which
is
great
new
success
and
yeah,
just
all
of
our
wins
from
July
and
all
the
updates
that
we
have
for
you
from
the
Sig
leaders.
A
Weekly
2.418
was
released
earlier
this
week.
There
were
some
issues
in
the
build,
but
we
got
it
got
straightened
out
and
released
no
problem,
so
that
is
available.
Lts
2.414.1,
the
new
Baseline
is
going
is
set
to
be
released
on
August
23rd.
The
release
candidate
was
is
available
as
of
yesterday
so
download
test
Etc,
the
change
login
upgrade
guide
have
been
created
and
a
pull
request
has
been
submitted
for
that.
Something
to
note
is
that
the
upgrade
guide
is
being
adjusted
still.
A
There
are
a
couple
of
issues
specifically
with
the
calendar
view
or
the
global
build
stats,
plugin
and
a
couple
other
items
that
are
still
in
the
process
of
being
worked
through.
So
there
are,
for
the
most
part,
it
is
ready
to
go
and
ready
to
be
reviewed,
but
the
upgrade
guide
may
see
some
additional
changes
before
it's
before.
It's
ready
to
merge.
B
A
A
Great
yeah
and
I
actually
just
submitted
an
update
for
it.
It's
essentially
explaining
that
for
the
global
build
stats
plugin
specifically
since
that
was
a
new
one
to
add
so
yep
Google's
Hummer
of
code
has
been
in
full
swing
for
some
time
now.
The
midterm
evaluations
have
passed,
all
four
participants
have
passed,
which
is
great,
and
so
we've
got
the
version
documentation
for
jenkins.io
AKA
building
jenkins.io,
with
alternative
tools
from
vandit
Vandy.
It's
going
to
demo
that
at
the
next
ux
fig
meeting,
which
is
August
16th.
B
A
A
Definitely
and
I
know
I'll,
be
there
so
yeah
we'll
have
we'll
have
representation
and
someone
to
ask
if
I
need
some
questions.
Speaking
of
questions,
these
are
some
that
have
come
up
lately
since
Vandy.
It's
got
the
demo
site
available
and
looks
really
good.
There
are
some
things
that
obviously
we
can
take
and
look
at
and
discuss,
such
as
what
versions
are
available
for
the
documentation.
A
Mark
stated,
the
Baseline
seemed
like
a
good
idea.
Meg
has
agreed
I
think
that's
a
really
good
idea
too.
The
weeklies
happen
so
often
and
so
consistently,
and
if
there's
not
necessarily
change
between
you
know
2.416
to
2.417.
Is
it
worth
having
both
of
those
versions
separated
and
available
like
that
or
is
it?
Does
it
make
more
sense
to
have
the
the
bigger
releases
be
that
that
point
of
change
and
that
point
of
okay?
A
Here's
where
we
can
definitively
say
we're
supporting
something
like
Java,
17
versus
Java
11.,
so
there's
yeah,
I'm
sure
there's
more
Nuance
to
it
than
something
like
that.
But
there
are
other
questions
that
have
come
up,
though,
is
there
a
way
to
limit
the
number
of
releases
displayed?
A
Is
there
a
way
to
to
know
that
the
the
information
has
changed
on
the
page
other
than
just
looking
at
the
version
number
or
seeing
you
know
what
are
the
differences
between
the
documentation
and
that
might
just
require
knowing
what
to
look
for
at
that
point,
if
there's
not
a
dead
giveaway,
but
just
great
questions
to
have
and
good
things
to
think
about,
as
as
we're
moving
towards
the
finish
line
here
for
Google
summer
code,
so
great
discussions
being
had,
though
the
doctor
could
pose
for
tutorials
that
ashitosh
has
been
working
on
still
has
some
more
work
to
be
done,
but
looking
good,
the
gitlab
plug-in
modernization
from
harsh
there's
still
some
things
that
need
to
be
tested
and
determined
for
that
Mark.
A
Do
you
have
any
other
notes
on
that?
One
or
any
other
insights
on
that
nope,
okay
and
the
plug-in
Health
score
that
jagruti
has
been
working
on
is
still
is
still
moving
forward,
so
great
work
there
thanks
to
everyone
for
their
constant
work.
A
Like
we
mentioned,
the
midterm
evaluations
have
been
completed
as
of
July
the
final
evaluations.
That
period
opens
on
August
28th
and
closes
September
4th
so
that
time
period
at
the
end
of
the
month
there
and
the
final
presentation
is
for
Google
summer
of
code
will
happen
in
mid-september.
There
will
be
a
webinar
or
some
sort
of
presentation
there
that'll
be
recorded
I'll
be
available
more
details.
A
Come
on
that,
though,
the
next
item
on
the
agenda
is
something
that
I
actually
just
started
discussion
discussion
with
Mark
about.
A
A
These
are
things
that
are
inherently
part
of
the
installation
guides.
So,
for
instance,
if
we
go
to
anything
like
Linux,
the
prerequisites
have
these
links
available,
but
beyond
that,
the
only
other
way
to
find
them
is
to
search
for
them.
A
So
what
I
had
proposed
is
potentially
moving
the
the
contain
the
support
policies
and
Java
requirements
into
the
system
administration
section
where
we
can
create
a
separate
section
for
these
support
policies
and
in
my
head
I
thought
they
could
work,
something
like
the
reverse
proxy
configuration
where
it
does
have
a
collapsible
menu
for
the
various
options
there.
A
We
would
have
similar
setup
where
it's
support
policies
and
then
it
would
drop
down
to
reveal
the
links,
the
windows,
the
server
containers,
Etc
and
then
having
a
separate
section
for
Java
requirements
or
Java,
just
upgrading
Java,
but
the
other
discussion.
There
is
well
we're
looking
to
have
an
upgrading
Jenkins
section.
Wouldn't
the
Java
upgrade
fit
really
well
there,
and
so
that's
another.
A
That
would
be
a
separate
section
from
the
system
administration
that
we
have
set
up,
though
I
want
to
say
it
started,
working
on
that
pre
a
little
while
ago
and
just
needs
some
more
work
there
to
get
that
to
a
point
where
we
can
publish
that,
but
outside
of
that,
it's
something
that
would
be
relatively
easy
and
I,
wouldn't
necessarily
change
anything
about
where
everything
is
located.
A
Currently,
it
would
just
give
them
a
secondary
home
so
that
it's
not
neces
like
people,
don't
necessarily
go
to
the
installation
guides
after
installing
they
may
not
find
need
for
it
or
have
use
for
the
installation
guides,
post,
installation
and
setup.
So
just
making
it
easier
to
find
would
be
a
win
that
we
could
get
really
pretty
easily.
A
This
is
an
ongoing
discussion.
I'm
not
trying
to
do
this
immediately,
just
something
that
I
have
been
thinking
about
as
I'm
working
on
stuff,
like
change,
logs
and
other
documentation
that
from
an
outside
user.
It
could
be
something
that
people
find
really
useful.
So
by
all
means
any
other
ideas.
Comments.
Insights
aside,
like
please
feel
free
to
share
them
here,
post
them
on
the
docs
getter
Channel.
There's
plenty
of
ways
to
communicate
so
feel
free.
A
And
then
for
the
open
port
pull
requests
of
Interest,
so
we
very
recently
had
one
that
Bruno
had
opened
up
basically
using
update
CLI
to
update
tool
versions
in
documentation
throughout
jenkins.io.
This
has
been
working
incredibly
well
and
putting
in
a
lot
of
work
as
it
stands.
There
have
been
tons
of
pull
requests
coming
in
to
update
the
tooling
the
tool
versions.
A
So,
just
like
this
one
here,
there's
still
some
there's,
there
can
be
issues
that
need
to
be
addressed
or
instances
within
the
pull
request
where
something
might
need
to
be
adjusted
or
fine-tuned
a
little
bit.
But
just
the
mere
fact
that
we're
getting
these
updates
and
these
pull
requests
created
automatically
is
a
huge
win
and
just.
B
A
And-
and
this
is
using
GitHub
actions,
which
is
something
really
nice
and
new,
so
that's
always
fun
to
incorporate
but
yeah.
This
is
something
that
Bruno
created
specifically
for
this.
It's
working
like
gangbusters,
so
yeah.
It's
super
super
thanks
to
him
for
all
his
work
on
that
and
then
the
other
pull
requests
that
open,
pull
request
that
we
have
is
the
administering
Jenkins
and
kubernetes
pull
request.
A
I
just
need
some
review
from
people
with
kubernetes
expertise,
but
that
we'll
get
we'll
get
that
determined
and
get
that
result
reviewed
and
published
when
we
have
that
next
on
the
agenda
is
the
proposal
that
Mark's
created
for
job
11,
17
and
21
support
and
what
our
next
steps
are
and
I'll
bring
up
the
proposal,
but
Mark
I
know
you
wanted
to
speak
to
this
and
discuss
some
points
on
this
yeah.
B
So
there's
just
one
item
here:
it
is
that
the
new
the
second
proposal
in
the
Java
11
section,
the
first
says
October
31
2024-
is
end
of
life
for
Java,
11
and
Jenkins
that
had
already
gone
out
to
to
the
board
and
to
the
officers.
The
third
proposal
there
end
of
life
admin
monitor
had
already
gone
out
to
the
board
in
the
officers
and
been
discussed.
Originally
the
middle
one
is
is
new,
and
it's
saying:
when
do
we?
B
When
do
we
declare
that
Jenkins
will
no
longer
support
Java
11
at
all,
and
and
for
me
my
proposal
was:
let's
make
it
the
as
close
to
the
Java
11
end
of
life
as
we
can
without
going
beyond
the
Java
11
end
of
life,
and
so
that
means
August,
7,
2024,
LTS
release
is,
would
be
the
last
Jenkins
version
to
support
Java
11..
So
roughly
a
year
from
now.
A
B
Or
well,
yeah
and
people
can
transition
to
17
now
right,
so
they
they
we're
we're
giving.
We
will
start
warning
them
in
OCT
in
a
weekly
in
October
and
then
in
the
LTS
in
December
that
Java
11
is
going
away
and
Java
11
will
then
go
away
with.
It
will
no
longer
be
supported
in
the
September
September
4
LTS
release,
so
the
forgive
the
numbers
they're
they're
declared
approximately,
because
we
can't
predict
what
number
will
be
selected
as
the
LTS
Baseline.
A
A
The
idea
is
to
line
up
with
the
end
of
life
and
make
sure
that
we're
not
going
over,
like
you
said
so,
makes
total
sense,
yeah,
cool
and
yeah,
and
the
I
mean
the
idea
is
just
that
we're
we
have
a
plan
laid
out
for
how
we're
going
to
support
Java
going
forward
for
Jenkins
overall,
but
whatever
the
version
might
be
at.
B
A
A
A
Some
of
them
have
a
couple
days
before
it,
such
as
the
September
and
October
events,
but
others
such
as
Chicago
and
Singapore,
are
really
going
to
have
one
day
dedicated
to
it.
The
idea
is
that
it
will
be
more
mobile,
more
accessible
for
more
people,
as
opposed
to
having
it
hunkered
down
in
one
location
for
a
few
days.
This
gives
folks
the
ability
or
gives
folks
that
might
not
have
the
ability
to
travel
the
ability
to
actually
get
to
devops
world
for
for
Advantage
and
in
person
has
posted
virtually
so
yeah.
A
So
the
the
goal
is
the
same.
The
idea
is
the
same
everything's
the
same:
it's
just
the
execution's
a
little
different
this
year
and
Mark's
actually
going
to
be
speaking
at
the
New
York,
Chicago
and
Santa
Clara
dates,
so
that's
very,
very
exciting
and
then
Olivia
will
be
speaking
at
the
Singapore
date
and
Tim
Jacob
will
be
speaking
at
the
London
date
and
I
got
that
right
this
time,
because
I
got
it
wrong
last
week,
so
yeah
just
a
great
chance
to
learn
more
get
in.
A
You
know,
acclimated
to
the
devops
world
and
a
chance
to
just
connect
and
meet
some
folks
that
may
not
have
been
able
to
Prior.
This
yeah
is
a
great
networking
event.
It's
a
great
event,
just
in
general
to
come
out
and
see
what
devops
has
to
offer.
So
registration
is
open
right
now.
A
A
On
the
agenda,
so
a
couple
of
housekeeping
notes,
so
Mark's
going
to
be
out
of
office
next
week,
so
the
I'm
taking
it
the
August
18th
meeting,
has
just
been
canceled
at
this
point.
Mark.
B
I
think
I
already
canceled
it
so
yeah.
If
you
want
it
back,
I'll
have
to
oh,
no
I
did
not
cancel
it.
I,
take
it
back,
I'm,
wrong,
I
I'm,
definitely
canceling
the
August
18
meeting
the
one
that
is
Asia
office
hours,
but
the
this
meeting
can
certainly
continue
so
office.
8
error,
eight
August,
18
office,
Asia
office
hours
is
canceled.
This
meeting
August
17
no
problem.
If
it
goes
ahead,
that's
up
to
you.
A
Yeah
and
it'll
be
happening
no
problem
there
yeah
your
U.S
doc's
office
hour
is
going
to
be
happening
as
normal,
so
no
worries
there.
Okay
and
then
this
is
actually
something
that
I
came
up
the
other
day,
but
I'll
be
out
of
office
on
August
31st.
A
A
A
In
that
case,
I'll
we'll
go
ahead
and
wrap
up
for
the
day,
we'll
give
some
time
back
to
everyone.
Thank
you.
So
much
for,
as
always,
for
joining
recording
will
be
available.
24
to
48
hours
and
yeah.
Take
care
have
a
great
rest
of
your
day
enjoy
your
week
thanks.