users@jpa-spec.java.net

[jpa-spec users] [jsr338-experts] Re: JPA.next process

From: Werner Keil <werner.keil_at_gmail.com>
Date: Wed, 3 Jun 2015 11:59:29 +0200

Hi Oliver/all,

Interesting point, thanks for the initiative (a more coordinated effort by
the PMO currently does not seem a priority under JCP.next, but several
other mostly Oracle lead JSRs did that on GitHub, plus every notable JSR
that's either active right now or just finished also use GitHub as their
main repositories)

While we saw some people also actively involved in the JCP (even former
Spec Leads) leave Pivotal recently is it safe to assume you have no such
plans in the forseable future?;-)

There is no JSR proposal for JPA under the Java EE 8 Umbrella, and while
still possible, I guess anything other than a MR would have to start soon
to still make it there.

Kind Regards,

Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead |
Eclipse UOMo Lead, Babel Language Champion | Apache Committer | Advisory
Board Member, Java Track Chair, DWX '15

Twitter @wernerkeil | @UnitAPI | @JSR354 | @JSR377 | @AgoravaProj | #DeviceMap
| #DevOps | #EclipseUOMo
Skype werner.keil | Google+ gplus.to/wernerkeil

[image: --]

Werner Keil
[image: https://]about.me/wernerkeil
<https://about.me/wernerkeil?promo=email_sig>


On Wed, Jun 3, 2015 at 11:32 AM, Oliver Gierke <ogierke_at_pivotal.io> wrote:

> Hi all,
>
> independently of the scope of the upcoming JPA specification I wondered
> what you're plans are about aligning the specification process of that
> upcoming version with a more state-of-the art style.
>
> I've seen the CDI guys are leading by quite a bit compared to us (spec in
> Asciidoc, public repo for spec and API, public repo for TCK) and I wonder
> whether there might be any good reason for the next JPA spec not to follow
> that model. I've reserved the "jpa-spec" organization name on GitHub to
> avoid anyone is hijacking it as this email will become public. Happy to
> hand over the organization to anyone who wants to be in charge.
>
> As it apparently has been decided that the scope is rather small for this
> iteration [0] it might be a chance to improve on meta things.
>
> Cheers,
> Ollie
>
> [0]
> https://java.net/projects/jpa-spec/lists/jsr338-experts/archive/2014-08/message/4
> [1] https://github.com/jpa-spec
>
> --
> /**
> * @author Oliver Gierke - Senior Software Engineer
> *
> * @param email ogierke_at_pivotal.io
> * @param phone +49-151-50465477
> * @param fax +49-351-418898439
> * @param skype einsdreizehn
> * @see http://www.olivergierke.de
> */
>
>