jdk9 update branch?

jesper.wilhelmsson at oracle.com jesper.wilhelmsson at oracle.com
Mon Jun 26 17:48:57 UTC 2017

> On 26 Jun 2017, at 19:27, Vladimir Kozlov <vladimir.kozlov at oracle.com> wrote:
> I thought label is 9-bp for backports to jdk 9.

Yes, that is another way to tag a bug for backporting but that won't remind you in the same way as having an issue assigned to you. (Well, I guess that depends on wether you keep an eye on your assigned issues or not :-) )

> Vladimir
> On 6/26/17 4:35 AM, jesper.wilhelmsson at oracle.com wrote:
>> Hi,
>> I agree that the 9u repo is due to be created fairly soon. (I'm not involved in the repo creation though.)
>> Just a suggestion to help you remember the backports: Create the backport issue in JBS, set the fix version to 9-pool and assign it to yourself. As long as you keep track of issues assigned to you it should stay on your radar until the update repo is created.
>> Cheers,
>> /Jesper
>>> On 26 Jun 2017, at 08:23, Langer, Christoph <christoph.langer at sap.com> wrote:
>>> Hi,
>>> as the JDK9 forest is virtually closed now due to the upcoming release, I'm wondering when a JDK9 update branch will be opened.
>>> Imagine there's a bug which applies to all releases, e.g. from 10 down to 8. Then I would first fix it in 10 and after that request a downport to lower releases. For 8 that would probably work but for 9 it is to my knowledge not possible at the moment. So I trigger the downport to 8 and then step away. And eventually it's very likely that I forget to do the downport to 9 at the time there will be an update branch. So, when will an update branch be opened? Or what else can I do to not forget my potential fixes for JDK9 update releases, e.g. label my bug for some automatic integration?
>>> Thanks and best regards
>>> Christoph

More information about the jdk9-dev mailing list