►
From YouTube: Jakarta EE Community Call | 2019-12-11
Description
Jakarta EE Community Calls are intended for the wide Jakarta EE community providing progress on the releases and activities related to Jakarta EE.
Agenda:
- Jakarta EE 9 release plan (Steve Milidge)
- Progress on Jakartifying of the specification documents (Ivar Grimstad)
- Jakarta EE 2020 Program Plan and budget, Steering Committee chair (Will Lyons)
A
A
B
Okay,
you
see
that
okay,
yes,
thank
you
right.
So
I'm
gonna
get
an
update
of
Ducati
9,
where
we
are
in
our
planning
so
I'm.
Obviously,
the
founder
of
payara
I'm.
Also
one
of
the
project
leads
on
the
car
tree
platform
and
village.
Jakarta
ee9
release
I'm
what
we're
calling
a
co-pilot
with
with
Kevin
Sutter
from
IBM,
so
we're
currently
in
the
phase
of
putting
together
and
the
plan
that
will
go
in
for
review.
B
Well,
the
steering
committee
in
the
specification
committee
just
to
go
through
a
bit
of
the
process,
so
I
did
a
similar
update
a
month
ago,
when
this
is
really
going
to
come.
Follow
on
from
that
and
has
some
more
decisions
have
been
made
since
then,
just
to
recap
a
little
bit
of
where
we
are
so
Carter
e8
was
out
in
September,
and
that
was
the
compatible
bility
release,
so
that
covers
that
was
based
in
the
Java
X
namespace.
B
And
the
big
thing
is
that
we,
we
have
open
specifications
that
are
managed
through
the
Eclipse
Foundation
specification
process
and
we
have
an
open
source,
TCK
and
an
open
source
development
process,
and
so
that,
but
that
completed
the
evolution
of
specifications,
the
API
use
from
from
the
JCP
and
now
we're
in
the
phase
of
creating
Thakkar
29
so
which
car
tree
9
we're
sort
of
targeting.
This
is
a
tooling
release
and
a
little
bit
about
what
we
mean
by
that.
But
it's
gonna
be
a
limited
scope
in
that.
B
What
we're
going
to
do
is
change
the
namespace
to
the
Jakarta
namespace
and
we're
gonna
deprecated
and
remove
some
api's
and
we've
got
some
slides
on
which
IP
eyes
are
remaining,
which
ones
are
you
deprecating
and
which
ones
we're
adding
and
also
we're.
Gonna
update
the
base
JDK
and
in
parallel
to
a
large
extent,
to
that.
We
can
also
start
thinking
about
Carter
e
10
so
check
our
tree.
B
So
the
reason
we
stopped
saying
it's
a
tooling
releases
that
we're
not
adding
any
specifications
other
than
some
have
been
pruned
from
Jakarta
sorry
from
Java
SE
8
we're
not
really
looking
to
make
any
breaking
changes,
so
not
introducing
any
new
api's
and
no
breaking
changes
other
than
the
namespace.
Obviously,
and
maybe
some
upward
compatible
changes,
whether
small,
but
predominantly
it's
the
move
from
davic
stooge
Akata
that
we'll
be
completing
in
the
api
package
names.
B
So
what
we
wanted
to
do
is
create
a
base
for
people
to
sort
of
target
when
dealing
with
the
names
race
change,
so
Shekhar
tree
9.
Release
will
really
give
time
for
IDs
to
to
build
some
to
willing
to
help
move
applications
that
target
the
old
to
car,
3:8
tovex
namespace
to
migrate
and
target
the
new
car
to
namespace.
B
Similarly,
it
gives
us
an
opportunity,
for
you
know:
vendors,
like
payara,
to
explore
how
we
sort
of
also
help
end
users
and
developers
move
this
names
make,
so
we
could
cross
the
namespaces
and
make
their
transition
as
smooth
as
possible.
So
we
can
look
at
explore
and
explore
compatibility
layers.
We
can
collaborate
with
with
other
vendors
on
how
we
can
build
compatibility
layers
to
support
old
applications
running
on
Shikari
9
and
then
finally
also
end
users
and
developers
out
there.
They
can.
B
B
So
if
we've
been
on
the
previous
call
there,
we
were
still
in
there
in
a
flux
and
what
is
the
scope
which
Carter
e9,
which
API
so
in
which
API
sat
out
and
there's
been
a
lot
of
chatter
on
the
platform
mailing
lists
and
based
on
the
call
this
Tuesday
we're
in
a
position
where
we
believe
that
this
is
all
agreed.
It's
not
going
to
be
put
into
the
release
plan
and
still
gotta
be
signed
off,
but
most
of
the
discussions
of
now
being
settled.
B
So
what
we're
going
to
do
is
proven
a
number
of
legacy.
Api's
they'll
be
removed
completely
from
takara
tree
9,
we
know
to
add
in
some
api's
might
used
to
be
in
Java,
SE
8,
but
I'm
no
longer
there,
so
they
were
pruned
from
from
se
and
we're
going
to
add
those
in
as
optional
api's
in
to
Tecate,
9
and
again,
I
got
more
slides
on
this.
B
B
If
we'd
left
the
baseline
at
SC
8,
then
obviously
they
would
exist
in
there
in
Java
SE
and
in
Jakarta
EE,
which
could
be
confusing
so
we're
taking
the
opportunity
by
bringing
these
in
to
also
operate
the
minimum
for
compatibility.
Saying
that,
though,
we're
going
to
require
that
API
jars
are
released,
so
they're
suitable
for
use
with
JDK
individually.
So
what
that
means
is
that
they
will
be
compiled
using
java
SE
a
class
file
format,
so
we're
not
going
to
compile
them
into
Java
SE
11
tasks,
file
format.
B
As
we
know,
the
API
jars
are
often
used
widely
outside
then
in
the
general
ecosystem,
and
there's
no
need
given
we're
not
allowing
any
API
changes
of
any
significance
to
not
do
this,
because
no
one
is
going
to
be
pushing
to
put
seu
leavening.
Only
API
is
into
the
API
signatures,
so
move
on
to
actually
in
details
of
each
specification.
B
B
You
decided
not
to
prune
it
because
it's
quite
complex
from
and
they
would
have
delayed
the
project
due
to
the
mix
and
match
of
namespaces
and
exception
hierarchies
and
things
between
the
current
age,
IV
and
the
older
egb.
So
doing
that
unpicking
work
was
decided
was
too
complicated
and
also
pruning.
The
old
Enterprise
web
services,
which
is
the
web
service
that
predates
the
XML
web
services,
objects,
WSS,
was
and.
B
So,
even
though,
to
get
compatibility,
something
that
payara
doesn't
need
to
implement
these
api's.
When
we
actually
release
the
specification,
then
the
implementation
that
goes
along
with
the
specification
release
has
to
support
all
these.
So
there's
a
burden
on
the
specification
team
and
the
compatible
implementation
to
support
optional
api's,
but
at
the
same
time
we
still
meet
our
goals,
which
is
to
sort
reduce
the
footprint
of
Tecate.
Eight
storage.
Cart,
we
nine
four
new
vendors,
so
new
vendors
wouldn't
need
to
support
any
of
these
optional
API.
B
Most
of
them
will
be
optional,
so
did
Carter
activation
will
be
added
into
Carter,
II
9
supports
Java
mail
and
that
so
that
will
be
Monday
tree
and
then
Java
Jack's
B,
as
well
as
Jakarta
X,
more
binding
or
jax-ws,
as
well
as
which
is
Jakarta
X
my
web
services
and
there
are
other
associated
web
services.
Api
is
and
specifications.
Well
now
all
the
added
into
two
Carter
e9
has
optional
api's
and
in
addition
to
that,
we're
going
to
move
all
these
five
api's
into
the
Jakarta
namespace
that
was
really
driven
by
community
feedback.
B
So
there
was
a
lot
of
community
feedback
that
these
api's
are
still
in
a
lot
of
use
and
they
wanted
to
see
them
move
into
Jakarta
namespace
again
from
a
specification
point
of
view.
It
was,
it
was
a
burden
to
support
these
and
move
them.
However,
because
of
the
community
feedback,
we've
decided
to
take
that
work
on,
and
you
know
bring
them
into
to
Carter
e9,
to
provide
a
solid
basis
to
where
you
know
where
these
api's
have
gone
and
that
they
will
be
available
to
applications
in
run
tags
that
support
them
again.
B
B
B
So
essentially
this
is
a
rough
view
of
what
depends
on
what
so
from
the
first
wave
will
be
the
lowest
level
api's
that
have
the
minimal
dependencies.
So
that
includes
Jakarta
concurrency,
annotations
messaging,
as
with
JMS
and
then
wave
2
again
brings
in
some
other
API.
Is
that,
may
you
know
depend
on
wave
1,
then
we
bring
in
the
big
one,
which
is
Jakarta,
Khan's
context
and
dependency
injections,
weight,
3,
and
then
you
know,
following
on
for
that
further
and
further
higher
and
higher
API
is
that
dependent
on
the
most
lower-level
api's.
B
B
You
know
there's
a
fixed
quantum
of
work
that
needs
to
be
done,
so
we
have
to
pick
a
date
when
that
work
can
be
finished
when
we
move
into
maybe
e
10
11
and
beyond,
and
we
can
follow
a
more
release.
Train
mode
whereby
we'd
be
able
to
you
know,
pick
a
date
for
the
release
and
then
just
pick
up
the
api's
that
are
ready
that
date
and
release
a
platform
that
way,
but
for
a
bit.
If
we
have
to
do
all
this
namespace
change,
so
the
quantum
of
work
is
fairly
fixed.
B
So
when
it
comes
to
API
jars,
we're
going
to
try
and
get
those
out
earlier
than
suggested
from
from
the
wave
diagram.
So
essentially
when
I
say:
artifact
I'm
talking
about
jar
files
really
from
those
people,
so
we
are
going
to
release
our
seesaw
release
candidate
API
jars
as
soon
as
possible
into
maiden
central.
B
You
know,
without
going
through
the
full
spec
process
and
and
everything
so
that
send
essentially
they'll
be
available
for
later
waves
and
to
willing
and
GlassFish
Eclipse
classification,
which
I'm
a
project
lead
of,
can
use
those
jars
early
as
early
as
possible,
and
that
will
speed
up
the
delivery.
So
we
won't,
you
know
we
won't
have
to
release.
B
Individual
specs,
because
obviously
I'm
just
on
the
platform
project,
which
is
an
umbrella.
Each
of
those
can
release
a
final
specification
at
any
time
subject
to
them.
Following
the
Eclipse
specification
process,
another
step
would
be
aiming
to
do
is
once
all
the
API
jars
have
been
released.
We're
intending
to
do
like
a
release
candidate
of
the
full
platform,
so
that
will
include
the
API
jars,
a
compatible
implementation
and
the
TCK,
but
it
won't
have
gone
through
the
full.
You
know
spec
process,
all
the
documents
necessarily
won't
be
ready.
B
Now,
I'll
give
an
opportunity
for
us
to
look
at
to
willing
and
and
make
sure
that
everything's
working
before
we
then
have
a
sort
of
a
window
which
maybe
a
couple
of
months.
Where
we'll
then
do
the
final
release
and
put
the
you
know
final
artifacts
up
into
maven
central
and
they
all
the
specification
documents
etc
and
go
through
the
formal
votes,
an
IP
flow,
etc.
B
So
again,
these
dates
are
gonna,
get
a
bit
more
nailed
down
in
the
next
week
and
we
have
to
give
any
new
projected
date
by
next
Tuesday
I.
Believe
it's
before
Christmas
and
we'll
put
that
into
release
plan
so
that
that's
where
we
are,
we
have
the
scope
nailed
down.
We
have
a
tentative
Porter
that
we're
gonna
release
things
on
and
we
have
a
plan.
In
the
sense
we
have
the
order
of
things
that
are
going
to
happen.
The
only
thing
where's
now
missing
is
the
date.
B
Anybody
can
contribute.
There's
a
lot
of
this
conversations
on
the
platform
dev
mailing
list
on
the
community
list.
We
get
to
a
date.
I'll
just
show
that
we
are
putting
together
a
tracking
on
a
spreadsheet
of
when
api's
can
move
to
the
namespace
and
what
you'll
see
is
actually
most
of
the
waveone
api's
PRS
are
already
done.
Some
of
them
are
already
merged,
actually
doing
the
API
change
itself.
Isn't
it's
not
a
big
deal?
B
Getting
the
implementations
and
the
TCK
will
be
a
bigger
deal,
but
we've
already
making
progress
on
this
and
I
say
many.
The
Piazza
trade
front
already
done
once
we
can
get
those
into
maven
central
as
release
candidate,
then
the
API
changes
can
be
done
on
wave
2
and
then
some
of
the
TCK
work
and
then
follow
on.
Basically,
you
just
need
artifacts.
For
these.
B
B
You
can
raise
issues
and,
like
I,
said
that
probably
at
the
beginning
is
Jakarta.
Attend
itself
can
also
start
progressing
and,
with
you
know,
I'm
Project
Lead
for
concurrency
and
we're
already
creating
issues
for
that
in
a
separate
branches,
and
that
can
work
in
parallel
to
the
API
work.
So
a
lot
of
the
the
namespace
work
is
just
so
boilerplate
type
work,
so
the
innovative
work
and
having
an
imperil
L
so
I
just
want
to
stress
that
as
well.
A
A
Seems
to
be
no
questions
but,
as
we
all
know,
majority
of
people
are
preferring
to
view
the
recording
of
this
this
meeting
so
for
this
is
the
request
for
people
out
there.
If
you
have
questions-
and
you
see
agenda,
please
send
them
to
me
priority
call
if
you
intend
to
look
at
the
recording
and
as
always,
to
give
us
feedback
on
how
useful
these
calls
are.
So
I
guess.
A
C
C
We
need
to
remove
the
references
to
the
JCPS
specifications
and
the
Java
trademarks
of
the
old
adjacent
versions
of
the
documents
and
and
replace
them
with
the
Jakarta
counterparts
and
most
of
the
specifications
just
6:00
this
morning
in
started
on,
and
then
they
are
per
Luke
arrests.
But
these
poor
workers
needs
to
be
kind
of
approved
by
some
committer
on
the
project.
So
I
would
encourage
the
committee
to
a
project
just
check
your
github
repo
and
see.
C
If
there
are
a
poll
requests
from
a
community
remember
because
they
are
not
able
to
merge
it
so
go
in
and
see
if
the
spec
documents
is
and
if
it
isn't
then
check
with
your
project
lead
if
the
certification
has
been
released
because
just
waiting
there
to
become
there
are
a
couple
of
specifications.
I
can't
remember
exactly
which
ones
that
are
the
document
is
released,
but
it
hasn't
been
picked
up
yet.
C
C
You
grab
the
ask
you
look
far
and
and
put
it
in
the
right
director
structure
or
build
it
and
see
that
it
works,
put
it
into
the
master
branch
and
then
start
working
on
it,
and
there
are
some
projects
that
are
almost
done,
like
the
security
and
the
I
took
all
the
rest.
So
look
at
those
delicious.
They
have
where
the
head
checked
place
for
what
you
have
to
do.
C
One
thing
we
should
mention
is
that,
while
we
would
certainly
like
all
the
specifications
to
be
dakota
fide
for
EU
nine,
we
won't
stop
it
if
it
if
they
aren't
so
we're
good
with
going
with
the
boil
of
respects.
As
for
eh,
if
it
kind
of
jeopardize
the
plan,
but
it
would
be
nice
to
have
both
aspects
on
the
same,
so
it
has
to
be
done.
C
A
A
Well,
if
you
wanna
present
the
program
committee
plan
and
the
budget
I'm
sure
everyone
is
familiar,
that
will
is
chairing
our
steering
committee
jacquard,
a
steering
committee
call
and
I'll
not
just
call
but
leading
the
the
the
the
steering
committee
from
the
chairing
the
steering
committee.
Thank
you
anyways
and
turning
over
to
will
welcome,
will.
D
Thank
You
Tanya
hi.
This
is
with
alliance
with
Oracle
and
in
product
management
responsible
for
Jakarta,
EE
and
WebLogic
server,
and
we
thought
I
mean
as
Tommy
says.
I
am
also
chair
of
the
Jakarta
EE
working
group
steering
committee,
and
we
thought
it
might
be
interesting
and
useful
to
share
what
the
steering
committee
is
planning
with
us,
but
to
not
only
evolving
the
jacquard
ee
technology
but
building
the
community
that
develops
the
technology
and
promoting
the
technology
in
the
broader
marketplace
in
order
to
develop
a
healthy
ecosystem
for
Jakarta
II.
D
So
we
thought,
you'd
be
worth
reviewing
the
process
and
our
plan
for
2020
to
build
a
healthy
ecosystem
for
Jakarta
II
and
the
budget.
That's
in
place
to
support
that.
So
that's
what
I
will
be
discussing
and
I'm
gonna
start
with
a
little
bit
of
terminology,
I'm,
not
sure
how
familiar
many
of
you
are
with
a
term
working
group.
D
Payara
is
a
strategic
member
and
you
can
see
IBM
Fujitsu,
Red,
Hat
and
Tommy
tribe
are
also
strategic
members
and
there's
standards
and
definitions
of
what
strategic
members
are.
Typically,
a
strategic
member
regards
the
technology
is
better
prize
Java
technology
or
excuse
me,
Jakarta
GE
technology
is
strategic
to
their
businesses
and
their
vesting
significant
resources.
We
also
participating
members.
We
typically
deliver
products
or
services
which
are
based
on
jacquard
ee
technology.
So
this
is
our
current
membership.
C
D
D
D
In
order
to
help
achieve
those
objectives,
we
have
concluded
the
budgeting
process.
We
have
an
approved
budget
that
was
approved
at
the
Jakari
working
group
steering
committee
meeting
at
the
end
of
November,
and
this.
This
is
a
collaborative
process
involving
active
discussion
over
several
weeks
and
so
I'll
describe
a
little
bit
of
what
we
defined.
First
week,
as
I
mentioned,
we
defined
some
strategic
goals
of
critical
importance.
Is
the
next
two
card
EEE
release,
and
you
just
heard
from
Steve
about
that.
We
need
to
get
a
e9
out.
We
know
that
that's
a
top
priority.
D
D
We
also
want
to
grow
the
developer
community,
not
only
developers
for
contributing
to
the
evolution
of
the
technology
itself,
but
developers
who
are
consumers
and
build
applications
using
the
technology.
We
want
to
create
programs
that
are
helpful
to
developers
a
one
area
focus,
and
this
is
something
that
Steve
alluded
to
in
the
Riccardi
nine
plan
is
we
want
to
drive
a
plan
for
building
out
tooling
support
for
the
technology
we're
delivering.
D
We
want
to
grow
the
working
group
membership
as
we
engage
with
more
members
and
vendors
who
have
interests
in
this
area.
This
has
helped
strengthen
the
community
and
it
helps
strengthen
the
funding
of
the
working
group
which
can
drive
community
success.
So
that's
an
important
goal
for
us
and
then
just
very
broadly.
We
want
to
invest
in
growing
awareness
of
Jakarta
EE
technology
and
the
brand
itself
in
the
community
and
build
engagement
within
the
community.
D
So
these
were
the
high-level
strategic
goals
we
discussed
within
the
steering
committee,
which
sets
the
strategic
direction
for
Jakarta
EE
and
hurry
to
these
strategic
goals.
We
set
finer-grained
objectives
for
what
we
want
to
achieve,
and
a
high
level
plan
for
targeting
those
objectives
in
each
one
of
the
areas
I
just
mentioned
so
I
won't
go.
I,
won't
agree
through
all
the
individual
slides,
but
in
terms
of
the
e9
we
want
to
deliver
a
new
release
that
accomplishes.
You
know
the
things
which
Steve
described
in
more
detail.
D
So
these
are
a
more
detailed
description
of
activities
that
we
will
undertake
to
achieve
our
strategic
goals,
and
that
was
a
set
of
activities
at
the
steering
group
agreed
to,
and
then
we
took
a
look
at
our
budget
and
allocated
it
to
specific
funds.
Specific
areas
our
budget
is
listed
here
you
can
see
in
the
2020
column
is
our
total
revenues.
D
So
these
are
the
revenues
of
the
working
group
from
member
contributions
and
that
total
is
1.3
million
dollars,
and
so
that's
the
revenue
and
the
expenses
are
the
way
that
funding
is
allocated
and
so
a
significant
portion
that
is
allocated
to
overall
management
of
the
cardi
program
itself.
Organizing
events
like
this.
D
We
have
a
significant
amount
of
infrastructure
which
requires
various
DevOps
tools
and
maintenance
of
those
tools
and
maintenance
of
the
overall
dev
infrastructure.
So
we're
allocating
resources
to
that
and
we're
also
allocating
resources
to
actually
managing
the
specification
process.
For
those
of
you
who
have
been
involved
in
actually
creating
the
initial
jacquard
ee8
specification.
D
In
addition,
we
are
funding
a
number
of
programs.
The
most
significant
is
marketing
which
I'll
come
back
to
in
a
moment,
but
we
funded
that
$285,000
for
marketing
activities,
marketing
programs
in
the
coming
year.
The
steering
committee
has
also
reserved
a
contingency
fund.
In
the
event,
we
need
rapid,
for
you,
know,
purchase
of
specific
tools
or
increasing
increasing
licensees
fees
in
certain
areas
or
other
contingencies,
whatever
might
be
required
to
actually
facilitate
our
primary
strategic
objectives,
including
things
like
delivering
ee9.
D
So
we've
held
back
some
funding
to
enable
us
to
respond
to
events
and
needs,
as
they
occur,
there's
also
legal
fee.
Contingency
there's
complicated
patents,
IP
licensing
flows
involved
in
in
a
specification
process
in
in
the
technology
area,
we're
managing
and
we
want
to
fund
a
certain
illegal
fees
to
deal
with
getting
legal
analysis.
Legal
opinions
on
various
issues
as
I
come
up.
You
think
were
reasonably
covered
from
the
perspective
of
the
into
the
hardware
infrastructure
that
is
set
up
for
our
builds
and
repositories
and
so
on.
D
So
the
total
amount
of
spend
on
those
programs
is
about
three
hundred
eighty
eight
thousand
dollars
in
addition
to
the
headcount
spending
at
the
Eclipse
Foundation
of
760
K,
and
that
program
spent
the
Eclipse
Foundation
generally
invest
a
significant
amount
of
time
on
administration
of
all
of
the
work
surrounding
Jakarta
ie.
Providing
advise
meeting
with
analysts.
D
In
defining
a
process
that
orchestrates
work
among
all
the
vendors
involved
here,
and
so
this
allocation,
as
general
administrative
allocation
is
intended
to
cover
the
administrative
expenses
that
essentially
get
applied
to
this
working
group
by
the
Eclipse
Foundation
and
those
expenses
total
up
to
1.3
million,
which
equals
our
incoming
revenues.
So
these
are
the
general
areas
in
which
the
working
group
is
investing.
B
D
2020
I
mentioned
the
marketing
budget.
The
marketing
committee,
which
is
one
of
the
working
committees
in
the
Jakarta
working
group,
has
analyzed
you
know
the
requirements
and
that
are
associated
with
meeting
the
strategic
goals
of
the
working
group
and
has
translated
each
of
the
strategic
goals
for
the
foundation
into
corresponding
goals
from
a
marketing
perspective
and
the
marketing
budget
that
we've
allocated
to
the
marketing
committee
will
be
directed
towards
marketing
activities
that
are
in
support
of
the
major
strategic
goals
that
the
working
group
has
established.