►
From YouTube: 2022 12 01 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
Welcome
this
is
Jenkins
documentation,
office
hours,
Europe
action
items
that
I've
got
on
the
agenda
for
today
action
items,
Jenkins
elections.
A
A
All
right,
so,
let's
talk
about
action
items
first,
then
archive
the
website
component
on
jira,
so
that
we
can
focus
on
GitHub
issues.
Alex
Brandis
has
submitted
a
not
a
a
submitted
I
think
it
was
a
ticket
submitted
to
the
help
desk
to
the
infra,
help
desk
so
and
I'll
get
that
archive
or
included
here.
He
put
it
in
and
I
made
a
mistake
of
clearing
his
suggestion.
B
A
Have
to
look
it
up
separately,
sorry
about
that
Okay,
so
the
other
Kevin
archived
the
docs
mailing
list,
so
that
one's
still
in
progress,
one
that
has
made
good
progress,
not
because
of
anything
I
did,
but
because
of
what
Basel
did
a
pull
request
documenting
the
web
application
server
support
policy,
and
it's
a
really
nice
piece
of
work
that
he's
done.
If
we
look
at
it,
what
you'll
see
is
on
the
installing
Jenkins
page?
It
now
talks
about
the
server
container
policy.
B
A
B
A
Done
and
it
describes
things
as
they
are
currently
now
in
addition
to
what
Basel
did
there
he's
also
implemented
tests
to
check
for
regressions
in
case
the
known
working
servlet
containers
were
to
somehow
stop
working.
Oh
so
he's
created
automated
tests
that
perform
checks
of
wild
thought,
wildfly
version,
26
and
Tomcat
version,
9.
A
A
Jenkins
elections
have
been
announced
and
the
transition
has
started.
Alex
and
Uli
attended
the
last
governance
board
meeting.
B
No
except
congratulations
for
being
elected.
Yes,.
A
B
Wrong
yeah,
that's
okay!
He
does
so
much.
Of
course,
when
you
think
of
something
done,
it
may
be
basil.
It
must
be
basil.
No
not
this
time.
Sorry
I
did
it.
It's
not
finished.
She
has
a
PR
has
been
created
and
I
have
a
few
things
to
to
change.
For
example
the
Highlight
section,
but
it's
almost
done
I
think
I'll
be
able
to
get
it
reviewed,
maybe
tomorrow,
and
so
my
goal
is
to
have
it
published
next
Mondays.
So
December
results.
B
Thank
you
and
thanks
a
lot
to
all
the
submitters
who
made
their
section,
and
you
made
two
I
think
so
congrats
in
that
too,.
A
Yeah
I
I,
like
the
I,
like
the
exercise
I,
was
able
to
reuse
content.
In
both
cases,
it
felt
really
great
anything
else
on
November
newsletter.
No
thank
you.
Okay
next
was
the
end
of
December
newsletter
and
what
I
had
suggested
to
Alyssa,
and
she
thought
it
was
an
okay
idea.
Checking
with
you
as
well
was
what,
if
we
made
the
December
newsletter,
a
look
back
at
12
months
rather
than
just
a
one
month
thing.
B
I
think
that's
great,
that's
a
very
good
idea
and
we
have
so
much
to
say
we'll
have
to
widely
choose
the
subjects,
but
you
know
I'm
not
a
long
time
user
long
time,
Jenkins
user
but
I've
seen
so
many
changes
during
that
it's
even
not
a
Euro,
because
I
have
seen
changes
from
April
I
think
but
from
April
to
now
the
changes
are
already
major.
B
You
know
going
to
GDK
11,
then
17,
even
some
part
19
and
the
UI
ux
has
changed
quite
a
lot
and
some
plugins
are
back
from
the
dead
and
yeah.
It's
amazing
all
what
has
changed
so
I
won't.
How
do
we
say
that
you
know
spoil
the
December
you
set
up?
We
have
lots
of
things
to
say.
A
Good
yeah,
well
and-
and
let's
see
okay,
so
I've
got
I've,
got
some
for
to
include
here
so
documentation,
site,
search
Improvement.
Oh
yes,
right
just
just
one
example,
and
it's
really
thanks
to
algolia
and
Gavin
Logan,
the
the
search
engine
works
much
better.
It.
A
A
And
yeah,
so
we've
got
more
topics,
let's
see
so
and
if,
if
any,
if
any
come
to
mind
by
all
means,
suggest
them
or
propose
them,
it
would
be
a
great
thing
for
Alyssa
or
you
and
Alyssa
or
others,
to
have
to
choose
which
things
they
want
to
include
in
the
news
that
are
based
on
highest
value.
Highest
priority
I,
see:
okay,
we'll
do.
A
A
Right
so
next
piece
was
lts2.375.1
has
been
released
and
now
one
of
the
the
oops
is
here
for
us
is
a
docs
Sig
was
we
had
to
revise
the
upgrade
guide
after
release
and
what
happened
was
I
missed
I
didn't
do
a
thorough
enough
review
of
The
Source
material.
We
had
Windstone
6.4
in
the
Baseline,
but
I
believe
then
we
did
a
back
port
of
Windstone
6.6,
oh
and
that
removed
some
additional
command
line.
Arguments.
B
A
Right,
that's
cool
right
and
if
you
read
the
upgrade
guide,
you'll
see
the
the
description
it
talks
about
hey
this
one.
This
one
was
these
two
were
taken
away
and
you
do
this
one.
Instead
or
these
were
taken
away,
they
previously
did
nothing
and
now
they
they
still
do
nothing,
but
they
do
nothing.
They
fail
because
you
can't
use
illegal
arguments.
A
B
Yeah
yeah,
of
course,
Mark
sorry
to
add
that
stupid
question.
But
how
do
we
enter
feedback?
For
you
know
a
new
LTS
version,
because
it's
nice
to
see
people
are
happy,
but
how
do
they
tell
us
that
they
are
happy
or
unhappy
with
the
reads
so.
A
They
click
this
link.
They
click
this
image,
it's
as
simple
as
that.
Well,
it
is
except
okay.
So
when
I
click
the
image,
it
says
thanks
right
now,
I'm
going
to
go
back
because
I
don't
want
to
disturb
the
measurements.
I
have
installed
375.1,
so
I
I,
happily
can
say
yes,
I've
been
pleased
with
it.
If
I
were
to
go
back,
though,
and
say,
oh
I
want
to
report
an
issue
that
I
found
on
346.1,
so
I
could
click
the
cloud
and
it
asks
for
an
issue
number
okay
and
for
instance,
you
you
see
here.
A
A
Is
the
scoring
the
rating
system
is,
is
a
sincerely
very
valuable
for
people
who
are
trying
to
choose
more
particularly
trying
to
choose
the
next
LTS
Baseline,
because
what
we
will
do
is
we'll
look
at
the
ratings
for
the
weekly
releases
and
if
the
ratings
are
particularly
bad.
Okay
380
is
one
that
hey.
B
Okay,
I
was
wondering
for
the
previous
month.
How
do
they
know
the
health
of
a
future
candidate
to
be
an
LTS
or
not
now
I
understand
thank.
A
A
But
this
one
doesn't
tell
me
if
it
was
fixed
in
oh,
oh,
this
one
is
a
complicated
one.
That's
why
okay,
but
we
could.
We
could
try.
Others
and
I
suspect,
we'll
see
where
it
will
tell
us
either.
Oh,
it
was
chosen
as
a
release
as
a
release,
candidate
or
nope.
It
was
not
selected
and
So
This
was
oh.
This
was
a
change
in
in
a
plug-in,
so
that's
another
challenge
is
sometimes
bug.
A
Right
good,
so
next
next
piece
then
I
wanted
to
take
a
few
minutes.
We
may
want
to
delay
this
one
a
week
until
Kevin's
available,
because
I'm
very
grateful
for
his
work
and
Alyssa's
work
and
everybody's
work
and
I
think
your
work
as
well.
Bruno
on
getting
the
Thanksgiving
blog
post
out
I
thought
it
was
a
good
idea.
I
think
it
really
was
a
good
idea,
but
it
was
very
rushed
and
it
meant
that
we
had
two
people
in
the
U.S
who
were
working
on
Thanksgiving
day
a
day.
A
A
A
Then
there
was
a
new
change
that,
with
the
release
of
2.375.1,
that
means
2.361.4.
The
preceding
end
LTS
is
now
second
to
La.
Is
is
penultimate
right,
it's
second
to
last,
and
that
means
it
becomes
a
recommended
version
for
choosing
your
your
Jenkins
Baseline
and
therefore
there
are
changes
in
the
documentation
to
do
that
and
changes
are
ongoing.
B
I
see
and
regarding
the
documentation,
it
has
to
be
made
by
the
human
being
the
modifications,
or
can
it
be
scripted
with
a
deadly
or
whatever,
or
does
it
even
make
sense
to
have
a
robot
change
that
in
the
documentation
now
do
we
have
absolutely
to
get
it
reviewed
by
a
human
being?
No.
A
Actually
a
robot,
a
robot
already
does
a
significant
portion
of
it
and,
let's,
let's
look
at
the
portion,
the
robot
does
because
I
think
what
the
robot
does
is
actually
really
really
a
great
idea
that
I
think
Daniel
Beck
started
this
idea.
But
let's,
let's
look
at
what
the
robot
does
so
choosing
choosing
a
Jenkins
Baseline.
A
So
what
we
see
here
is
currently
recommended
versions
and
what
it
suggests
is
2.346.3
and
2.361.4
make
good
codependencies
and
then
here
it
inserts
the
value
2.361.4
in
the
recommended
code
in
the
in
the
set
of
code.
Well,
the
way
it
computes
those
if
I
click
this
improve.
This
page
it'll
take
me
to
the
to
the
the
page
and
then
when
I
look
for
jenkins.version.
A
Yeah,
oh
there,
it
is
yes
exactly
placeholder
recent
LTS
Point
High
and
the
build
process
that
constructs
the
website
will
replace
that
placeholder
text
with
the
actual
value
extracted
from
the
Jenkins
update,
Setter,
okay,
perfect-
and
it's
it's
things
like
this
one
has
the
same:
Behavior
placeholder
latest
split.
Each
of
these
is
provided
by
this
tooling.
That
I
believe
Daniel
wrote
that
reads
the
Jenkins,
Update
Center
or
read
some
other
location
gets
these
numbers
and
provides
them
as
text
strings.
Oh.
B
A
It's
it's
just
as
just
as
the
changelogs
are
data
driven.
The
change
logs
are
data
driven
from
a
data
file
that
provides
the
definition
in
this
case.
These
numbers
are
data
driven,
but
they're,
taken
from
data,
that's
downloaded
from
an
extern
from
another
URL,
and
then
that
data
is
fed
into
the
process.
I
see
yeah,
so
nice,
nice
result.
That's
all
that
I
had
anything
else
from
you,
Bruno.