kevin.rushforth at oracle.com
Fri Jul 24 17:44:39 UTC 2020
Setting aside the policy discussion, the Skara tooling will at least
alert reviewers that something is amiss by showing a warning message
where the JBS issue link and description would go:
* ⚠️ Failed to retrieve information on issue |8250553|.
Perhaps an RFE for the Skara team could make this more explicit in the
case where it can't retrieve the information because the bug is
Confidential. See the following PR, which is referring to a Confidential
bug, for an example of how it looks now:
On 7/24/2020 9:08 AM, Langer, Christoph wrote:
>>> 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?
>> I don't think there is any connection between the two things so the move
>> to git won't change anything there.
> Well, I think at least Skara should give us the technical possibilities to mechanically enforce such a policy.
>>> 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 :)
>> I'm not sure where such a policy decision needs to be made.
> I guess this decision probably needs to be taken by Mark / the Governing Board?
> Best regards
More information about the jdk-dev