►
From YouTube: 2023 06 08 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
it's
documentation.
Office
hours
is
the
8th
of
June
2023.
Topics
on
the
agenda
for
today
include
2.401.2
20401.1,
a
pull
request
for
from
a
new
contributor
end
of
life,
notifications,
container,
end
of
life
and
a
couple
of
topics
from
our
last
session.
Anything
else
you
want
to
add
Bruno.
B
A
Thank
you,
Mark,
okay,
so
Chris
Stern
is
acting
as
release
lead
for
2.401.2
and
we'll
need
to
create
the
changelog
Kevin
Martens
is
planning
to
be
back
next
Monday,
so
we
he
may
be
able
available
to
do
the
change
log
and
upgrade
guide
hoping
and,
if
not,
we'll,
take
care
of
it
in
the
docs
team.
Next
topic
is
related
to
that,
but
it's
sort
of
an
embarrassment
in
the
live
stream.
There
are
at
least
at
least
two.
B
But
the
two
of
you
really
handled
that
beautifully
during
the
line.
B
A
Mistake
yep
and
that's
okay,
so
we've
got
an
we've,
also
got
a
new
pull
request
from
Jeffrey
Chan,
with
a
conversion
of
something
from
Wiki
Meg
McRoberts
agreed
in
last
doc's
office
hours
ages
that
she
was
willing
to
review
it.
I,
don't
think
she's
had
time
yet,
but
I'll
have
we'll
have
that
discussion
during
Asia
office
hours
in
about
12
hours.
B
Yes,
I
already
done
my
review,
but
it's
very
low
level
review.
B
You
know
it's
just
a
few
things
changing
commas
or
world,
something
like
that,
but
we
need
somebody
who
has
a
better
picture
from
far
away
for
thou,
further
away
to
change
things,
because
of
course
some
things
have
changed
since
the
wiki
was
created
and
some
things
are
already
in
other
parts
of
the
documentation.
So
yes,
please
make.
Whenever
you
have
time,
your
review
is
welcome.
B
Yes,
but
I
I
can
see
that
Jeffrey
is
still
motivated.
You
know
he's
doing
merge
from
Master
into
his
Branch
twice
a
day,
so
he
wants
right
that
to
be
covered.
That's
cool!
Thank
you.
Jeffrey
foreign.
A
Good
all
right
end
of
life
notifications
in
Jenkins
core
have
are
now
live,
they
became
available
in
2.407
and
a
fix
is
included
in
2.409
or
Fedora
38.
B
No,
it
was
just
a
stupid
joke,
but
10
weeks
from
now
mean
that
we'll
be
in
August
10
weeks
from
now
correct.
It
goes
way
too
fast.
My
brain
is
still
in
April
wow.
A
I
wholehearted
agreement.
Absolutely
so
so
August
is
the
plan
and
we
look
forward
to
it
now.
We've
got
an
additional
idea
that
I
don't
know
when
it
will
happen,
because
it's
lower
priority
for
me
than
other
things.
It
is
that
our
container
controllers
should
be
that's,
that's,
let's
call
it
this
and
then
we've
got
a
further
idea,
which
is
Agent
control
or
container
agents.
A
So
what
we've
seen
is
well
Bruno
you
had
done.
You
had
done
some
work
on
the
con,
the
container
agents
build
recently
and
it's
possible
for
users
to
be
referencing,
a
very
old
unmaintained
container
agent
image,
and
they
they
get
no
warning
their
administrators.
Get
no
warning,
there's
no
hint
that
you've
chosen
a
dangerous,
outdated
controller,
container
image
or
control
agent
image,
and
so
the
idea
here
is
if
we
can
find
a
way
to
warn
people
that
they're
running
old
agents,
it'd
be
good.
A
And
I
think
that's
a
piece
where
well
platform
labeler
hints
that
it
should
be
feasible
without
touching
the
agent
in
the
container
image.
Since
platform
labeler
looks
at
the
agent,
for
instance,
it
looks
at
its
operating
system
and
says
this
operating
system
is
such
and
such
a
version.
So
we
could
do
something
like
that
and
say
we
could
conceivably
extend
the
end
of
life,
notifications
here
and
say,
sweep
through
all
the
all
the
play,
all
the
agents
and
if
any
of
the
agents
have
a
in
fact,
maybe
that's
an
enhancement
for
the
platform
labelers.
B
That
would
be
interesting,
but
the
thing
is:
will
everybody
have
a
version
of
platform
labor
in
their
Jenkins
instant,
no.
B
Interesting,
nonetheless,
if
platform
laborer
could
reuse
what
the
kind
of
framework
you
put
for
in
the
Jenkins
core,
that
would
be
interesting
and
it
already
does.
I
I
did
not
understand.
I
had
to
look
at
the
platform
level
code,
but
I
did
not
fully
understand
how
the
magic
was
happening,
and
but
it
doesn't
really
for
sure.
You
know
the
other
day,
I
tried
platform
labeler
with
Jenkins
running
on
my
Android
phone
and
it
managed
to
find
it
was
Android
and
it
was
working.
B
So
why
not
I
guess
this
is
a
very
good
foundation
for
the
rest
of
the
work.
A
Yeah
and-
and
that's
all
of
it,
that's
all
that
the
end
of
life
notification
does
right
is
it
reads
and
acts
on
a
file
in
the
file
system?
So
not
a
not
a
complicated
thing.
If
the
agent
operating
system
is
helping
us
with
that
now,
in
some
cases,
Arch
Linux
the
agent
operating
system
will
tell
us
what
what
operating
system
it
is
the
case
of
things
like
Alma
Linux
8.
The
operating
system
is
not
end
of
life,
but
we
can
tell
that
it
exists
as
an
operating
system.
B
Not
for
the
time
being,
thank
you
but
I
guess.
I'll
get
I
have
lots
of
questions
when
the
meeting
ends,
as
always.
Okay,.
A
All
right-
and
we
had
a
leftover
question:
should
we
document
tested
operating
systems
I
think
it's
a
good
idea.
Maybe
the
simplest
approach
is,
let's
create
a
in
fact.
Let's
just
do
it
now,
let's
create
a
ticket
that
that
describes
it
because
there's
no
reason
to
leave
it
in
our
notes.
Let's
just
put
it
right.
B
A
B
A
We
test
in
in
multiple
ways
so
and
and
you'd
have
to
read
the
repositories
to
see
which
tests
run
where
okay,
because
it's
a
good
question.
A
A
Which
one
is
it?
Is
it
this
one
19
minutes
worth
of
testing
here
we
go
if
you
scroll
to
the
bottom
of
this,
and
you
can
see
all
sorts
of
things
that
are
tested
here
where
they're
listed,
hey
we're
testing
this
and
this
and
this
and
this
we're
testing
Tomcat
9
and
we're
testing
Etc.
So
all
sorts
of
interesting
and
useful
data
is
hiding
in
this
about.
A
If
we
look
at
it,
if
I
look
at
it
from
the
the
pure
console
view,
what
we'll
see
is
we
look
for?
Let's
look
for
Rocky
here
you
go.
B
Yeah,
okay,
my
ID
beyond
that
was:
would
it
be
easy
or
not
to
maintain
by
a
real
human
or
could
we
automate.
A
B
Of
course,
because
I
think
that
would
be
a
pain
in
the
neck
to
try
to
maintain
that
by
hand,
because
it's
always
changing
it.
B
Very
good
point:
yeah
the
Matrix
we
I
say
Matrix,
because
maybe
we
are
testing
on
several
different
CPU
architectures
for
the
same
Linux
distro,
for
example,
for
the
same
operating
system.
So
maybe
we
should
have
a
matrix
some
somewhere
that
describe,
and
we
may
even
discover
things
that
we
don't
know
yet.
But
what
is
tested
on
what
system
where
it
is
a
VM?
Is
it
a
real
machine
or
I?
Don't
know,
but
that's
interesting
nonetheless.
Well.
A
And
so
as
another
example
of
places
where
we
do
testing,
we've
got
this
one
right
here.
Let's
go
to
this
thing
because
I
never
remember
where
it
is
the
release
checklist.
Oh
I,
know
where
it
is.
It's
right
here
we'll
look
at
it.
This
way
we'll
go
this
and
acceptance
test,
and
if
we
look
at
Debian
latest,
for
example,
so
here
is
a
set
of
tests
that
run
on
various
operating
systems,
to
test
packages
for
LTS
and
for
for
weekly
and
so
again,
that's
another
part
of
the
testing
that
happens.
Acceptance,
tests.
B
A
And
then
say:
hey
these
are
the
things
and
then,
of
course,
we've
got
the
weekly
or
the
CI
tests
of
the
of
Jenkins
core.
A
B
A
So
yes
yep,
so
it's
captured
and
I
think
we
can
use
that
as
a
good
starting
point.
If
someone
wanted
to
work
on
it
see
it
was
CI
more
core
there
we
go
and
let's
just
take
this
one
and
the
last
build
a
less
successful
build
because
that's
the
easy
way
to
see
it.