sgehwolf at redhat.com
Wed Jul 29 08:21:10 UTC 2020
On Tue, 2020-07-28 at 13:02 -0700, Joe Darcy wrote:
> On 7/24/2020 6:47 AM, Severin Gehwolf wrote:
> > On Fri, 2020-07-24 at 23:37 +1000, David Holmes wrote:
> > > On 24/07/2020 11:15 pm, Severin Gehwolf wrote:
> > > > Hi,
> > > >
> > > > Any particular reason this bug is not public?
> > > It contains information in the description that requires it not be
> > > public - sorry. But it basically says (as seen in the patch) that the
> > > resource array may be too small.
> > OK, thanks, David.
> > Does anybody know whether this issue of closed bugs being used to push
> > changes will be rectified once moved to git and skara via JEPs 357/369?
> > It would be nice if that could be caught in future. I.e. if a bug
> > exists that contains internal/confidential info, another bug needs to
> > be created, possibly referencing the other. In a setup which I've in
> > mind only public bug could be used to push changes. Hopefully we'll get
> > there :)
> It remains on our list (including my own list) to evaluate some Jira
> plugins which would allow most of the incidentally non-public bugs to be
> made public.
That's great to hear! Thanks for this.
> Note that there are classes are bugs that are eventually pushed
> publicly, including security vulnerabilities, that would not be made
> public even with the augmented tooling.
Understood, thanks. Hopefully we can get to a point where *only*
security vulnerability bugs would be private.
More information about the jdk-dev