redhat-openjdk labels in JIRA
Gil Tene
gil at azul.com
Thu Apr 25 11:31:41 UTC 2019
Why use “redhat” in a tag name used for overall coordination outside of RedHat personnel? Can we come up with a non-vendor-specific tag that would mean “issue of interest to the project”, or “issues of interest for backporting”?
E.g. backport-openjdk seems much more appropriate than redhat-openjdk. Or backport-8u and backport-11u (and backport-7u) if we want to specifically identify them per target updates project or version.
Sent from my iPad
> On Apr 25, 2019, at 3:18 AM, Aleksey Shipilev <shade at redhat.com> wrote:
>
> Hi,
>
> We use our "redhat-openjdk" tag to get issues tracked in our backporting tracking. We used to have
> it to coordinate work with others, "claiming" the issues for our team to work on. Starting today, we
> mark _all_ issues of our interest, and it does not necessarily mean we (Red Hat people) are doing
> the backporting work for it -- so if you see that tag on the issue, you are free to grab it for
> backports anyway!
>
> As we discussed earlier, you might consider putting down the JBS comment that you are doing
> backports for a given issue, and then replace that comment with the actual Fix Request. Please only
> grab the issue if you are actually doing the work, not just planning to do it. This apparently
> scales better and works for non-Red Hat people too :)
>
> --
> Thanks,
> -Aleksey
>
More information about the jdk-updates-dev
mailing list