RFR: Addition of a causes link type [v7]

[David Holmes]

On Wed, 22 Jan 2025 13:06:23 GMT, Alexey Ivanov <aivanov at openjdk.org> wrote:

> Why not? I assume that one thing you want to capture is when backporting. So if B is broken, you definitely would want to know that it caused undesired behavior that was fixed by C. Or am I mistaken?

First off if B is broken it should be Verified as Fix Failed and that is what tells backporters there is an issue. It then has a link to C (the backout) and a link to a REDO issue (potentially). These links are evident regardless of how the link is described.

If we say that the Backout issue is caused by B then that would imply the REDO issue is also caused by B - they are both only necessary because B was broken. Are you proposing that as well? If so the Backout section of the guide also needs to reflect this.

I understand that without B being broken there is no need for a Backout issue but that relationship is to me more specific than simply causal. Maybe we need a backed-out-by kind of link.

-------------

PR Comment: https://git.openjdk.org/guide/pull/139#issuecomment-2609044460