Should I use Bug ID JDK-8239012 or JDK-8234608 for this 14u backport?
Man Cao
manc at google.com
Wed Feb 19 21:32:19 UTC 2020
Thanks for the help!
Now I know how to properly handle cases like this.
-Man
On Wed, Feb 19, 2020 at 1:26 PM Jesper Wilhelmsson <
jesper.wilhelmsson at oracle.com> wrote:
> You should be good to go now. Now you can use JDK-8234608 as the bugid for
> the backport as well.
> /Jesper
>
> > On 19 Feb 2020, at 22:15, Jesper Wilhelmsson <
> jesper.wilhelmsson at oracle.com> wrote:
> >
> > Since JDK-8234608 is the bug mentioned in the commit comment, let's use
> that one as the main bug. Let me clean that up for you.
> > Please don't push the backport until I get back to you.
> > /Jesper
> >
> >
> >> On 19 Feb 2020, at 22:01, Man Cao <manc at google.com> wrote:
> >>
> >> Hi,
> >>
> >> I'm trying to submit a backport to 14u:
> >> https://bugs.openjdk.java.net/browse/JDK-8239012.
> >> The problem is that I initially created JDK-8234608
> >> <https://bugs.openjdk.java.net/browse/JDK-8234608>, and "Fix Version"
> was
> >> set to 14. When I pushed it to jdk/jdk, the major version has become
> 15, so
> >> "HG Updates" automatically created JDK-8239012
> >> <https://bugs.openjdk.java.net/browse/JDK-8239012>.
> >> I have closed JDK-8234608 <
> https://bugs.openjdk.java.net/browse/JDK-8234608> as
> >> a duplicate, but the commit record
> >> <https://hg.openjdk.java.net/jdk/jdk/rev/7ec9c6a6df4f> in JDK-8239012
> >> <https://bugs.openjdk.java.net/browse/JDK-8239012> still shows
> JDK-8234608.
> >>
> >> So the question is, when I push it to 14u, should I keep using
> JDK-8234608
> >> as the bug ID in the commit message, or can I change it to JDK-8239012?
> >>
> >> -Man
> >
>
>
More information about the jdk-updates-dev
mailing list