►
From YouTube: 2023 04 28 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
Well,
welcome
everyone:
it's
the
28th
of
April
2023.
This
is
Asia
documentation,
office
hours,
thanks
for
being
here,
topics
on
my
list,
Google
summer
of
code,
a
proposal
to
change
the
rating
system,
upcoming
LTS
documentation,
transition
from
java
11
to
Java,
17
and
end-of-life
notifications
and
early
end
of
life
for
Centos
7..
We
may
not
get
to
those
last
two
and
I'm
not
sure
it's
crucial
that
we
do
any
other
topics
you
want
to
put
on
the
list.
B
A
Nope
good
for
me,
okay,
so
Chris
we
have
have
we
officially
submitted
or
is.
Is
that
coming
still.
C
It's
submitted
I
think
the
application
has
been
closed.
So
it's
like.
We
have
submitted
rankings
OK.
A
A
Excellent,
thank
you
Chris
thanks
very
much,
congratulations
to
you
and
the
other
organization
admins.
So
next,
next
Milestone
is
May
the
4th
when
Google
announces
the
projects
right,
yep,
excellent,
congratulations
thanks
very
much
any
any
questions
make
from
you
or
Chris
any
other
comments
on
Google
summer
of
code.
B
I
take
it,
we
had
very
good
projects
this
year.
We.
B
B
A
A
So
what
you
see
here
is
the
Jenkins
changelog
and
there
are
three
icons
across
the
top
of
each
change:
log
entry,
a
thundercloud
that
has
hover
text
I,
had
to
roll
back
a
cloud,
I
experienced
notable
issues
and
the
Sunshine
that
says
no
major
issues
with
this
release
and
what
the
problem
we
get.
Is
we
get
silly
things
like
this,
where
someone
pressed
the
rollback
or
the
notable
issues,
and
then,
when
the
dialogue
appeared
that
says
Please
provide
the
issue
number
they
put
in
the
number
one.
A
Now.
One
is
not
a
helpful
thing,
because
this
issue
is
actually
not
relevant
to
that
release,
and
we
know
it's
not
right,
because
that
issue
was
resolved
in
2007.,
so
so
and
when
people
put
other
issue,
numbers
thinking,
they're
being
Charming
or
cute
or
whatever
it,
it
reduces
the
value
of
the
thing.
However,
all
of
our
discussions
on
what
can
we
do
to
improve
the
quality
of
the
data
that
people
submit
there
have
ended
in
a
in
a
g
there's
not
much.
A
We
can
do
because
anything
we
do
will
tend
to
reject
the
wrong
things,
all
sorts
of
challenges.
So
this
is
what
we
have
today.
What
Alex
is
proposing
is
we,
he
says,
hey
look.
This
is
a
problem
because
there's
really
no
classification
of
the
the
numbers
that
they
put
in
there's
no
way
we
can
connect
with
them
when
they
enter
something
it's
completely
anonymous
and
so
his
recommendation,
let's
take
out
the
neutral
and
the
negative
votes,
so
the
cloud
and
the
Thundercloud
and
just
put
up
a
banner
at
the
top.
A
C
A
So
so-
and
this
is
the
banner
that
he's
added
saying
hey
if
you
need
to
encounter
an
issue
or
if
you
encounter
an
issue,
please
use
the
community
forums
to
report
that
issue
or
report
the
bugs
on
jira.
Following
these
issue,
reporting
guidelines
and
the
issue
reporting
guidelines,
Alex
and
I
are
two
relatively
active
people
on
jira,
and
it
is
the
most
common
thing
that
happens
is
we
have
to
tell
people
you
have
not
given
us
enough
information
to
duplicate
your
bug.
Please
follow
the
instructions
and
the
the
most
common
response
is
completely
being
ignored.
B
A
A
When,
when
I
went
when
I
sent
email
about
three
or
four
days
ago,
saying
I
recommend
2.401
be
selected
as
the
LTS
base
as
the
next
LTS
Baseline.
It
was
because,
among
other
things,
I
had
looked
at
this
at
this
data
and
said
that
looks
like
that's:
okay,
I
I
specifically
look
at
this
data
and
was
very
concerned
because
of
that
number,
and
this
bug
report
and
and
correctly
so
that
bug
report
is
an
unhealthy
bug.
So
so.
A
Right
with
the
new
system,
this
would
be
gone
and
now
I
I
had
to
go.
I
had
to
watch
the
bug
tracker
anyway,
so
the
rating
system
is
certainly
not
enough
to
choose
an
LTS
Baseline
right.
I
looked
in
jira
I
I
considered
the
the
changes
that
had
been
made
in
various
versions.
So
there's
there's
much
more
to
choosing
an
LTS
Baseline
than
just
reading
the
rating
system.
Yeah.
Okay,.
B
C
A
Okay,
so
my
my
concern
was
that
that
I'm
I'm
one
who
uses
the
rating
system
and
so
I
absolutely
did
not
want
to
lose
it.
Tim
Jacob
our
release
officer,
said:
hey:
I'm
conf
he's
conflicted
with
it.
He
he
sees
them
as
helpful
to
get
a
pulse
of
the
community,
but
it
is
spammy
right
it.
It
tends
to
be
low
value
content
at
certain
times
and
you
can
see
it
if
you
look
at.
A
If
you
look
through
the
history
you'll
see,
let's
see
some,
for
instance,
here's
one
with
two
rollbacks
and
not
none
of
them
entered
a
bug
report
10
and
we
got
one
bug,
number
24
and
only
two
bug
numbers.
C
A
A
B
A
As
far
as
I
know,
because
at
least
Jenkins
core
doesn't
doesn't
have
GitHub
issues
enabled
so
if
they
were
filing,
it
would
be
some
place
that
I
don't
know
where
it
is.
Okay,.
B
C
B
At
one
time
it
was
kind
of
fun
they
want
to
know,
and
now
it's
getting
into
overload,
but
whether
there
was
something
like
I
don't
want
to
bother
with
filing
a
bug.
It's
a
bug.
It's
not
that
big
a
deal
to
me
or
whatever
they
don't
have
many
options
for
what
they
re.
If
they
don't
want
to
I
mean
it
also
strikes
me
that
if
you
have
no
details,
knowing
if
you
look
on
here
and
you
see,
there's
a
release
where
you've
had
you
know,
like
70
people
had
to
roll
back.
C
B
Name
and
my
favorite
Elementary
School,
you
know,
and
it's
and
I
just
say
no
I
don't
have
time
for
you.
You
know
rather
than
saying
I
had
to
roll
it
back
and
I'm
not
invested
enough
for.
A
B
A
B
C
C
C
B
That
I
see
that's
potentially
useful,
is
if
I'm
sitting
here
thinking
about
installing
it
and
there's
two
types
of
people,
there's
one
who's.
Oh
this
thing's
buggy
I
want
to
go
in
and
play
with
it
and
see
if
I
can
figure
it
out,
because
I'm
That
Kind
of
a
geek,
the
other,
is
G
and
awful
large
percentage
of
people
who
tried
to
do
this
have
had
problems.
Maybe
I'll
wait
a
few
days
and
see
what
happens
and.
C
C
A
B
B
A
B
B
True
I
mean
another
thing:
what
you
could
simplify
is
I'm,
happy
I'm,
not
happy
and
we're
not
happy
it
could
be.
You
could
say
you
could
give
them
a
list
of
issues.
Not
one
of
these
are
issues
you
want
to
just
tell
us
what
happened.
You
know,
which
might
not
be
your
full
bug
report,
but
it
might
be
a
hint.
B
C
C
And
on
top
of
that,
I
just
want
to
add
like
well.
Unless
we
have
a
feature
that
would
give
us
a
drop
down
list
of
all
the
issues
patched
per
like
per
release
it
it's
the
feature
would
not
be
as
helpful,
so
we
maybe
we
could
like
request
a
feature
for
that.
B
A
We
did
the
last
five
bug
reports
or
something
like
that.
Last
five,
last
seven
bug
reports
or
or
the
last
the
titles
of
the
last
seven
of
the
most
recent
seven
bug
reports,
something
like
that
as
just
a
wild
guess
and
titles
of
any
bug.
Well,
no,
that
was
probably
begging
well
and
titles
of
bug.
Reports
already
mentioned.
B
And
then
another,
if
you
know
I,
don't
know
that
I'm
voting
I'm
trying
to
take
the
opposite
side,
because
it
doesn't
look
nice
and
clean
along
with
that
could
be
underneath.
That
could
be
a
link
if
you'd
like
to
file
a
bug,
go
here,
your
link
to
jira
and
follow
these
guidelines
that
thing
that
you
had
but
put
it.
B
So
they
don't
have
to
go
looking
for
it,
because
you
know
again
when
I
don't
know
where
to
go,
how
much
am
I
going
to
go
snooping
around
to
try
to
find
stuff
and
then,
after
that,
just
leave
a
blank
place
and
make
it
you
know,
give
them
140
characters,
something
you
know,
or
would
you
like
to
tell
us
what
your
problem
was
briefly
here
when
my
assumption
would
be
in
a
large
number
of
cases,
you
would
just
ignore
that,
but
they
would
feel
like
they've
been
able
to
say
something.
A
A
A
C
A
Well
then
it
would
then
it
would
be
no
worse
than
the
fact
that
today
we
have
relatively
few
people
who
read
I'm
going
to
paste
the
link
into
this.
One
with
this
is
something
that
relatively
few
of
us
read:
I'll
open
it
here.
You
have
to
both
promise
that
you
won't
be
offended
if
there
are
words
in
it
that
really
shouldn't.
A
Very
good,
well
so
here's
this
sheet,
this
Google
sheet
is
the
content
of
feedback
given
by
readers
who
are
reading
pages
on
www.jenkins.io
when,
when
they
click,
when
they
click,
did
this
page
help
you
or
some
such
thing?
Let
me
find
a
page
and
I'll
show
you
what
it's
like.
Was
this
page
helpful
when
they
click
this,
then
please
submit
your
feedback
through
this
quick
form.
A
C
B
I
mean
it
could
be
worded,
you
know
to
say
you
know
to
be
most
useful.
We
need
to
know
you
know
we
need
an
issue
just
just
this.
You
sound
like
your
stuff
or
or
go
here
and
file
one
and
say
you
can
also
just
leave
a
you
know
a
brief
report
like
we
don't
guarantee
we'd
look
at
it,
but
the
one
thing
might
be.
If
you
had
one
that
had
you
know,
50
thunderclouds
filed
nobody
had
filed
a
bug
report,
a
juror
ticket
and
you're
just
curious.
A
A
B
B
You
know
and
you're
like
gee,
flammable
pipelines.
So
I
don't
know,
and
then
you
know
there's
a
question
of
how
much
like
I
think
this
thing
that
suggested
would
be
kind
of
cool.
But
is
it
useful
enough
to
be
worth
the
effort
and.
A
And
whether
useful
or
not
right
now,
the
the
the
most
common
thing
is
all
the
ideas
in
the
world
need
to
be
supported
by
someone
actually
doing
the
implementation.
We
don't
have
anyone
who's
interested
in
doing
that
implementation
right.
So
if
someone
decides
they'd
like
to
do
the
implementation,
that's
a
different
thing,
then
it's
okay.
How
would
we
do
it
and
here's
the
benefit.
B
A
Is
it
this?
This
is
probably
not
well
suited
to
a
good
first
issue,
because
it
requires
access
to
the
ratings
database,
which
is
a
privileged
operation
and
and
they
could
do
it,
maybe
with
a
prototype
copy
of
the
database
But.
Ultimately,
it's
there
are
privileged
operations
involved,
and
it's
not
really
well
well
equipped
for
development
experience.
B
A
A
Next
topic,
then,
we've
got
the
2.387.3
change
log
and
upgrade
the
release
is
next
week.
Thanks.
A
C
A
A
Extreme
and
ASCII
null
handling
has
changed,
and
with
this
change
they
need
to
be
sure
they
upgrade
their
the
junit
plug-in
to
the
latest
version.
A
And
the
the
problem
is,
the
old
version
of
the
plug-in
was
writing
an
ASCII
zero
and
that's
that
that's
per
the
XML
1.1
specification.
That's
illegal,
it's
not
allowed.
So
this
is
now
better
compliant
with
the
specification,
but
the
problem
is
we
have
date.
We
may
have
data
on
customer
on
systems
that
can't
be
read.
If
you
don't
have
the
new
version
of
the
of
the
the
junit
plugin.
Okay.
A
B
C
A
A
We've
discussed
that
Java
17
is
now
fully
supported
and
Java
Java
11
will
no
longer
will
not
be
included
in
the
upcoming
release
of
Debian.
It
won't
be
available,
and
so
we
felt
like,
rather
than
spending
energy,
to
describe
oh
for
Debian
12.
You
have
to
use
Java
17.
Let's
use
this
as
our
excuse
to
document
describe
everything
with
Java
17
and
let
people
use
Java
11
if
they
wish.
But
Java
17
will
be
the
thing
we're
describing.
A
C
A
Nope,
okay,
then
next
piece
was
the
concept
of
end
of
life.
Notifications
in
Jenkins,
core
I,
believe
Chris.
You
and
I
discussed
this
last
time
and
I'm
not
sure,
there's
a
significant
change
that
needs
to
be
needs
to
be
described
further.
I
actually
about
15
minutes
ago
started
the
implementation,
so
I've
discussed
it
with
different
levels
of
people
Meg
for
your
info.
The
idea
is
that
Ubuntu
18
will
be
end
of
life.
May
31st
2023.
A
Jenkins
only
supports
operating
systems
that
are
supported
by
the
Upstream
vendor.
Ubuntu
18
will
be
unsupported,
June
1st,
but
we
don't
have
a
way
inside
the
Jenkins
UI
to
tell
the
user
hey
you're
running
on
an
operating
system.
We
don't
support
uh-huh
and
so
the
the
idea
here
was:
let's
find
a
way
to
tell
that
user
you're
running
on
an
operating
system.
A
We
don't
support
with
the
the
thought
that
we
may
be
able
to
use
this
same
technique
to
tell
people
you're
running
a
Docker
container
that
we
no
longer
maintain
oh
yeah
or
you're
running
a
something
else
that
is
no
longer
receiving
updates
and
and
so
that
they
know.
Oh
I
need
to
make
a
change
based
on
this
alert.
That
tells
me
something
right.
A
Sure,
and
then
at
least
they've
been
warned,
they
have
to
take
their
chances
and,
and
the
concept
is
that
there
are
some
things
that
are
a
little
different
about
this.
In
that
there
is
a
when,
should
we
start
showing
them
the
warning?
What
dates
do
we
start,
showing
them
the
warning
and
during
the
warning
period,
what
which,
during
the
the
pre
pre
period,
we
give
one
message,
then
the
the
final
date
happens.
The
thing
is
now
end
of
life.
We
give
them
a
different
message
and
bring
the
admin
monitor
up
again.
A
A
B
A
Yes
and
that
this
is
what
started
the
whole
idea
right,
because
the
fact
that
I
dislike
Centos
so
strongly
motivated
me
to
say
how
do
we
get
a
message
to
users
that
tells
them
we're
ending
support
for
Centos
7,
and
a
piece
of
this
is
my
my
dream:
is
that
we'll
declare
end
of
life
for
Centos
7
well
before
the
official
end
of
life?
C
A
Great
any
any
other
topics
for
today's
session:
I'm
good
I'm
good
too.
All
right,
thanks
to
both
of
you
recording,
will
be
available
whenever
I
get
around
to
posting.
The
recording
terrific
thank.