[JSR358-13] Oracle should encourage other Spec Leads of in-flight JSRs to join them in voluntarily adopting the new Process once the JSR is finalized Created: 01/Jul/11  Updated: 08/Apr/15

Status: Open
Project: jsr358
Component/s: Implementation
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: pcurran Assignee: pcurran
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is duplicated by JCPNEXT4-15 Oracle should encourage other Spec Le... Closed

Comment by weirj [ 06/Jul/11 ]

I believe it would be good to do this at the earliest possible opportunity, and embrace the mantra of a more active and involved process. Asking the Spec leads of the inflight JSR's if they would have any objections in principle to moving to the new process once it is defined, may tease out any unlerlying concerns or issues that people may have for the WG to discuss

Comment by pcurran [ 20/Jul/11 ]

Just FYI, I'm working this within Oracle, and we do hope to be able to make a public statement relatively soon.

Comment by pcurran [ 06/Jul/12 ]

This is still in progress. The PMO is actively encouraging all in-flight JSRs to upgrade to 2.8 when they submit a new draft or a Maintenance proposal. As for Oracle's JSRs, some have already converted and others will soon.

I'll keep this issue open until it's clear that we're done (or almost done.)

Even though this is not strictly-speaking a JSR 358 issue, I'm moving it over to that project so it won't get lost here. (Otherwise it would be the only remaining open issue for this now-completed project.)

Generated at Sat Feb 25 18:20:28 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.