Articulating Interactions with JBS

[smlambert]

This is a listing of the several use cases when we interact with the Java Bug System (JBS) at the project. The intent is to list them, and then look for opportunity to automate and create a smoother interaction between this upstream bugs database and our projects.

AQAvit

• Tracking test failures seen during AQAvit runs (need to be reported or already reported upstream using JBS label)

Release Notes

• Creation of release notes (related to this prototype)

Support

• Managing adoptium-support issues - see the full set of labels below:
  • checking for the existence of an issue jbs:preexisting-issue
  • raising a new upstream issue jbs:reported
  • checking for the status of a raised issue (whether we delivered a patch, or whether patch needs backporting, or was rejected)

---

Mostly for our use cases, we can query anonymously. However, there are case for all 3 use cases where some information is not available (when querying bugs that are restricted visibility and for CVE patch details). In those