> On 16. Apr 2020, at 20:16, Robert Reeves <[email protected]> wrote:
>
> Just to follow up…we’re trying to get this security issue resolved but have
> not been able to get access to SECURITY-519. How can we view that so we can
> fix the issue?
As I wrote in a previous response, Keith's account has access to the issue.
Since you're working with him per your first email in this thread, ask him for
the details.
>From a Jenkins project POV, Keith is the only maintainer of the plugin, and
>the only one entitled to view the security issue information for his plugin.
>(While we can add additional users to the private issue, that requires consent
>by the current maintainer.)
The only option that doesn't require active involvement from a current
maintainer is to request a transfer of maintainership of the plugin per
https://jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/6C7D5AFB-2AF8-4BD8-8C76-5A07E3CC279B%40beckweb.net.
