On what issues could I help clean up for JDK 9

Mon Dec 5 20:09:42 UTC 2016

Oops got cut off, I meant to say thanks for the Roadmap details!

Cheers,
Martijn

On 5 December 2016 at 20:09, Martijn Verburg <martijnverburg at gmail.com>
wrote:

> Hi Dalibor,
>
> Thanks for the road - that shouldn't stop us from the initial
> investigation however (it may not even be an issue anymore!). So perhaps
> the message to core-libs can be "We're looking into this in the current 9
> forest but with a view that any fixes would go into 10".
>
> Patrick - do you want to take lead on investigating this or another bug
> and have the rest of us join in?
>
> Thinking out loud there might be a useful mini guide we can put onto the
> wiki on the process we go through.
>
> Cheers,
> Martijn
>
> On Mon, 5 Dec 2016 at 15:23, dalibor topic <dalibor.topic at oracle.com>
> wrote:
>
>> My suggestion for developers who want to work on fixing some JDK cleanup
>> issue, and on nothing else at all, is that they should wait for a little
>> bit longer until JDK 10 forests are created, and then concentrate their
>> cleanup efforts there.
>>
>> On the JDK 9 side, with the JDK 9 Rampdown Start coming up in a few
>> weeks, please be aware that changes for P4 and P5 issues won't be
>> accepted any more from then on into JDK 9 forests.
>>
>> For details on the timing, please see
>> http://openjdk.java.net/projects/jdk9/ .
>>
>> I would absolutely agree that it doesn't makes a lot of sense to ask
>> anyone to start contributing code to some "JDK 9 focused P4/P5 cleanup"
>> effort at this stage of JDK 9 development, in particular with the
>> holiday season and Feature Extension Complete dates coming up right
>> before Rampdown Start.
>>
>> I understand that it can be a bit disappointing to be told that, but I
>> think that's preferable to being "mentored" into spending time on low
>> priority cleanups for JDK 9 that don't have a high a chance of making it
>> into JDK 9 on time.
>>
>> cheers,
>> dalibor topic
>>
>> On 02.12.2016 22:35, Patrick Reinhart wrote:
>> > It’s a bit disappointing answer after all.
>> >
>> > All you get told on the various Presentations is that „we need you“,
>> but when you actually try to help there seem’s to be nobody that actually
>> want’s to mentor new contributors. I know that a new contributors should
>> prove in a some way that they are willing to do more than one contribution.
>> But on the other hand if I ask for help, I should also do some investment
>> on my side.
>> >
>> > The main reason for keeping me on trying to help is the nice response
>> of a couple guys like you Stephen, Stuart Marks, Mandy Chung and Paul
>> Sandoz to just name a few that actually took the time to help me going.
>> >
>> > I read the post [1] but only pointing to documentation only seems to me
>> not be mentoring
>> >
>> > For me it looks like:
>> >
>> > „We are so busy working, that we got not time to help new guys in
>> getting in shape, to take over some of the work“
>> >
>> > -Patirck
>> >
>> > [1] http://mail.openjdk.java.net/pipermail/adoption-discuss/2016
>> -August/001422.html
>> >
>> >
>> >> Am 02.12.2016 um 17:13 schrieb Stephen Colebourne <
>> scolebourne at joda.org>:
>> >>
>> >> This advice reads as "go bother some other mailing list, we're too
>> >> busy doing important things". Essentially it ensures that there will
>> >> be no new contributors to the JDK (core-libs) because they have all
>> >> been sent elsewhere.
>> >>
>> >> Stephen
>> >>
>> >>
>> >> On 2 December 2016 at 15:08, dalibor topic <dalibor.topic at oracle.com>
>> wrote:
>> >>> Community-wide 'starter issues' are a better idea in theory, then
>> they are
>> >>> in practice.
>> >>>
>> >>> Typically the theory behind them is to mark some low priority issues
>> for
>> >>> someone else to fix. But in practice, not all low priority fixes are
>> welcome
>> >>> at all times. See
>> >>> http://mail.openjdk.java.net/pipermail/adoption-discuss/2016
>> -August/001422.html
>> >>> for a longer explanation why that's the case.
>> >>>
>> >>> In practice, it's a better idea to focus new contributors' attention
>> not on
>> >>> what they can do for the large projects with schedules, processes and
>> all
>> >>> that good, complicated stuff that enables releases to happen, like
>> JDK 9 or
>> >>> JDK 8 Updates, but on what they can do in the projects that are in a
>> more
>> >>> exploratory phase, such as Valhalla. Beside exploration of new ideas
>> being
>> >>> more fun for new contributors, they are also often eager for the kind
>> of
>> >>> feedback on the new ideas and designs, that comes from playing with
>> the new
>> >>> toys and often enough, breaking them in interesting ways.
>> >>>
>> >>> cheers,
>> >>> dalibor topic
>> >>>
>> >>>
>> >>> On 02.12.2016 13:53, Patrick Reinhart wrote:
>> >>>>
>> >>>> What was the outcome of that discussion?
>> >>>>
>> >>>> I seem to miss that one. My question comes from the past
>> presentation I
>> >>>> gave about contributing to the OpenJDK. And one of the main things
>> was not
>> >>>> only to do some local hacking but instead try to solve some small
>> issues,
>> >>>> that else would not be fixed because of other more important things.
>> >>>>
>> >>>> -Patrick
>> >>>>
>> >>>>> Am 02.12.2016 um 11:45 schrieb Martijn Verburg
>> >>>>> <martijnverburg at gmail.com>:
>> >>>>>
>> >>>>> There's no JBS query that I know of (I think in the distant past we
>> >>>>> discussed adding a low hanging fruit 'Duke' tag?).
>> >>>>>
>> >>>>> Cheers,
>> >>>>> Martijn
>> >>>>
>> >>>>
>> >>>
>> >>> --
>> >>> <http://www.oracle.com> Dalibor Topic | Principal Product Manager
>> >>> Phone: +494089091214 <+49%2040%2089091214> <tel:+494089091214
>> <+49%2040%2089091214>> | Mobile: +491737185961 <+49%20173%207185961>
>> >>> <tel:+491737185961 <+49%20173%207185961>>
>> >>>
>> >>> 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
>> >>>
>> >>> 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, Jan Schultheiss, Val Maher
>> >>>
>> >>> <http://www.oracle.com/commitment> Oracle is committed to developing
>> >>> practices and products that help protect the environment
>> >
>>
>> --
>> <http://www.oracle.com> Dalibor Topic | Principal Product Manager
>> Phone: +494089091214 <+49%2040%2089091214> <tel:+494089091214
>> <+49%2040%2089091214>> | Mobile: +491737185961 <+49%20173%207185961>
>> <tel:+491737185961 <+49%20173%207185961>>
>>
>> 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
>>
>> 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, Jan Schultheiss, Val Maher
>>
>> <http://www.oracle.com/commitment> Oracle is committed to developing
>> practices and products that help protect the environment
>>
>