►
From YouTube: 2023 05 26 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.
This
is
the
26th
of
May
2023
topics
for
today,
the
2.401.1
changelog
and
upgrade
guide,
internationalization
and
localization
a
new
pull
request
and
some
opportunities
to
review
there.
If
Chris
joins
us,
we
can
talk
about
Google
summer
of
code
and
we'll
talk
about
end-of-life
notifications
in
Jenkins
core.
Any
other
topics
you
want
to
put
on
the
list.
Meg
looks
good
to
me
all
right.
A
A
Is
one
of
those
that
these
things
are
phrased,
a
very
specific
Way,
Daniel
Beck
has
guided
us
on
how
to
do
those
and
so
comments
are
welcomed
and
happily
encouraged,
okay.
B
A
So
Bruno
will
also
review
it
and
I
suspect
Alex
Brandis
will
review
it,
so
we've
got
good
review
there.
Next
topic,
then,
was
on
internationalization
and
localization.
So
this
one
we've
got
a
pull
request
from
from
Jeffrey
Chen
a
new
contributor.
The
pull
request
is
bringing
back
an
old
poll
request
that
had
been
started
and
then
stalled.
A
So
we
had
smarted
a
stalled
and
Jeffrey
said:
hey
I'd
like
to
work
on
it
so
started
work
on
it
and
Jeffrey's.
Work
is
now
visible
here
and
we've
been
going
through
a
series
of
improvements
to
try
to
get
it
ready
right
now,
it's
running
through
the
build.
What
I
had
done
was
Jeffrey
gave
some
initial
changes
that
looked
like
this,
so
here
you
see
the
top
level
page
notice
that
it's
still
marked
with
the
work
in
progress
flag.
A
He
added
a
whole
new
page,
or
rather
the
original
pull
request
did
and
then
the
top
level
page
still
showed
as
work
in
progress
with
a
link
to
the
new
page.
I
took
a
little
broader
approach
and
said:
hey:
let's
do
it
this
this
other
way,
and
so
what
I
did
was
put
the
content
that
he
had
created
in
the
top
level
page.
A
As
a
series
of
of
hey
do
this:
do
this
links
to
how-to
guides
and
then
placed
the
integration
to
crowd
in
right
next
to
it
and
linked
inside,
because
crowdin
is
this
great
tool
that
we
use
for
to
support
our
translators
right
and
I,
asked
Jeffrey:
hey!
Are
you
okay?
If
I
apply
my
changes
onto
your
pull
request,
Jeffrey's
answer
back
seems
to
be
yes
and
so
I've
gone
ahead
and
done
that
and
it's
now
building
I
just
pushed
it
just
a
few
minutes
ago.
A
So
so
we'll
be
able
to
see
that-
and
this
is
another
one-
Meg
I'd
love
to
have
a
review,
particularly
because
we
want
to
we'd
like
to
have
this
done
well
enough
that
people
can
understand
it.
There
are
two
or
three
cases
where
translators
can
do
the
easy
thing
if
they're
plug,
if
the
plug-in
they're
working
on
is
supported
by
crowd,
and
they
just
have
to
do
this-
translate
messages
in
crowd
in
right
and
it
talks
them
how
to
do
that.
It's
it's
a
really
nice
interface.
B
B
A
A
Thank
you
all
right
on
Google
summer
of
code,
since
Chris
isn't
here
we'll
move
this
later
next
topic
was
end
of
life
notifications
in
Jenkins
course,
so
this
one
is
a
process
that
I'd
started
discussing
in
platform
Sig
and
in
doc's
office
hours.
Oops
two
warn
users
when
their
operating
system
is
no
longer
supported,
because
we
don't
support
operating
systems
that
the
vendor
doesn't
support,
and
so
this
now
gives
us
a
user
interface
inside
Jenkins
that
says
you're
running
on
an
operating
system.
We
won't
be
supporting
in
the
not
too
distant
future.
B
A
B
A
And
so
so,
the
the
message
here
is
takes
them
through
it.
Now
we've
got
a
number
of
activities
that
have
to
be
done
and
I've
put
some
notes
in
here
on
those
we'll
need
a
blog
post
and
just
to
go
with
the
blog
post,
we'll
want
to
community.jenkins.io
post
that
tells
people
so
that
people
can
have
conversations
about
the
blog
post.
A
B
A
A
B
B
B
A
and
containers,
so
they
are
explicitly
listed.
Then
there
are
others
where
we
say
we'll
we're
willing
to
consider
patches,
but
we
don't
test
them.
We.
A
Test
and
we
may
drop
support
without
telling
anybody
32-bit,
for
instance,
risk
five
other
exotic
architectures,
like
mips
uh-huh
and
then
any
version
not
supported
by
the
vendor.
We
don't
support.
A
Was
one
that
was
vetted
originally
I?
Think
olegnanashev
created
this
Linux
support
policy
page
and
made
very
was
very
careful
to
be
sure
that
people
understand
this
is
not
any
statement
of
the
existence
of
a
support
organization.
It's
rather
that
here
are
the
things
we
test
and
hear
the
things
we
don't
test.
Yeah.
B
A
A
Yes,
absolutely
well,
and
there
are
companies
out
there
who
say
the
only
thing
you
can
use
is
Centos
7.
and,
and
they
largely
don't
care
that
it's
reaching
end
of
life.
It's
they've
chosen
it
all
those
years
ago
and
they
they
expect
you
to
keep
using
it,
and
the
answer
is
you're
free
to
keep
using
it.
We
just
won't
support
it
right.