Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addition of a causes link type #139

Closed
wants to merge 13 commits into from
2 changes: 1 addition & 1 deletion src/guide/jbs-jdk-bug-system.md
Original file line number Diff line number Diff line change
@@ -233,7 +233,7 @@ Now that the issue is in the right component and has the basic information, the
* Well contained issues that seem to be easy to fix: [[starter]{.jbs-label}](#starter)
* Enhancements that are pure cleanups: [[cleanup]{.jbs-label}](#cleanup)
* Project specific issues usually have their own labels as well
1. Managing regressions - for a bug (B) where behavior has _incorrectly_ changed from a previous fix (A) sure that the label [[regression]{.jbs-label}](#regression) is added. Once it is known what fix caused the regression a [caused by]{.jbs-value} link should be added to 'B' or a causes link to 'A'. A causes link would be added to A if after the integration or release of A, it is found that additional work needs to be done. This might be that extra work in another area forgotten and needs to be completed or the more common case would be that a fix ‘causes’ a change of behavior (intentional or otherwise). If 'A' has been identifed as well as a caused-by link to that issue and set the [Introduced in Build]{.jbs-field} and [Introduced in Version]{.jbs-field} fields of 'B', based on which release 'A' was fixed in. Do not add a [caused by]{.jbs-value} link if there was no specific product fix which _caused it_, for the additon of a test which finds an underlying problem should not be linked.
1. Managing regressions - for a bug (B) where behavior has _incorrectly_ changed from a previous fix (A) ensure that the label [[regression]{.jbs-label}](#regression) is added. Once it is known what fix caused the regression a [caused by]{.jbs-value} link should be added to 'B' or a [causes]{.jbs-value} link to 'A'. A [causes]{.jbs-value} link would also be added to A if the fix _causes_ a change of behavior (intentional or otherwise) or it is found after integration, that additional work needs to be done. If 'A' has been identified as well as a adding a [caused by]{.jbs-value} link to that issue, set the [Introduced in Build]{.jbs-field} and [Introduced in Version]{.jbs-field} fields of 'B', based on which release 'A' was fixed in. Do not add a [caused by]{.jbs-value} link if there was no specific product fix which _caused it_, for example, the addition of a test which finds an underlying problem should not be linked.

At this point move the issue into the [Open]{.jbs-value} state.