Preparation of update releases

Volker Simonis volker.simonis at gmail.com
Wed Oct 24 19:05:28 UTC 2018


Andrew Haley <aph at redhat.com> schrieb am Mi. 24. Okt. 2018 um 17:02:

> On 10/24/2018 01:42 PM, Rob McKenna wrote:
> > 2) non-vuln closed issues may need to be distributed along with the vulns
> > on vuln-dev.
>
> Indeed. This has been a problem for a little while now. It's hard for
> me, as an outsider, to make any meaningful distinction between a non-
> vuln and a vuln closed issue, but we get one and not the other.
>

The easiest and most practical solution would be to grant members of the
Vulnerability Group access to the security repos. I don’t see any principle
problem with such a solution because there’s nothing in these repos that
members of the Vulnerability Group are not allowed to see. So it can only
be technical problems which prevent such a solution and technical problems
should be easy to solve :)


> --
> Andrew Haley
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F
> <https://maps.google.com/?q=035+332F+&entry=gmail&source=g>A671
>


More information about the jdk-updates-dev mailing list