Sigh. On Mon, Feb 18, 2019 at 11:07 AM Aleksey Shipilev <sh...@redhat.com> wrote:
> On 2/18/19 8:02 PM, Martin Buchholz wrote: > > I am trying to follow the process - this thread is the RFR for 11u ! > > No, it is not. > > Please put yourself into the shoes of reviewers and maintainers: they need > to have all the context > at once, not reading through tens of messages and replies spread across > the mailing lists. > > Try again, by starting a new thread, spelling out the exact thing you want > to backport, the history > behind the issue, etc. Here is the template: > > https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-February/000425.html Your backporting and JIRA REST automation is totally awesome, but I think it would be an excessive burden to expect everyone doing backports to clear such a high bar. All the javadoc tests pass ./test/langtools/jdk/internal/shellsupport/doc/ $(find test -name javadoc) At Google, we originally backported 8212233 with the hope that it would fix problems with maven, but the problems did not get resolved. Although we are "using" this backport, perhaps it is not needed in jdk11u. I'm not at all sure what to do here.
