►
From YouTube: Jenkins Governance Meeting June 12, 2023
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
everyone:
this
is
the
Jenkins
governance
meeting,
it's
June,
the
12th
2023.
we've
got
a
number
of
topics,
including
news:
several
open
Action
items
and
jira
upgrade
and
budget
and
expenses
and
Community
activity
summary
that
I
assembled.
Are
there
any
other
topics
that
people
would
like
to
be
sure
we
add
to
the
agenda.
A
Okay,
then,
let's
go
over
the
topics.
We've
got
so
by
way
of
announcement.
Jenkins
2.401.2
release
candidate
will
be
available.
This
Wednesday
special
thanks
to
Chris
Stern
for
his
work
as
release
lead,
Debian
12
has
released
last
Saturday.
It's
a
nice
operating
system
upgrade
important
to
note
that
it
does
not
offer
Java
11.,
so
our
documentation
will
be
updated
to
guide
people
to
use
Java
17..
A
That
way,
we
don't
have
to
explain
that
on
Debian
12
Java
11
is
not
even
available
from
the
operating
system
provider,
and
the
last
topic
I
had
was
a
reminder
that
the
CDF
technical
oversight
committee
election
is
in
progress.
I've
been
nominated
from
the
Jenkins
project.
There
are
only
four
seats
on
the
committee
application
by
six
candidates.
I
would
love
to
have
your
vote
if
you've
received
an
invitation
to
vote
any
questions
on
any
of
the
news
items.
A
So
let's
take
a
look
here:
easycla
documentation
not
happened
yet
Alexander
I
believe
there
was
some
interaction
there
that
might
need
more
on
this.
Do
I,
remember
correctly
or
am
I
am
I.
Forget,
am
I
off
base.
B
A
A
Okay,
so
he
took
both
paths-
yeah,
very
good,
okay,
thank
you
all
right,
and
that
was
now
that
I
think
about
it.
I
remember
that
was
so
that
Chris
wants
to
join
the
Linux.
The
the
security
team
and
volume
is
interested
in
that,
if
I
understand
correctly.
B
A
A
A
Retire,
the
Jenkins,
the
Chinese
Jenkins
site
is
in
progress
in
that
it's
no
longer
on
the
header,
but
we've
got
more
to
do
in
terms
of
getting
the
the
sub
Pages
under
the
site
redirected
right
now.
For
instance,
the
install
instructions
are
two
years
out
of
date
and
we've
had
an
awful
lot
of
changes
in
installation
instructions
in
two
years.
It's
really
bad
we're
showing
Chinese
users,
Incorrect
and
flawed
install
documents.
So
this
is
one
on
Kevin's
shoulders,
Kevin,
we'll
trust
you'll.
Take
it
forward.
A
Then
I
had
the
item
to
Archive
the
governance
meeting.
Notes.
Sorry,
no
progress
retrospective
on
the
signing
certificate
renewal,
progress,
I've
opened
the
document,
but
not
started
that
again.
Sorry,
I
am
proud
to
say
the
next
one
I
have
completed
the
reimbursement
process
for
the
code.
Signing
certificate
is
done,
I
have
the
money.
The
process
worked
thanks
to
Oleg,
especially
because
it
took
a
number
of
steps
for
us
to
figure
out
how
to
get
that
money
out
of
the
account
through
the
Linux
Foundation
into
my
account,
and
we
have
one
other
reimbursement.
A
A
So
I
had
asked
the
question
Johnson
Nguyen
from
Linux
Foundation
asked
me
on
30th
of
May.
If
we
had
a
specific
timeline,
my
answer
was
not
really
so
long
as
we're
done
with
jira
8
well,
before
the
end
of
supportive
of
jira.
Eight
we're
fine
with
that.
Anyone
have
any
concerns
about
that.
Do
you
want?
Do
you
want
me
to
put
pressure
on
them
to
say?
No,
we
need
to
do
it
much
earlier
than
say.
August.
A
Okay,
great
all
right
next
topic,
then
was
budget
and
expenses
and
I'm
proud
to
say
that
vatic
felonia
has
been
reimbursed
now
the
rest
of
you
may
not
say
that's
a
very
big
deal,
the
52.99
reimbursement,
but
it's
taken
us
as
much
as
two
years
to
get
this
reimbursement
finally
closed.
He
confirmed
the
money
has
arrived
in
his
account.
A
Finally,
so
it's
a
reminder
that
when
we
have
expenses,
the
easiest
way
to
do
it
is
have
somebody
from
Linux
Foundation
use
their
card
to
pay
the
thing,
rather
than
any
of
us
using
our
own
funds
and
trying
to
get
reimbursed
it's
just
much
easier.
If
we
make
them
do
the
payment
they'll
figure
out
how
to
route
the
money,
then
any
questions
on
that
one.
A
And
the
topics
that
I've
got
I'm
open
to
any
of
these,
that
that
are
particularly
of
interest
to
those
of
you
who
are
in
the
meeting.
If
you,
if
you
want
to
say
hey,
let's
talk
about
this
one
first
or
that
one
I'm
happy
to
move
things
around.
A
Okay
with
no
change,
then
we've
got
an
active
project
with
jfrog
trying
to
reduce
the
bandwidth
that
we're
using
on
repo.jenkinsci.org
we're
proud
to
say
that
we
reduced
by
20
terabytes
a
month
in
April
compared
to
previous
months
and
that's
a
nice
reduction.
But
they
really
think
that
we
need
to
do
more
and
we're
we
tried.
A
We
did
a
test,
drive
Brown
out
a
reduced
functionality
test
by
shutting
off
the
J
git
copy
that
we
have,
and
it
was
disruptive
and
because
of
that,
we're
going
to
have
to
now
talk
to
jfrog
about
what
other
alternatives
are
there.
So
we'll
we'll
be
doing
that
work
with
the
infra
team
to
identify
ways
to
reduce
bandwidth
use,
the
most
flagrant
abuser
of
the
bandwidth
has
already
been
banned,
but
they're.
A
A
Okay
prototype.js,
so
this
one
is
a
special
thanks
to
Basel
Crow
and
to
Tim
Jacob
prototype
is
a
JavaScript
library
from
2010
last
released,
I
believe
in
2013,
or
maybe
2015
so
in
the
world
of
JavaScript.
It's
ancient
and
it
disrupts
the
use
of
JavaScript
in
other
ways
in
Jenkins
core.
So
the
progress
is
being
made
to
remove
it
completely
from
Jenkins
core
and
from
the
entire
plug-in
Suite.
A
It's
it's
references
to.
It
have
been
removed
from
Jenkins
core
already,
as
of
2.406
and
key
plugins,
have
received
pull
requests
and
there's
a
feature
flag
so
that
those
of
us
who
are
testing
and
interacting
after
2.406,
we
can
actually
disable
prototype
completely
to
see
how
it
behaves
so
Basel.
Is
there
anything
additional
you
wanted
to
share
on
this
one.
C
No
I
think
you
covered
it,
so
it'd
be
great
to
see
more
help
to
adapt
plugins,
because
that's
really
what
we're
blocked
on
in
order
to
complete
the
project.
A
Right
and
this
this
sheet
that
buzzle
has
been
maintaining
is
a
is
a
marvelous
piece
of
work
in
terms
of
seeing
where
can
I
help.
So
when,
when
volunteers
come
saying,
hey
I'd
like
to
help
the
Jenkins
project,
any
one
of
these
rows
is
a
good
way
to
say
you
here,
you
can
learn
some
JavaScript
and
help
the
Jenkins
project
in
a
substantial
Way.
By
applying
to
your
work
to
one
of
these
plugins,
the
red
lines
are,
are
very
much
wide
open
ready
to
have
somebody
help.
C
D
C
C
I
I,
don't
have
any
I,
don't
have
any
knowledge
of
whether
when
Tim
plans
to
take
that
pull
request
out
of
draft
state,
but
until
the
spreadsheet
is
more
green
I,
don't
think
we
could
do
it
anytime
soon,
mm-hmm.
A
Yeah,
that
was
that
was
my
assessment,
because
if
we,
if
we
dropped
prototype
today,
any
user
of
the
credentials
plug-in
and
that's
280
000
users
to
it
would
be
broken
right.
So
so
that's
the
today's,
not
the
time
and
I
think
the
same
thing
applies:
we've
seen
at
least
down
to
the
30
000
level
or
the
10
000
installs
level,
but
we
really
want
to
get
those
resolved.
A
Okay,
next
topic,
then,
is
HTML
unit
3
upgrades,
so
this
one,
the
HTML
unit
project
changed
their
package
name
and
changed
some
of
their
apis
in
their
upgrade
from
two
to
three
and
Tim
Jacob
and
Basel
have
have
done
the
Preparatory
work.
Tim
has
tooling
that
creates
pull
requests.
You
can
see
the
hyperlinks
here.
The
test
harness
has
been
upgraded,
core
has
been
upgraded,
the
plug-in
Palm
has
the
plug-in
bill
of
materials,
and
there
are
150
open,
plug-in,
pull
requests.
A
So
there's
there's
still
a
lot
of
work
to
do
there,
but
the
work
is
proceeding.
It's
this
one,
because
it's
all
test
infrastructure
is
not
a
risk
of
breaking
Jenkins
users
at
runtime.
The
challenge
is,
if
you
choose
to
upgrade
to
plug
in
Palm,
4.66
or
newer,
you
need
to
adapt
yourself
to
HTML
unit
3..
Now
Uli
and
Alex
I
believe
you're,
both
also
plug-in
maintainers.
Are
there
any
things
that
you've
experienced
in
your
plugings
around
this?
That
you
wanted
to
highlight.
D
I
am
not
using
HTML
unit.
Oh
and
look
at
my
plugins
real
user
interface
tests
with
acceptance
test
harness.
Okay
in
my
plugins
it
yeah.
It
seems
that
HTML
unit
is
something
one
should
not
use
anymore.
So,
let's
I
completely
removed
it
in
from
my
plugin
tests
and
I'm,
using
a
real
browser
tests
with
80
ath.
B
Was
just
checking
I
have
received
one
PR
from
Tim,
pretty
smooth,
updating
the
Imports
and
changing
a
couple
of
methods,
but
this
is
basically
it
checks,
went
green
and
I
merged
that
last
week,
great.
C
Oh
well,
the
upgrade
of
guava
in
2.406
had
a
bug
for
Windows
users
when
creating
temporary
files,
and
there
were
two
plugins
that
used
guava
to
create
temporary
files,
artifactory
and
check
marks.
C
So
those
were
broken
on
windows
with
2.406,
but
we
were
able
to
get
in
contact
with
the
guava
developers
and
they
fixed
this
problem
in
a
new
version
of
guava,
which
we
should
be
releasing
in
Jenkins
core
tomorrow
in
the
latest
weekly.
So
that
should
resolve
the
Windows
issue
that
we
saw
I.
Think
that's.
A
A
And
that's
that's
especially
valuable
I
think
that,
yes,
that
means
they're
testing
Windows
more
than
they
ever
tested
it
before.
We
like
that
great
Google
summer
of
code
is
continuing
and
the
early
end
of
life
for
Centos
7
has
been
announced
and
we're
going
to
accelerate
the
visibility
of
that
warning
so
that
it
will
begin
appearing
to
LTS
users
at
the
end
of
this
month
with
2.401.2.
A
It's
it's
been
approved
by
Tim,
jacol
and
merged,
so
thanks
very
much
Alex
for
your
inputs,
thanks
for
Tims
and
thanks
for
Basils
last
item.
Our
next
item
was
on
GitHub
Enterprise
and
this
one
Alex.
Maybe
you
want
to
describe
what
prompted
it
you
gave
us
a
blog
post
about
it,
tell
us
more
about
how
that's
that's
working
Etc.
B
B
B
B
B
A
C
Well,
we've
started
using
it
in
Jenkins
core
to
on
the
Windows
CI
builds,
so
they
they're
a
lot
shorter
now
for
pull
requests
because
we're
running
a
subset
of
Windows
tests
in
Jenkins
core,
and
so
that
was
the
first
of
the
next
steps
in
the
next
steps
bullet
a
few
lines
down.
So
that's
been
done
and
the
next
step
after
what
has
been
done
already
is
the
second
bullet
and
the
next
step
section,
which
is
to
add
subsetting
to
ath,
so
I'm
hoping
to
get
to
that
sometime
this
week
or
next.
A
C
No
I
mean
if
we,
if
they're
we're,
still
running
full
Builds
on
builds
to
the
main
branch.
So
if
there
was
a
test
that
was
failing
in
a
PR
but
we
didn't
but
but
subset
it
away,
we'd
notice
it
as
soon
as
that
PR
was
merged
to
the
main
branch.
We
haven't
noticed
anything
like
that:
okay,.
A
C
And
the
only
thing
I
can
think
of
or
would
have
caught
problems
would
be
that
guava
issue,
and
you
know
that
we
would
have
caught
that
in
PCT,
but
we
don't
run
PCT
on
windows
at
all,
so
we
didn't
catch
it.
There
I
did
run
PCT
with
the
guava
upgrade,
but
it
was
all
on
Linux
right,
so
I
don't
think
launchable
would
have
helped
us
in
that
case,.