User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
Oracle contributed them long ago. The hold up has been on the
Eclipse side with getting all the intellectual property rights from
the many contributors to the specs so that they could be made
available under the Eclipse license. Fortunately, Eclipse says
they've made great progress and will provide a status update very
soon.
Guillermo González de Agüero wrote on
9/29/19 11:24 AM:
So that means Oracle was finally able to donate
them all?
Eclipse says most specification
documents will be available "soon".
Christian Kaltepoth wrote on 9/28/19 7:54 AM:
I just sent a mail to the community and
WG lists and asked for an update regarding the status
of the contributions. Let's see if there are any news
about this topic.
I personally don't
think that the jakarta package rename must
be done with a major release. However, we
should wait for a Specification Committee
decision regarding this.
However, I'm not sure
if it makes sense target releases for
specific quarters as we still don't have
the specification documents. Theses are
required for the releases and it is not
under our control when we get them.
They
did not ask for the roadmap
independently. I was asked to give a
talk on October 23, and they know
what my "usual" talk is about - the
JAX-RS roadmap.
-Markus
Von:jaxrs-dev-bounces@xxxxxxxxxxx
[mailto:jaxrs-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Santiago
Pericas-Geertsen Gesendet: Freitag, 27.
September 2019 19:31 An: jaxrs developer
discussions Betreff: Re: [jaxrs-dev]
Revisiting Roadmap
I
can only speak for
myself since we
haven't discussed
versioning of the
projects, but I
would be very
surprised if the PMC
has any opinion
regarding how the
individual projects
are versioned. The
Jakarta EE
Specification
committee may have
for the
specification
projects, but none
that I am aware of
other than usual
practices.
For
Jakarta Faces
the first plan
we had was to
call the
version with
the package
change (and
only the
package
change) "2.9".
The
current
version is
2.3, so we
hoped the jump
from 2.3 to
2.9 would
signify it
clearly enough
that 2.9 is a
big
incompatible
change. But
indeed, some
Faces
committers
have suggested
too to make
3.0 the
package change
version, and
then 4.0 the
big new
version after
that.
Maybe
Jakarta REST
can indeed do
something
similar.
I strongly believe that the switch to the
jakarta.*
namespace should
result in a new
major version of
the spec, e.g.,
Jakarta RESTful
Web Services 3.0.
It's a big
incompatible
change that
shouldn't be
slipped in in a
minor release.
Santiago
Pericas-Geertsen wrote on 9/25/19 10:05 AM:
Hi
All,
Now
that Jakarta
EE 8 is
officially
out, we should
revisit our
existing
roadmap. I
updated it
with some
tentative
dates for the
versions that
we had
planned.
