►
Description
Meeting notes: https://docs.google.com/document/d/1FARi55vDjsdzi6Nj9ZB9e1wh2dU8nyWK6mq_cge0ceg/edit#
A
Hi
everyone
welcome
to
the
platform
sick
meeting.
This
is
our
fifth
meeting
and
yeah
special
group
works
on
several
projects,
including
Java,
eleven
support,
multi
architecture,
docker
images
and
Windows
agents.
So
at
this
meeting
we
will
have
a
short
update
for
each
project
and
we
will
sync
up
on
the
next
actions.
Just
in
case
you
are
interested
to
get
more
information
or
join
the
discussion.
We
have
Gita
channel
just
a
second
I'll
share
my
screen.
A
Yep,
okay,
thank
you!
So
yep
we
have
a
jenkins
area.
Slash
platform
seek
gita
channel
here
you
can
find
a
participant
link
and
also
link
to
the
meeting
notes
from
this
document.
So
everything
we
will
be
discussing.
They
will
attract
in
the
this
Google
Doc
and
then,
of
course,
we
will
publish
it.
So
you
try
to
admit
it
not
so
there.
A
So
today
we
have
three
items
in
the
agenda
just
in
couple
for
all
projects
we
have
then
I
wanted
to
discuss
regular
office
hours
before
we
proceed
and
I
also
want
to
discuss
all
Summer
of
Code
project
IDs.
So
this
is
an
agenda
for
today
and
yeah
I
would
start
with
the
regular
office
hours.
So
my
first
question
to
you
guys
is
whether
we
really
need
that
and
if
yes,
how
often
I
was
about
proposing
a
meeting
every
two
weeks,
but
here
maybe
we
want
to
meet
more
often
or
maybe
just
once
per
month.
A
A
Maybe
we
could
just
go
forward
with
the
current
time,
but
yeah
I'm
afraid
it's
a
bit
earlier
for
the
west
coast,
but
on
the
other
hand,
other
participants
can
join.
So
probably
we
could
just
keep
the
current
time
slowed.
Let's
see
what
doodle
says:
okay
I
believe
it's
something
we
could
go
forward
twist.
Yep.
A
E
E
One
was
kind
of
updating
the
existing
Windows
installer
and
the
other
one
was
chocolaty
packaging,
so
I
during
Jenkins
world
and
I
kind
of
worked
with
mark
a
little
bit
to
test
out
my
initial
updates
of
the
windows
installer
and
received
some
feedback
from
mark,
and
there
were
some
questions
that
we
kind
of
came
up
with
him
talked
about
a
little
bit
just
based
on
that
kind
of
way
that
modern
windows
works
as
compared
to
how
the
windows
installer
was
developed
when
you
know
as
Windows
XP.
Basically
so.
E
There's
some
there's
some
questions
there
in
terms
of
like
where
Jenkins
home
should
go
on
the
system,
because
the
idea
would
be
to
allow
the
user
to
specify
a
user
account
to
run
this
service.
As
so,
do
we
want
the
Jenkins
home
to
go
into
their
home
directory,
or
do
we
want
it
to
go
into
a
shared
location?
E
So
those
are
just
some
questions.
I
didn't
I
didn't
have
any
answers
to
those
yet
so
maybe
this
group
can
help
kind
of
figure
those
out,
but
I
have
a
working
installer
that
you
know
it
looks
more
updated
than
the
previous
one
and
and
provides
some
additional
capabilities
for
setting
properties
of
how
Jenkins
will
run
like
the
user
account,
for
instance,
and
and
it
will
search
for
a
Java
installation
instead
of
using
a
packaged
version.
There
are
our
version.
That's
packaged
along
with
the
installers.
E
E
E
And
really
is
looking
for
some
additional
feedback
before
I
submitted
a
PR
in
a
in
addition,
at
the
the
way
that
the
installer
is
built
right
now
in
on
the
trust
and
infrastructures
a
little
bit
murky
there,
it
uses
things
like
cygwin
and
stuff
like
that.
That
I
think
could
be
cleaned
up
significantly
using
the
Jenkins
files,
but
I
don't
have
enough
information
about
what
the
infrastructure
looks
like
or
what's
available
in
order
to
kind
of
push
forward
and
create
a
Jenkins
file.
Yeah.
A
E
A
It
would
be
great,
but
even
before
that,
maybe
we
could
discuss
heaven
experimental
packages
listed
on
Jenkins
I
own,
so
it
actually
applies
to
all
stories
we
have
to
be
so.
We
have
Gingka,
say
you
download.
The
res
only
launch
our
money.
We
can
probably
we
could
somehow
add
experimental
button
here
and
this
multi
platform,
docker
images,
Java,
11
downloads,
chocolaty
and
whatever
else
we
have
yeah
that'd
be
great.
A
D
Great
in
terms
of
evaluating
the
windows
installer:
do
you
would
it
help
to
have
more
people
exploring
that
I
I
know,
I
haven't
done
a
Windows
install
with
your
current
code
since
Jenkins
world?
So
even
if
we
don't
have
don't
yet
have
the
experimental
page
on
the
download
site,
I
may
be
able
to
give
you
some
time
to
help
with
help
with
checking
out
that
Windows,
installer
and
I
know.
I'm
gonna
want
to
be
some
experimenting
with
chocolaty
shortly.
E
E
D
E
With
the
with
the
windows
installer,
yes,
there
is
that's
why
we
need
to
build
it
on
the
trusted
infrastructure
because
they
are
there's
a
signing
key
and
so
forth.
That
is
used
so
that
and
that's
part
of
the
stuff
that
I
don't
know
a
ton
about
how
its
set
up.
But
yes,
we
definitely
want
to
sign
the
windows
installer
so
that
people
can
verify
that
it's
from
the
correct
source
and
so
forth.
Well,
it's
just
windows
that
are
picking
yourself
or
installer
requires
signing
in
certain
circumstances.
So
we
definitely
want
to
sign
things
and.
C
E
A
C
A
A
D
A
Yep
so
well,
we
keep
it
in
chocolaty.
We
have
always
notion
to
set
up
with,
on
another
instance,
just
to
set
up
a
distribution
but
yeah.
The
main
problem
is
that
is
trigger
and
cough
releases.
So
pretty
much
the
same
problem
like
we
hit
with
multi
architecture.
Doc
is
packagin,
but
we
could
set
up
what
hooks
if
needed,
yeah.
E
E
E
Is
it
so
I
went
through
it
for
I
am
only
the
maintainer
of
ironpython
I
went
through
it
for
that,
and
it
was
mainly
I
just
had
to
show
that
I
had.
You
know,
commit
access
and
administration
access
on
the
github
repo,
so
I
don't
think
there
was
the
legal
entity
requirement
there.
I
can
find
out
more
information.
Now,
okay,.
A
A
D
Jep
seems
like
a
good
idea
in
particular,
because
we're
taking
over
the
we
really
do
want
to
make
a
transition
of
responsibility
away
from
the
rather
Abha
or
the
ad
hoc,
the
community-based
chocolaty,
to
something
or
to
to
a
an
individual
in
the
community.
Now
to
you
having
the
community
as
a
whole
on
it,
oh
yeah,
I
think
you're.
Jeff
is
a
good
thing.
A
A
A
C
Point
in
it
was
kind
of
should
we
start
trying
to
describe
what
well,
if
the
real
commitment
is
very
clear.
But
what
are
the
packages
we
kind
of
tube
leash?
Has
a
community
or
whatever,
but
yeah
I?
Don't
think
anyone
is
going
to
want
to
make
that
official,
because,
right
now
we
can
just
escape
by
saying
well,
this
was
never
super
red.
You
know
I.
A
Believe
that
we
should
just
create
the
jobs
for
major
changes
we
are
doing
forward
and
if
there
is
tremendous
interest
to
have
forced,
encourage
increased
distribution
so
that
probably
we
create
a
job
or
to
describe
the
places.
So,
for
example,
now
it
would
be
a
good
question
about
multi
resection,
docket
image
next
topic,
but
I'm
not
sure
about
other
packages.
A
A
E
A
A
A
A
D
F
A
C
A
It
doesn't
change,
so
everybody
is
still
able
to
run
32-bit
platforms
and
actually
the
problem
of
force
that
by
default,
the
windows
installer
was
just
broken.
If
you
were
running
on
64-bit
system,
you
were
getting
a
jinx.
Additionally,
each
was
booted
managing
processes
on
64-bit
systems,
so
we
just
fix
64-bit,
installer
I
believe
I'm
32-bit.
Ok,
it's
a
breaking
change,
but
yeah
I
think
we're
fine
with
it.
Though
job
would
be
Radian
yeah.
B
B
A
C
B
Cross
compilation
option
is
probably
more
simpler
right
to
go
to
our
main
repository
in
some
time,
because
we
don't
need
to
add
anymore
CI
nodes
so
that
we
overcome
the
security
requirements
right,
that's
needed
by
Jenkins,
so
that
might
be
one
of
the
most
safer
options.
So
if
the
customer
must
say
okay,
we
are
all
good.
With
the
cross
compilation
binary
side.
They
are
not
having
any
issues,
then
that
might
be
one
of
the
more
easier
solutions
for
us
to
upward
to
the
Jenkins
official
docker
hub
repository
right,
that
is
Jenkins
/
Jenkins.
B
However,
what
I
have
done
at
the
moment
is:
I
am
also
I,
also
added
a
CI
for
s
390x
platform,
which
would
receive
the
notification
from
the
docker
hub
and
build
the
docker
images
more
natively
for
s
390x
and
push
it
to
the
Jenkins
for
evil
repos.
So
at
the
moment,
if
you
look
at
the
Jenkins
for
evil,
I'm.
B
A
B
C
B
B
One
is
a
cross
compilation
and
one
is
native
and
see
how
it
fares
at
the
moment,
I
have
been
verifying
this
internally
right
with
both
the
approaches
and
I
haven't
faced
any
issues
either
on
s/390,
with
power
or
even
with
alpine
based
images.
So
the
cross
compilation,
as
well
as
a
native,
a
builds
docker
images
are
faring
pretty
well
without
any
issues.
C
B
So
this
is
one
of
the
reasons
I
am
somehow
now
feeling
that
okay,
even
if
the
cross-compilation
generated
images
works
well,
I
think
that
might
be
a
easier
way
out
for
us
right,
because
you
don't
need
to
get
into
any
security
related
discussions
and
so
on.
You
know,
because
if
we,
if
we
start
adding
more
nodes
or
more
platforms
using
the
native
approach,
then
we
might
need
more
stringent
process
on
how
we
can
add
more
architectures
right
to
hook
into
the
CI
and
then
how
do
we
maintain
the
SLS
right?
B
How
quickly
each
one
can
turn
out
the
turnaround
time
and
so
on,
so
we
might
get
rid
of
that.
So
the
reason
I
am
keeping
my
fingers
crossed
on
the
cross-compilation
based
images
at
the
moment.
It's
pretty
good,
no
issues
as
such,
but
we
need
to
see
once
we
move
on
right
if
there
are
any
problems
that
the
customers
face.
So
that's
the
reason
we
have
this
to
approach,
paged
images
being
thrown
out
or
given
to
the
customers
to
try
it
out.
B
A
Along
the
risk,
with
this
pull
request
that
actually
it
becomes
a
part
of
jenkins
weekly
release
flow,
so
it
means
that
it
will
be
always
running
experimental.
Would
you
say
that
it
terrance
only
after
the
main
releases,
so
I
assume
which
yoki
they
believe.
But
hist
was
the
law
the
last
one
to
modify
this
file
last
week,
but
here
I
believe
that
it
should
be
okay
right
right.
C
B
Did
not
want
it
if
anything
fails
on
the
experimental
side,
we
did
not
want
it
to
feel
the
experimental
so
there's
a
reason.
We
had
to
explicitly
return
the
status
so
that
we
don't
fail
and
someone,
if
once
to
handle
it,
then
they
can
handle
explicitly
here
so
and
the
same
was
incorporated
in
the
docs
as
well,
because
without
having
this
incorporated,
the
dots
would
not
make
sense,
because
there
is
no
way
the
published
experimental
shell
script
would
be
invoked.
B
A
A
A
B
C
A
A
One
of
the
ways
which
we
could
probably
try
just
to
set
up
untrusted
user
on
see
aging
SEO
and
redirect
it
to
Jenkins
forever.
So,
in
addition
to
the
production
user,
we
also
have
whatever
test
user,
which
can
deploy
to
Jenkins
for
awhile
without
personal
call.
This
yeah.
All
these
obstacles
to
get
on
trust
is
cherry,
so
right,
so
that
would
it
help.
B
B
A
A
B
A
C
So
there's
that
typically
but
I
was
thinking,
I
think
yeah.
The
the
deployment
and
the
way
publishing
works
right
now
makes
it
pretty
as
I
understand
it's
feasible
to
run
it.
You
know
any
at
any
time
in
the
week.
Basically
so
I'm
not
saying
this
is
ideal,
but
you
don't
really
have
to
like.
We
did
wait
for
the
lately
next
week
or
whatever
you
know
to
have
some
run.
C
So
the
next
week
is
going
to
Poole
to
trigger
some
automated
one,
but
if
you
would
just
merge
something,
I
want
to
try
and
before
you
hits
the
fan,
basically
checking.
If
the
thing
you
added
it's
not
breaking
everything,
I
guess
we
can
probably
just
ask
in
for
a
team
to
run
the
build
and
see
you
know
as
if
still,
if
things
still
stay
red,
green
or
goes
red
whatever
you
know
and
try
to
fix
it
before
the
actual
release,
not
a
week
after
it.
Well.
C
We
know
I
mean
they
formed
from
somewhere,
watching
that
it
could
wonder
what
the
hell
but
yeah
it's
it's
been
it's
worth
the
case
before,
and
so
some
of
us
know
why
it's
been
done.
This
way,
it's
possible
for,
for
privacy,
reasons
and
security
reasons.
Many
many
things
were
actually
moved
out
of
the
public
access,
so
yeah
that
that's
one
of
the
cons
with
that.
Definitely,
but
nothing
can
be
perfect.
C
A
C
Yeah,
because
I
think
we
got
kind
of
a
discussion
similar
similar
to
this
this
morning,
basically
saying
the
situation
about
that
is
no
specific
in
the
end
of
experimental
bills,
because
there's
also
going
to
be
the
case
more
and
more
often
regular
alleyways.
You
know
the
JDK
release
the
Kadence
acceleration,
so
you
know
make
changing
things
that
could
break
everything
is
going
to
become
probably
more
irregular,
so
we
need
to
probably
see
how
to
make
that
more
sustainable,
I
guess.
B
So
Oleg-
and
that
is
right,
so
what
what
is
the
process
right
now?
We
have
been
adding
so
many
new
things,
so
Java
11
and
there
have
been
there
will
be
some
more
features
that
comes
in
which
might
need
such
changes
right.
So
is
there
any
process
in
order
to
get
this
ruled
out
and
tested
on
the
trusted
CI?
Or
is
it
always?
B
A
A
B
C
B
A
C
A
A
B
A
A
A
Okay,
so
thanks
a
lot
for
the
update,
yeah
I
believe
we're
doing
a
good
progress
prayer,
so
one
of
the
shortcuts
would
be
to
just
get
everything
published
from
external
infrastructure
here,
because
you
already
have
merging
this.
Multi
are
Co
mo
where
we
have
access,
but
nobody
published
it
so
far.
So
all
we
just
go
through
this
for
one
get
everything
published.
A
C
A
Just
okay,
so
Java
love
and
support.
Actually,
this
is
mostly
a
cup
of
slides.
We
had
with
a
market.
There
was
forging
its
Walt
one
last
month
with
some
status
update
and
he
actually,
we
had
a
seek
update
in
September,
which
is
always
pretty
much
the
same
status,
but
without
slide.
So
you
can
find
a
meeting
notes
using
list
link,
I
pasted
the
link
to
my
slide
deck
in
meeting
notes,
but
yeah
just
repost
it
a
in
the
chat
as
well.
Just
in
case
somebody
wants
to
take
a
look.
A
A
Okay,
so
major
changes
we
had
since
September
27th,
so
the
first
one
is
Jeb,
2011,
sorry
211,
so,
firstly,
we
integrated
some
changes
for
scope
of
work
before
that
it
was
quite
unclear
and
in
cost
some
questions
in
the
previous
discussions.
So
now
we
explicitly
have
scope
of
changes
here.
We
say
that
we
do
a
bunch
of
stuff,
but
also
we
don't
do
some
needs
like
JT,
6,
evergreen
drinks,
runner.
Also,
we
don't
touch
Gradle
flow.
A
We
don't
touch
Windows
installers
because
alex
is
it
a
work
on
demand
parallel
and
there
is
no
sense
to
touch
them,
and
probably
most
important
thing
is
that
we
agreed
to
exclude
alpine
and
slim
packaging
from
the
scope,
because
there
is
no
upstream
images.
So
it's
unfortunate
but
I
believe
that
we
should
go
without
it
for
now
and
it
can
be
edited
later
at
any
moment.
So
this
is
the
scope
change
wheels.
A
I
also
split
the
plan
a
bit.
So
now
there
is
preview
availability
phase.
It
wasn't
a
way
before
so.
Currently,
if
you
take
a
look
at
the
plan,
the
risks
rollout
plan-
and
there
are
several
stories.
So
it's
already
done.
Experimental
availability
from
the
feature
branch,
and
now
we
have
preview
really
between
weeklies,
then
gene
week
and
J,
a
and
LCS,
so
we
have
epochs
for
which
story,
and
these
epochs
always
reflect
at
the
current
state.
A
A
What
has
gone
next
actually
I
would
be
really
interested
to
approve
this
job
in
August,
I
asked
for
the
feedback,
so
actually
I'm
still
looking
for
feedback.
So
if
anybody
is
interested,
please
take
a
look
at
this
jerk
and
please
comment
on
the
platform
Sigmund,
at
least.
If
you
have
any
comments
or
if
you
still
want
to
review
that,
so
I
want
to
go
forward
and
maybe
a
subject
in
the
beginning
of
the
next
week.
A
Yes,
mm-hmm
yeah,
there
are
still
some
glitches.
Like
you
know,
GT
ki-10
mentions
I
still
failed
to
clean
up
everything,
but
him.
So
if
you
have
any
feedback,
please
let
me
know
by
the
end
to
the
next
week
by
the
beginning
of
the
next
week.
I
need
a
Java
level
process.
So
currently
we
here,
we
have
all
the
things
available
for
preview,
but
it
comes
from
the
each
branch
and
we
need
to
do
some
changes
before
it
becomes
public.
So
what
changed
over
last
month's?
A
Firstly,
we've
had
hog
face
and
DevOps
will
change
both
conferences
in
both
the
United
States
and
news,
and
we
have
got
a
bunch
of
contributors
working
there
in
order
to
get
it
over
the
fence.
If
I
missed
somebody-
sorry
about
that,
but
yet
generally
we
have
some
patches
in
documentation.
We
need
testing
creative
or
packaging,
and
the
biggest
thing
is
actually
all
functional
patches
already
available
in
Jeng
this
weekend.
So
we
have
integrated
all
changes.
Being
you
about
accept
changes
which
really
live,
but
at
the
postponed
till
dig'
like
rejects,
be
abundant
and
yeah.
A
We
are
ready
to
place
it
on
the
preview.
One
of
the
main
issues
we'll
have
miss
preview
is
pipeline
support
release
to
enable
pipeline.
So,
unfortunately,
now
in
order
to
front
pipeline,
you
need
to
use
an
incremental
version
of
a
pipeline
support
plug-in.
So
if
you
just
installed
vanilla,
Jenkins
and
download
plugins
Jenkins
won't
work
on
g11
for
pipeline
at
all,
and
we
need
to
do
something
about
that.
Currently,
we
are
waiting
for
park
alignment.
A
nurse
provide
some
guidance.
A
Yeah
I'll
try
to
revisit
this
topic
by
the
end
of
the
next
week,
so
that
we
have
a
plan
how
to
proceed
then
docket
packaging.
So
there
are
some
good
news
about
that.
So
agents
packaging
is
fully
done.
So
we
have
all
three
common
types
of
agents
updated.
We
don't
have
agents
for
remote
in
cover
pachi
Kafka,
but
here
I'll
work
with
the
bouton
with
plugins,
making
a
try
to
get
this
image
here
out
of
the
door
as
well.
A
C
They
would
like
to
understand
what's
happening,
but
basically
I
think
this
is
just
docker
hub,
API,
crappiness
issue
or
something
I
I've
seen
that
when
I
was
trying
it
out
locally
a
few
times,
there's
a
401
that
happens
from
time
to
time.
So
I'm
not
sure
how
we're
going
to
do
that.
So
maybe
the
solution
here
is
just
to
enrich
the
script.
That
of
a
given
variant
could
exclude.
You
know
a
start
from
a
given
given
core
version
that
would
solve
it
for
now,
but
yeah
good.
A
C
D
C
A
Actually,
the
reason
thought
years
should
even
work,
so
we
didn't
back
for
some
patches
from
recent
versions,
but
it
should
be
able
to
start
the
execution,
etc.
Our
main
problem
with
the
current
deployment
is
that
some
people
may
think
that
it's
a
J
release.
So
me
being
exactly
that's
like
that's
my
concerns
in
it.
Maybe
you
should
do
something
about
it.
D
D
C
A
A
A
Okay,
let's
go
next,
then
blood.
Okay
images
is
still
to
do.
We
have
experimental
images
with
automatic
deployment.
So
if
somebody
wants
to
try
out
lotion,
it's
available
drink
is
for
well
Jenkins
or
roll,
so
blows
on
images.
I
hear
so
the
road
tax
yeah,
probably
yeah
automatically
deployment
is
not
configured
but
yeah.
Anyway,
we
need
to
somehow
promoted
to
common
religious
with
publishing
like
we
do
for
the
rest,
so
we
still
need
to
resolve
that,
but
yeah,
it's
a
much
less
story
than
muster
images.
A
Okay,
I
see
I
flow,
one
of
the
good
news
which
changed
since
the
last
version
that
we
have
jenkees
test
harness
integrated.
So
if
you
go
here,
you
may
see
that
various
pull
requests
builder
and
this
pull
request
builder
effectively.
It
builds
with
DD
11
on
both
linux
and
windows.
So
all
the
patches
integrated
even
for
Jenkins,
test
harness
test
for
other
at
least
for
link,
is
caught.
So
it's
a
good
start
and
for
begins
planning
on
results,
updated.
So
all
critical
changes
are
there.
There
are
some
pitfalls
like.
A
If
you
use
power
mode,
then
you
will
have
to
update
on
your
own,
which
may
be
a
problem
and
it
probably
will
need
some
developer
guidelines,
but
at
least
we're
more
always
good
with
the
core
and
Java
learn.
Support
intubation
in
branch
currently
looks
like
that.
So
we,
actually
they
everything
except
dockerfile,
were
change,
was
integrated,
so
branch
is
totally
aligned
which
is
cool
for
us
and
it's
still
an
open
question.
How
we
deliver
experimental
questions
after
the
mesh?
A
Probably
we
should
keep
Java
11
supported
range
for
now,
or
probably
we
should
just
decorate
it
and
somehow
good
dockerfile
build
strong
and
commit
basis.
So
it's
open
question,
but
it
generally
will
change
test
harness,
be
a
good
acceptance
test,
harness
that
our
pull
request
from
Oliver
gonzo
genuinely.
We
need
to
send
cup
whiskey.
Man
agree
how
we
go
forward
and
for
PCT
the
results
going
work
by
our
enemy.
So
we
got
a
pull
request
to
enable
a
genome
part
test,
a
two
piece:
Java
11.
A
By
the
way,
if
somebody
asks
saying
I
think
in
the
church,
I
do
not
see
it
well
presented.
So
just
raise
your
hand
interrupt
me
and
ask
okay
regarding
quickly,
so
we
still
have
to
do
a
lot
of
testing
so
for
preview
availability.
We
just
prepare
test
frameworks
and
clean
up
our
known
issues.
Then
we
also
have
to
open
concerns.
We
need
to
resolve
before
we
get
into
G
V
clear,
so,
firstly,
its
jugs
B
packaging,
which
we
haven't
addressed
yet
so
the
current
state.
A
When
you
want
to
run
this
job
11.
Actually
you
can,
but
you
need
to
download
some
charge,
libraries
and
then
pass
this
command
line.
So
out-of-the-box
experience
for
war
files
is
far
from
being
perfect
and
it's
something
we
need
to
consider
before
they
weekly
releases
me.
There
somehow
fix
that
or
document
eight,
but
here
it's
to
be
discussed
and
we
need
to
resolve
that
and
Java
Web
Start.
There
is
pull
request
from
Mark
Waid,
so
the
story
behind
that
the
Java
Web
Start
is
that
removed
from
GDK
11
at
all.
So
we
need
war.
A
Now,
users,
that
start
agent
buttons
do
not
longer
work
in
Java
11.
So
there
is
a
pull
request
from
mark
which
should
fix
that
and
if
somebody
is
around,
reviews
will
be
appreciated,
because
earlier
we
merge
that
will
be
fine
with
it.
So
there
is
no
need
to
postpone
it
before
the
week
is
here.
The
politic
was
built,
failed,
but
a
belief.
It's
not
related,
or
maybe
it's
related
sure
I.
D
A
Okay,
it
would
be
great,
so
I
believe
this.
The
only
blockers,
if
you
see
more
blockers-
please
let
us
know
so
we
have
one
major
question-
is
about
plugins
which
are
going
to
break
because
we
don't
know
which
plugins
are
going
to
break.
Probably
many
and
the
may
rely
on
the
preview
motor
and
don't
know
incoming
testing
to
get
that,
so
there
is
still
a
bunch
of
plugins
which
are
likely
to
fail.
A
For
example,
we
know
that
version
columned
plug-in
has
issues
with
visualization
and
there
is
a
ticket
somewhere
most
likely
jacoco
plugin
won't
work
with
java
11.
I
still
need
to
run
PCT
because
jacoco
plugin
includes
power
mock
tests,
so
it
just
fails
on
java
11
out
of
the
box.
Until
I
update
that
but
yeah
there
are
problems
there
and
most
likely
will
have
other
issues
we
haven't
discovered.
Yet
so
some
plugins
like
Minotaur
and
you
already
fixed
but
yeah,
there
is
probably
a
long
tail
of
plugins
which
are
going
to
be
impacted
a
bit.
A
A
C
C
A
A
Yes,
oh
it's
here,
so
its
announcement,
blog
post,
integrated
and
ranked
score.
We
didn't
do
preview
availability
there.
Probably
we
should
have
done
that,
but
yeah.
So
there
is
a
blog
post
which
describes
how
to
test
it,
how
to
approach
that,
how
to
run
it
and
how
to
update
plugins,
etc
in
order
to
make
it
atom
compatible.
So
I
believe
it's
something
we
need
to
do
for
the
preview
announcement
so
that
we
start
again.
A
So
if
somebody
is
interested
to
be
part
of
the
team,
just
join
it
on
github,
so
we
use
this
team
now
to
do
code
reviews,
but
he
believe
that
there
will
be
a
kind
of
entity
for
Radian
coefficients
as
well,
so
they
will
be
maintained,
esteem
which
we'll
be
doing
3
each
of
issues,
and
we
will
launch
this
team
in
parallel,
this
preview
availability
announcement
and
another
part
which
we
are
going
to
have.
They
will
be
week
page
to
track
known
Java,
Levanon
compatibilities
again.
A
Similarly,
to
what
we've
heard
is
jab
200,
the
change
fist
Java
will
be
a
bit
better
for
us,
because
not
everybody
will
hope
in
Java
11
immediately
and
we
will
still
have
downplayed
to
Java
8
as
a
resolution,
but
I
believe.
The
tracking
changes
like
on
this
page
is
something
we
need
to
do
so.
The
final
format
is
to
be
published,
but
here
we
need
this
page
before
the
preview
availability.
A
Okay,
so
yeah
I'll
just
finish
of
this
thing
and
then
we
can
pass
it
with
other
topics,
so
post
G
what
we
need
to
do
actually
job-relevant
maintenance,
as
I
said,
Java
11
support
team,
the
currency
of
resumes
that
we
maintain
it
at
least
for
two
months
before
they
really
built
in
LCS
and
know
this
dope
thing
doesn't
count.
Is
this
so
it's
a
minimum
April
2008
in
according
to
the
current
one,
what
southern
thinkin
and
probably
a
bit
later?
So,
let's
see
how
it
works.
A
Then
there
will
be
a
lot
of
technical
depth
claim
knobs.
So
there
is
a
ticket
with
a
bunch
of
key
codes,
probably
means
some
pagination
in
JIRA
soon,
but
they
still.
There
is
a
lot
of
stuff
to
do
and
you
have
an
open
question
about
sub-project
packaging,
so
jinx
evergreen,
jinkies
file,
runner,
Jenkins
X.
All
of
them
may
need
some
packaging.
So
it's
an
open
question
and
discussion.
The.
If
you
are
part
of
these
sub
projects,
please
feel
free
to
join
the
discussion
and
to
coordinate
releases
with
us.
A
So
far,
it's
not
a
part
of
the
job
but
yeah.
Obviously,
we
all
cut
well
cut
it.
Maybe
everything-
and
there
is
also
early
access
for
Java
12,
which
is
already
available,
and
probably
we
need
to
start
setting
up
some
testing,
because
Jenks
is
a
part
of
quality
outreach
and
we
expect
to
provide
feedback
about
the
testing
statuses.
A
Okay,
so
does
anybody
want
to
contribute
on
this
story?
If,
yes,
I
can
describe
how
if
no
stay
tuned
for
the
blog
post,
because
we
are
going
to
describe
it
anyway,
okay,
but
yeah
generally,
the
restraining
is
Java
ten
and
eleven
blog
posts,
so
you
just
run
and
provide
any
feedback.
Any
issues
you
heat,
any
complexity
is
what
we
are
looking
for,
so
any
feedback
will
be
really
appreciated.
Of
course
you
can
test
your
plugins
projects
and
just
take
any
improvements
from
the
list.
If
you
want
so
I
believe,
that's
it.
A
A
D
A
A
A
Yeah.
Let's
see
so
it's
a
blocker,
but
please
don't
feel
that
you're
on
the
hook
to
deliver
that.
So
if
you
have
no
time
and
cetera
just
let
us
know
so,
maybe
we
will
be
able
to
handle
it
as
a
personal
chef,
javelin
support
team.
Unless
you
plan
to
join
mark
so
you're
more
than
welcome
to
join
by
the
way
and.
D
C
Indian
general,
if
you're
looking
for
the
team's,
you
know
just
open
the
GDI
org
and
meet
hub
and
then
click
teams
and
you
should
be
able
to
find
many.
Many
teams
and
public
ones
and
I
think
that
one
is
very
public.
So
you
should
be
able
then
to
click
on
the
recurse
I.
Think
put,
it
is
like
quick
question
or
something
and.
A
C
A
C
A
C
Anyway,
so
I
adjust
for
for
people
watching
I
did
that,
but
only
in
read
mode,
so
it
just
had
a
little
weird
trick,
because,
anyway,
you
will
resend
open
source
projects
or
window
doesn't
make
it
as
a
big
sense.
But
it's
the
way
you
can
enable
people
to
get
we
requested
with
you'd
reduce
basically,
okay.
A
C
A
Okay,
so
I
believe
that's
what
I
wanted
to
talk
about
Java
Levin.
If
there
was
no
feedback
again
one
of
the
critical
things
we
need
a
stop
rock
job
in
order
to
proceed.
So
if
you
have
any
feedback
is
provided
a
sock
and
yeah.
The
next
is
Java
11
preview.
So
if
you're
lucky,
maybe
we'll
be
able
to
lend
it
to
even
next
week,
but
it
really
depends
on
pipeline
support,
which
is
not
clear
when
it
happens,
and
the
docker
packaging
and
j4j
11
is
also
something
we
need
to
do.
Yeah.
C
Just
maybe
something
that
I
commented
under
the
trap
that
I
think
makes
sense
for
people
wanting
to
test.
We
should
be
able,
hopefully,
to
provide
docker
ever
drink
its
evergreen
flavor
for
Java
11
soonish,
so
that
people
can
try
it
out
very
easily
and
we
probably
a
nice
way
to
to
contribute
testing
basically
to
the
drinkers
project.
Yeah.
A
Right
so,
if
you're
interested
to
test
that
there
is
a
guideline
running
drinks
with
Java
10
in
Jove
11,
so
now
we
have
a
bunch
of
docker
images
being
produced,
including
latest
GDK,
11
blows
and
JDK
Levin.
All
of
them
go
to
Jenkins
experimental,
so
you
can
try
them
out
and
once
we
fix
the
issues
with
official
release
for
Jenkins
Jenkins
will
bills
available
with
such
labels.
So
yep.
D
A
All
blue
integrates
Jenkins
pipeline
and
blue
channel.
So
the
idea
of
this
image
that
you
can
get
it
drunk
out
of
the
box
and
the
advantage
of
that
is
that
we
can
package
incremental
set
Elise
for
pipeline
plugins.
So
if
you
go
to
Java
11,
you
may
see
that
a
info
against
ext
here
we
install
this
version
so
pipeline
support
incrementals
whatever.
A
A
A
A
Public
announcements
actually,
according
to
Martin,
they
happened
on
this
weekend,
so
we
will
definitely
apply
and
then
not
apply.
We
need
project
ideas,
so
if
you
have
anything
in
mind
and
if
you're
interested
to
mentor
jisub
project-
just
let
us
know
there
is
another
chart
for
JSOC
sig.
So
if
somebody
is
interested,
you
can
just
join
this
chat
and
we
can
discuss
your
project
ideas.
So
yeah
is
here
and
yeah.
We
will
try
to
incorporate
this
project
ideas
right
now.
D
A
A
That's
it
in
this
topic
and
yeah.
Probably
the
next
meeting
I
will
think
again,
because
yeah
I
have
at
least
two
project
ideas,
but
they
are
so
far
not
related
to
platform.
Seek
may
be
the
work
of
Windows
service.
Installers
is
actually
related
to
platform.
Seek
so
just
to
give
you
an
idea.
I
want
to
work
a
Windows
service
wrapper
so
that
we
stop
for
doing
these
crazy
things
about
XML
s,
etc
and
probably
switched
something
more
standard
as
GM
a
Lewis
definition,
checkers
I
may
be
only
with
dotnet.