On 19.02.2015 15:50, Mario Torre wrote:
Ok, so let it not be a JEP. Let it not be a separate patch set for
review. What other options are there?
Like I said, you start by finding a suitable home for the code in an
OpenJDK Project.
Once you have that, you can begin the process to bring the necessary
code over into that new home.
Once you have done that, you can begin to adjust the code to whichever
JDK Project you're targeting. If you're targeting JDK 9, for example,
that means setting up a JDK 9 clone, adjusting the code accordingly, etc.
Once you have done that, you can start to separate the changes into
different buckets - for example, bug fixes or simple performance
enhancements might be easier to review and accept upstream than
algorithmic improvements - I'd guess.
Once you have done that, your next goal should be to find the simplest
possible change that you can get upstream from that Project, and then
try to make it move upstream to familiarize yourself with the process
and to socialize the planned changes.
It can be helpful to order the changes you want to make from simplest
and smallest to largest, and then proceed accordingly, in order to get
an idea of how much work it is to get a change of what complexity
socialized, reviewed and integrated. [0]
Once you have done that, you might find that there is enough left over
to draft a JEP, or two. Excellent, then go and draft a JEP, or two. At
that point you will have a much better idea of what it takes whom to get
your desired changes in what form into what release than when you
started out. In addition, the reviewers will have a much better idea
what to expect and plan for.
cheers,
dalibor topic
[0] A neat post from a Linux kernel maintainer on the need to spend time
to explore and socialize contributions in order to avoid rejection is
available at https://paulmck.livejournal.com/38591.html
--
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961>
ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Geschäftsführer: Jürgen Kunz
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher
<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment
