►
From YouTube: Jenkins Governance Meeting, Sep 16, 2020
Description
Recording of the regular Jenkins Governance meeting. At this meeting we discussed the recent news (2.249.1 release, security advisory for plugins, GSoC/GSoD, and the upcoming DevOps World conference) and the incoming governance board and officer elections. We have also reviewed the public roadmap status and agreed on the status changes required there.
Full agenda and meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o
B
A
B
About
that
sure
so
jenkins
2.249.1
has
released.
There
was
some
concern
expressed
initially
about
compatibility.
We
did
vlad
silverman
and
I
did
some
deep
testing
of
windows
in
various
scenarios.
Upgrading
from
previous
versions
to
current
version,
I've
been
monitoring
the
jira
bug
queue
since
then.
Looking
for
issues
and
problems,
there
are
still
some
known,
node
issues,
issues
being
reported
and
we've
just
it's.
It's
been
an
interesting
release,
so
windows
agents.
A
A
B
So
vlad
and
I
posted
a
description
of
the
testing
process
we
used
and
describing
the
three
window
scenarios
we
use,
it's
been
merged
and
is
already
available.
Okay
and-
and
so
we
have
that
one.
There
is
a
revision
proposed
to
the
upgrade
guide
to
deal
with
two
surprises
and
that
revision
to
the
upgrade
guides.
Still
that's
the
second
one
down
on
your
list
there
and
it
still
needs
a
revision
based
on
feedback
from
jesse
glick.
But
I
don't
think
either
of
those
things
are
particularly
catastrophic.
B
A
A
B
Correct
it
was
purely
it's
purely
what
what
what
I
realized
is
vlad
and
I
were
testing
is
we
have
been
through
a
number
of
scenarios
that
may
not
be
documented
anywhere.
We
thought
well,
we
could
put
it
into
formal
documentation,
but
that
will
take
longer
than
if
we
just
do
a
blog
post
for
now,
so
we
intentionally
did
a
shortcut
did
the
blog
post
so
that
it
could
be
out
there
in
case
it
would
help
someone.
D
It
was
a
fairly
routine
security
advisory,
the
most
popular
effective
plugins
for
the
email
plugins,
where
java
just
has
a
bad
default
and
does
not
actually
perform
hostname
validation,
and
there
were
two
issues
in
lotion
plug-in,
and
I
would
like
to
mention
that
the
initial
version
of
the
security
advisory
had
a
bad
description
for
the
second
one.
It
was
the
same
problem,
but
it
did
not
correctly
identify
what
the
problem
was.
D
D
However,
the
in
this
case
the
only
thing
that's
wrong
in
the
cve
entry
is
the
cwe,
which
is
a
classification
for
the
kind
of
vulnerability
it
is,
and
the
description
itself
was
correct:
2020,
oh
yeah,
maybe
it
hasn't
been
published
yet
well
I
mean
I
would
expect
them,
and
that
description
is
correct.
As
I
mentioned,
the
only
thing
that's
wrong
would
be
the
cwe,
and
I've
submitted
an
update
to
the
database
there.
So
I
would
expect
anyone
who
consumes
the
cve
database
to
synchronize
later
changes
as
well.
D
A
D
A
And
yeah
all
other
node,
so
google
summer
of
code
is
officially
over.
I
have
seven
projects
this
year
and
all
the
projects
have
been
completed
successfully,
so
we
are
still
working
on
summarizing
the
results
on
the
project
side,
but
if
you're
interested
you
can
go
to
the
jenkins
youtube
channel
and
they're
all
themselves.
A
Similarly,
if
you
go
to
any
project,
there
are
also
links
to
videos
and
recordings
of
what
was
presented
in
the
end
of
august,
so
yeah
thanks
again
to
all
contributors,
including
students,
applicants,
mentors
shortcut
means
and
basically
anyone
who
contributed
to
the
projects
because
of
course,
it's
the
first
year
when
all
projects
succeed,
yeah.
I
believe
that
all
projects
have
delivered
significant
changes
which
are
important
to
the
community.
A
This
is
quite
excessive
success
for
us
and
yeah.
Obviously
we
should
keep
doing
it
next
year,
so
we
have
started
retrospective.
The
first
retrospective
meetings
was
actually
today
and
if
anybody
has
any
feedback,
please
follow
up
on
the
my
link
list
so
that
you
incorporate
this
feedback
for
the
next
year.
A
So
if
you're
interested
to
know
more,
there
is
a
project
page
on
genki
scion
and
basically
the
goal
is
to
have
documentation
sections
for
jenkins
and
kubernetes
right
inside
our
documentation,
so
that
we
can
highlight
how
to
use
jenkins
and
how
to
install
jenkins,
how
to
configure
the
edd
addressing
other
deployment
options,
like
arbitrators,
help,
charts
and
many
other
things
which
are
available
in
the
kubernetes
ecosystem
for
jenkins
right
now.
Basically,
nothing
is
really
documented
on
the
jenkins
io
website,
so
at
least
creating
some
solution
pages
and
creating
the
index
of
existing
documentation.
A
A
If
anyone
is
interested,
please
join
us
and
yeah
another
update
that
next
week
we
actually
have
devops
world.
So
this
is
one
of
the
reasons
why
we
start
shifting
governance
meetings
so
that
there
is
no
overlap,
and
I
believe
that
there
will
be
a
lot
of
community
presence
today,
including
multiple
junkies
related
talks,
including
community
booths
and
others.
So
maybe
please
would
you
like
to
summarize:
what's
going
on
there
for
the
drinks
community.
E
So
in
total
we
have
close
to
more
than
50
breakout
sessions
that
is
community
related
open
source
related.
We
also
have
a
cdf
booth,
so
under
that
booth
we
have
the
different
projects
there's.
So
if,
if
anybody's
interested
in
helping
out
at
the
booth,
I'm
going
to
be
on
the
platform
pretty
much
all
day,
tuesday
to
thursday,
so
I'll
be
monitoring
and
monitoring
speaker
sessions
as
well
as
the
booth.
E
Let
me
see
what
else
and
for
this
meeting
I'm
asking
for
permission
to
get
the
the
devops
world
logo
on
the
jenkins,
dot,
io,
jumbotron
and
then,
and
then
probably
shortly.
We
will
I'd
like
to
get
permission
to
get
ad
cd
con,
which
is,
which
is
a
virtual
conference
that
is
taking
place
in
october,
that
is
hosted
by
cdf
as
well,
and
there
are
jenkins
and
jenkins
acts
and
all
a
lot
of
the
projects
sessions
are
on
that
event.
E
A
D
A
A
A
Okay,
so
yeah.
If
you
play
jumbotron,
it
would
be
nice
to
also
create
an
event,
maybe
even
put
it
into
the
calendar
yeah,
I'm
not
sure
whether
it
will
generate
any
additional
traffic,
but
yeah
listing
events
could
be
important
because
really,
instead,
here
we
list
on
the
blog
pages,
etc.
So
it
will
improve
visibility.
B
A
Yeah,
so
this
blog
post
basically
summarizes
the
incoming
sessions
and
yeah.
There
are
three
sessions
about
jenkins,
two
just
about
one
about
j
cask
by
william
another
one
about
dicton
client.
So
this
what
we
were
discussing
from
cloud
native
seek
we've
been
trying
to
organize
a
meeting.
It
will
succeed
but
yeah.
Maybe
we
will
do
one
after
citycon
so
and
yeah.
There
was
ted
talk,
but
I'm
not
sure
what
it
is
about
and
it's
not
listed
so.
E
C
A
Note
that
we
have
multiple
jumbotrons,
for
example,
we
have
for
now
published
jsoc
one
will
be
removed
with
my
pull
request,
which
has
been
already
submitted,
hi.
Regarding
me,
the
continuous
delivery
foundation.
I
believe
that
we
can
safely
remove
it
as
well.
It
has
been
on
for
more
than
one
year,
yeah.
E
A
A
A
I
don't
have
time
there,
I'm
good
okay,
so
for
elections.
Yes,
we
discussed
in
august
if
you
want
to
hit
the
target
date.
I
mean
beginning
of
december
announcement
for
new
officer
assignments
and
elected
port
members.
We
need
to
hold
elections
in
november
and,
although
it
looks
like
we
have
a
lot
of
time,
actually
we
don't
if
we
take
the
existing
process.
A
So
this
is
what
we
discussed
at
the
last
governance
meeting
and
I
tried
to
address
the
comments
submitted
by
board
members
and
other
contributors,
and
I
think
that
we
really
need
to
start
finalizing
this
process
so
that
we
can
make
a
decision.
Firstly,
whether
we
make
a
change
when
compared
to
the
previous,
and
if
you
make
the
change
here,
we
will
need
to
roll
out
it
quickly.
A
You
can
commit
some
time
this
week
and
next
week
to
get
it
done,
but
we
need
to
agree
in
principle
whether
we
change
the
process
and
I
seek
feedback,
especially
from
alex
from
daniel
from
alisa,
so
alisa
mark
and
daniel
will
be
up
for
election.
If
you
decide
to
participate
me
and
alex
yeah,
basically,
we
remain
for
another
year.
B
And
I
think
I
think
the
new
proposal
is
is
sufficient
and
I
think
we
should
go
with
the
change
I've
read
through
it.
I
don't
see
any
any
major
gaps
or
problems
the
place
that
I
raised.
The
one
question
oh
like
you
had
addressed,
so
it
was
about
github
organization,
user
id
being
part
of
the
form
that
we
asked
them
to
submit.
A
Yes,
just
to
summarize
what
changes
key
change
is
that
we
do
not
want
to
rely
on
jenkins
lab
database
for
reaching
out
to
contributors
and
eligible
voters.
Instead
of
that,
we
first
make
requirement
that
basically,
election
is
done
by
contributors,
but
the
criteria
for
contribution
is
not
just
a
meter.
It's
basically
anyone
who
can
prove
a
public
contribution
before
september
1st
this
year.
A
So
that's
basically
the
whole
idea
of
the
change
and
yeah.
It
also
makes
to
stage
election
official
because
it
wasn't
it's
not
documented
in
the
current
election
process,
but
it's
the
fact
effectively
what
we
had
to
use
last
year,
because
we
were
unable
to
handle
six
voting
for
100
southern
participants.
A
A
Yeah,
it's
fine
so
for
me
yeah
assuming
that
well,
at
least
here,
since
we
intend
to
change
the
process.
So
what
I
will
do
tomorrow,
I
will
actually
recommend
the
process
and
submit
it
as
pull
request
to
the
election
process.
So,
in
addition
to
this
doc,
there
will
be
actually
a
formal
documentation
for
the
process
on
this
page.
B
B
F
F
F
A
A
A
A
A
A
C
A
C
G
A
B
A
B
A
B
A
Thank
you,
configuration
ui
tables
to
leaves
which
I
think
we
need
to
discuss
the
status.
I
there
was
supposed
to
be
a
ux
sequencing
today,
but
I
guess
we,
it
will
happen
only
in
two
weeks
but
yeah.
For
me,
it
would
be
interesting
to
know
whether
we
plan
to
merge,
because
the
main
concern
was
about
compatibility
issues
not
about
the
feature
readiness.
So
at
some
point
we
we
need
to
make
a
call
whether
we
merge
it.
A
B
Moving
to
mirror
beats,
so
the
mirror
bits
move
is
complete.
What's
not
completed
is
the
disabling
and
shut
off
of
the
old
infrastructure
and
the
transition
for
windows.
So
it's
I
think
it's
current.
I
don't
think
it
is.
It
is
near
term
it's
really
current
and
it's
actively
being
used
in
production
in
many
use
cases,
but
we've
still
got
a
few
use
cases
left
to
do.
They
were
discussed
in
the
infrastructure
meeting
on
tuesday
tim
noted
two
or
three
that
we
still
need
to
do
so.
C
A
Well,
there
was
a
pull
request
today
to
update
glossary.
So
now
here
you
can
find
a
controller.
There
is
still
master,
but
this
disclaimer
is
duplicated
term
later.
I
think
probably
we
need
to
move
duplicated
terms
elsewhere,
but
yeah
this
glossary
is
updated
for
me,
what's
important
for
this
section
item,
so
technology
updates
inherently
include
a
lot
of
minor
tasks
and
we
have
octoberfest
starting
in
two
weeks.
A
So
what
could
be
done?
We
could
highlight
terminology
now.
Both
agents
and
masters
white
is
politics
for
oktoberfest,
but
in
such
case
we
really
need
to
have
a
set
of
tasks
somewhere
as
github
wishes
or
strengthens
jira
and
right
now
there
is
still
a
link
to
the
developer.
My
name
is,
I
believe
that
took
an
action
item
to
create
these
tasks,
but
I'm
not
sure
who
was
it.
A
Yeah
for
october
first
good
first
issues
will
be
automatically
highlighted
on
a
random
basis
to
hacktoberfest
contributors
as
well
the
highlight
through
github,
I
would
say
it
could
well.
If
jenkins
io
website
was
in
the
jenkins
ci
github
organization,
it
would
have
been
even
better
in
terms
of
highlighting,
but
it's
definitely
not
a
reason
to
move
the
website.
A
So
just
creating
good
first
issues
could
help
us
and
we
also
need
to
document
it
as
featured
project,
and
this
is
definitely
marked
section
item
total
work,
the
up
test
page
right
now.
Yes,
I've
still
got
that
yeah.
Maybe
we
should
move
it
to
current,
with
the
assumption
that
we
create
this
framework
so
that
we
can
unbox
more
contributors.
A
A
A
A
D
A
A
Built-In
plugin
management
is
called.
We
had
an
agreement
from
jcask
meeting
that
we
want
to
redefine
this
item
a
bit
basically
to
have
a
roadmap
embedded
in
a
plugin
installation
manager
tool.
We
haven't
done
it
yet,
but
so
yeah,
it's
rather
near
term,
though
recently
there
was
a
2-0
release
with
some
changes
but
yeah
my
best
feeling
that
we
will
also
need
a
3.0
very
soon,
because
there
is
still
some
strange
behaviors
in
the
component.
A
C
A
A
A
Works
as
well,
so
it's
development
instance,
but
basically
it's
smallest.
What
was
no
sorry,
it's
actually
all
prevention,
because
I
switched
to
another
branch
yeah
it's
here,
so
this
was
published
on
the
website.
We
have
a
few
stories
and
maybe
it
makes
sense
to
put
them
on
the
roadmap
explicitly
so,
for
example,
build
logs.
A
It
would
be
nice
to
have
taskbox
configurations,
maybe
not
because
after
the
junk's
configurations
code,
arguably
nobody
really
needs
a
plugin
storage
for
configurations.
It's
arguable,
but
definitely
doesn't
seem
to
be
a
priority.
Like
code
coverage
results.
Yes,
it
makes
sense,
buildtrans
jobs,
it
would
be
nice
to
have
it
listed
for
test
results.
A
Yeah
tim
jacom
currently
is
working
on
updates,
so
the
unit
plugin
has
been
already
released
with
changes
to
support
that
the
results,
a
reference
implementation.
It
still
needs
to
be
hosted
on
jenkins
organization,
but
I
think
that
it
was
being
mentioned
on
the
roadmap
and
yeah
for
the
rest,
yeah
other
items.
I
also
think
it
makes
sense
to
put
them
on
the
roadmap.
A
A
A
Drinking
fast
capabilities,
basically
drinks
fire
runner,
but
rather
with
tooling
perspective
and
this
packaging
perspective,
so
I'd
be
different
domains
as
this,
and
maybe
when
I
have
better
roadmap
for
next
phases,
I
will
not
be
working
recommending
some
kubernetes.
Now
it
should
be
in
progress,
so
I
will
move
it.
Click
on
pipeline
execution
engine.
Maybe
you
should
be
moved
to
short
term
because
yeah
there
is
a
lot
of
discussions
already
happening
around
that
but
yeah.
Let's
see
blackboard
storage,
we
discussed
okay
and
you
think
we
miss
four
cloud
platforms.
B
B
A
B
Right
and
so
so
that
that's,
but
that
that
we've
seen
progress,
the
alpine
image
has
been
updated
to
use,
adopt
open,
jdk
the
adopt
open
jdk.
The
adoptium
project
was
willing
to
provide
the
alpine
image
base
for
us,
and
it's
worked
out
reasonably
well
or
the
alpine
build
custom
jenkins
distribution
build
service
was
a
google
summer
of
code
project.
A
A
Better,
we
plan
to
keep
working
with
sledding
to
see
how
we
can
proceed,
but
as
a
service,
it's
definitely
not
ready
as
a
self-hosted
solution.
It
might
be
moved
to
preview,
but
you
will
need
to
think
how
we
reorganize
roadmap,
because
it
can
be
two
parts:
custom
jenkins,
distribution
built,
two,
probably
not
but
yeah.
They
need
to
think
how
to
call
it
and
the
customized
drink
is
say.
Oh
then,.
B
C
A
B
Got
it
okay,
then,
in
the
far
right
most
column,
java,
14
plus
support
should
now
be
updated
to
javascript
they've
just
released
java
15,
but
it
is
not
an
lts
we
get.
We
need
to
look
again
to
see
when
the
actual
jdk
project
plans
to
do
an
lps.
The
last
I
heard
it
was
targeted
for
17,
but
there
was
noise
in
the
mailing
list
that
it
might
be
16..
So
we
need
to
check
that
further.
A
B
Right
and
I
I
think
that's
completely
infeasible
too
many
people
critically
depend
on
java,
8.
yeah.
So
this
one
is
an
open
topic.
I
would
rather
let
it
sit
and
even
wait
until
after
java
goes
with
their
lts
before
we
start
work
on
it.
So
it's
I
think
java
8
is
much
more
valued
in
the
computer
community.
Right
now
than
java,
11.
B
A
A
A
Unless
he
just
made
it
yeah
so
anyway,
it's
no!
It's
not
mission.
Okay
cloud
native
java
support
yeah
definitely
future
well.
I
have
some
good
progress
in
junkies
file
runner
but
yeah.
Extrapolating
the
experience
of
drinks
fall
runners
on
drinking
in
this
particular
matter.
It
doesn't
seem
to
be
feasible.
A
B
B
A
A
Yeah
plugin
bomb
static
analysis,
local
automation,
dependency
management,
basically,
nothing
changed,
so
we
it's
mostly
the
documentation
issue
but
yeah
this
bits.
I
would
rather
keep
it
as
this
on
the
wrong
path
for
the
next
infrastructure
for
experimental,
docker
images
and
continuous
delivery
of
jenkins
plugins.
With
the
incoming
changes
for
docker
hub
and
this
constitution
reported
for
the
factory
yeah.
It
looks
like
these
items
are
rather
subject
for
under
consideration,
so
not
touching
them,
but
yeah.
A
A
C
A
B
A
Okay,
yeah
moving
on
so
funding
con
community
breach
no
changes,
it's
available
in
the
preview,
but
we
haven't
promoted
to
it,
which
means
we
didn't
really
get
any
money
so
far.
Although
the
process
is
documented,
it's
not
working.
So
I
believe
it's
on
my
list
to
push
the
eventually
over
the
line,
but
yeah
right
now.
If
you
ask
about
status
of
jenkins
money.
A
A
A
G
A
B
B
And
next
meeting
we
we
should,
we
will
include
on
the
agenda
jfrog
artifactory
and
what
we
know
about
that.
There's
really
nothing
to
say
this
time,
but
next
time
we've
got
to
discuss
what
what?
If
we?
What
if
daniel
and
I
learned
about
artifactory
and
what
do
we
need
to
do
in
order
to
meet
their
their
requirements?
A
A
A
A
B
B
A
B
A
So
I
guess
that's
it
for
today
and
you're
sorry
for
going
cover
time.
I
yeah.
I
need
to
think
how
to
do
the
roadmap
review
better,
but
at
the
same
time
we
just
need
to
do
it
once
per
quarter
according
to
the
job
right,
so
it
shouldn't
be
a
problem
for
the
next
meetings,
at
least
thanks
to
everyone.
For
your
time.