JBS, confused about JDK-8201572, JDK-8202638

[David Holmes]

On 8/05/2018 1:24 AM, Daniel D. Daugherty wrote:
> Hi Thomas,
> 
> I have fixed this for you. I've also attached my note for how to fix this
> kind of issue.
> 
> Before pushing a fix to jdk/jdk, please make sure that the "Fix Version"
> is set to appropriate release. In your bug's case, the bug was targeted
> at "12" (as part of release planning) and you pushed a fix for "11".

We need to improve processes here:

1. If you file a bug you plan on fixing immediately, set the Fix version 
to current release (and ensure it is assigned to yourself)

2. "release planning" should not update assigned, targeted bugs without 
consulting the assignee.

That said IIUC we're supposed to moving to using tbd_* as "future" Fix 
Version rather than hard wiring 12, 13 etc. That should also avoid the 
backport problem.

Cheers,
David

> Dan
> 
> 
> On 5/7/18 10:23 AM, Thomas Stüfe wrote:
>> Hi,
>>
>> I created JDK-8201572 to improve metaspace coding. Implemented fix,
>> reviewed, tested, pushed.
>>
>> However, that item has been marked in the meantime as "target 12". So
>> the push created a new item, JDK-8202638, marked as "backport of
>> JDK-8201572", targeted for 11.
>>
>> JDK-8202638 now is marked as resolved, the original JDK-8201572 is 
>> still open.
>>
>> Can you help? JDK-8201572 should be closed and should have target 
>> release 11.
>>
>> Thank you!
>>
>> Thomas
>