Do you guys have a schedule in place for conference calls to discuss next steps etc?Cheers
Sent from my iPhone
On 31 Jan 2013, at 17:27, Werner Keil <werner.keil@...> wrote:
Looks good, thanks.Btw, regarding portability, just to let you know, the CLDC 8 "Umbrella" Profile started today, and the Spec Lead wishes to plan calls and discussions in weekly intervals, so it looks like they want to catch up on a bit of the lost time there, too (keep in mind, that JSR just like 354 also falls under JCP 2.9, so it'll risk Renewal Ballots if nothing happens like an EDR soon<329.gif>)Whether those efforts take place in OpenJDK or another appropriate place, we should be able to contribute to relevant parts.
Most packages and classes are subsets of Java SE 8, javax.microedition is upgraded from the CLDC 1.1.1 spec:
- java.utilMeaning, a scaled down version of java.util.Currency as an RI for a limited part of the JSR (probably no more than the core-api) plus java.util.Money or a similar value type are perfectly in scope here. The platform and those platform JSRs define demand, if CLDC 8 happens before SE 9, so be it, and we can actually focus on a smaller set first, while fleshing other, heavier parts out for SE 9.Cheers,WernerOn Thu, Jan 31, 2013 at 5:32 PM, Tresch Anatole (KFSC 225) <anatole.tresch@...> wrote:
I have defined the components in JIRA as for me should make sense. Feel free to give feedback. In short I’ve defined the following components:
<image001.gif>build and quality improvement
<image001.gif>RI: Basic RI
<image001.gif>RI: JDK Adaptations
<image001.gif>spec: specification (Lead: atsticks)
As you see, currently I only am the owner of the specification document. So everybody that wants to take over a basic default component responsibility can ask for ;-)
Afterwards we have to define also the features and requirements and assign them to the components. Any support in this area is quite welcome!
By the way: the ongoing renewal ballot for this JSR looks good so far. This should allow us to continue effectively with our work.
CREDIT SUISSE AG
Information Technology | Java Core Framework & Support, KSXK 23
Zollstrasse 20/36 | 8070 Zürich | Switzerland
Phone +41 44 334 03 89
JSR 347, "Data Grid" which also is among the few JSRs with a Twitter handle btw., released this call on Google Groups: https://groups.google.com/forum/?fromgroups=#!topic/jsr347/D5-KATaXrzI
For all those who are official EG Members of JSR 354 (making it easier with IP and all that stuff, everyone may contribute, but officially only EG Members are supposed to add it to the Spec<image002.gif>) something similar may be a good idea here, too.
@Anatole, or anybody (also non-EG members) on the list, please suggest features or components. Also good to transfer that into JIRA as soon as the list of features is known and accepted.
The modules that currently exist could be a starting point:
- Core + Singleton (I would say semantically close enough)
- TCK (tbd, there is no module yet)
There may of course be logical areas like
feel free to suggest something you think is important enough to form a "feature" or "component" right now.
|Tresch Anatole (KFSC 225)||01/31/2013|
[JSR-354] Re: Components