search

apastsya / jsr358

0 stars 0 forks source link

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 #1

Open apastsya opened 13 years ago

apastsya commented 13 years ago

Jira issue originally created by user pcurran:

apastsya commented 13 years ago
apastsya commented 13 years ago

Comment created by weirj:

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

apastsya commented 13 years ago

Comment created by pcurran:

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

apastsya commented 12 years ago

Comment created by pcurran:

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.)