On 3/24/2015 10:34 AM, Mario Torre wrote:
On Tue, 2015-03-24 at 10:28 -0700, Phil Race wrote:
> i.e is it still JBS but there is some other target release value that
should be being used ?
It seems that question has been answered in the link Dalibor sent : its
"openjdk7u"
for the release.
Yes, this makes totally sense, however the bug was closed as won't fix.
I know I'm failing from my side in adjusting to this new work flow so
please indulge me, but I would expect the bug to be still open and just
move from 7-pool to openjdk7u.
There is a workflow - one that I think is over-used - of creating
backports and
closing them as "not an issue", or "will not fix", as a way of making it
clear
that "we didn't just forget about this release, we made a decision
documented here".
Sometimes they are created and closed like that all in the blink of an eye.
That's not exactly what happened here, since I think there may have been an
intent to fix that was rescinded, but probably it could be considered to
document
that better by its presence than its absence.
Or will a new backport be createad with openjdk7u as target release?
* If you pushed to the new openjdk 7 without doing anything, then a new
backport will
be automatically created when you push
* If you create a new one manually, assign to yourself, target it to
openjdk7, then that one
will get marked fixed when you push
* Or, you could re-open the existing one, target it to openjdk7u (and
assign to yourself)
and it will be marked fixed when you push. However I think the workflow
I documented
above will then be messed up.
-phil.
Thanks,
Mario
