►
From YouTube: Jenkins Governance Meeting, Jun 30, 2021
Description
Jenkins Governance Meeting June 30, 2021. Topics included:
* News - Jenkins 2.289.2 and 2.300 security releases, Contributor Summit, Google Summer of Code upcoming webinar, Oleg takes a break
* Jenkins funding update
* Plugin end-of-life policy
* Discourse evaluation status
Notes in https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.apj7jmvnm2f3
A
Welcome
to
the
jenkins
governance
meeting
it's
june,
the
30th
2021
thanks
everyone
for
being
here,
uli
and
daniel
thanks
very
much
so
topics
that
I
have
news,
keep
it
very
brief
daniel.
I
assume
that
you'll
have
something
to
share
with
us
on
news
thanks
very
much
for
your
heroism
today
and
then
a
brief
on
jenkins
funding,
update
just
a
status
report,
plug-in
end-of-life
policy
summary
or
discussions
from
the
developer
list
discourse
any
other
topics
that
need
to
be
added,
not
for
me.
A
Okay,
then.
Let's
talk
news
first
and
the
biggest
news
is
jenkins.
2.289.2
and
2.300
security
releases
were
delivered
today
thanks,
it's
very,
very
much
daniel
for
doing
those.
It
also
fixes
security
issues
in
three
plug-ins.
Very,
very
grateful
for
that
anything
that
you
wanted
to
share
daniel
with
regard
to
the
security
advisory.
B
There
is
one
issue
I
send
an
email
to
the
developer
list
that
one
that,
due
to
infra
issues
this
afternoon,
that
we
had
to
work
around
these
two
jenkins
releases
as
well
as
selenium
html
report
plugin,
are
not
available
in
the
releases
repository
in
artifactory,
as
they
would
usually
be
because
that
didn't
work
this
afternoon
and
we
had
to
I
made,
I
made
the
staging
repository
that
we
generally
only
used
temporarily.
B
But
there
may
be
issues
and
we
will
resolve
that
as
soon
as
our
defectory
behaves
normally
again
and
additionally,
I
mentioned
some
of
the
repositories
and
workarounds
we
had
to
apply,
and
I
would
ask
everyone
to
not
rely
on
the
continued
presence
of
these
workarounds
just
in
case.
A
And-
and
that
makes
sense
so
your
your
point-
there
is
that,
in
order
to
handle
some
challenges
to
earlier
today
with
infrastructure,
you
had
to
do
something
a
little
bit
different
but
temporary.
With
the
repository
configuration
and
eventually
your
intent
is
to
go
back
to
the
standard
repository
configuration.
B
Essentially,
yes,
so
the
artifacts
exist
they're,
just
in
a
different
repository
than
expected,
but
once
we
can
move
them
over,
we
will
and
these
temporary
repositories
will
go
away,
so
nobody
should
be
relying
on
them
more
details
about
that
are
in
my
email
to
the
developer
list.
A
Great,
thank
you
very
much
daniel,
and
so
let
me
make
a
note
of
that
and
I
will
include
a
link
to
the
developer
list
for
details
of
temporary
yeah,
temporary
artifact
or
temporary
repository.
A
A
A
A
A
Okay,
then
jenkins
funding
updates
this
one.
To
give
a
brief
summary
jenkins.
Treasury
has
been
hosted
at
this
at
software
in
the
public
interest
for
many
many
years,
and
now
that
we're
part
of
the
continuous
delivery
foundation,
we
can
move
those
funds
from
spi
to
cdf
the
it's
in
progress,
but
it
will
likely
need
to
wait
until
oleg
returns.
A
A
Okay,
plug-in
end-of-life
policy
was.
This
is
continuing
to
be
discussed
in
the
google
groups
in
the
developer
list
and
it
was
discussed
in
depth
in
a
session
at
the
contributor
track.
Encourage
you
to
view
that
that
vid
or
read
the
notes
from
that
video
and
continue
the
discussions
in
the
google
group.
A
B
A
That's
quote
now
daniel
I
did
have,
I
know:
we've
got
the
lfx
security
2
project
running
or
running
is
the
wrong
way
to
say
it
under
discussion,
but
I
didn't
have
any
status
to
share
here,
and
so
I
intentionally
did
not
put
it
on
the
agenda.
Just
saying,
look
we're
we're
watching
that
thing
evolve
and
we'll
get
involved
with
them
as
they
continue
to
involve
with
us.