-
Task
-
Resolution: Unresolved
-
Minor
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
Unset
-
None
-
-
-
ReBAC Sprint 13, ReBAC Sprint 14, ReBAC Sprint 15
Summary and goal
Description of what we're building, the end goal and how we'll go about it.
The goal is to establish basic management and automation for the Relations API Java client, so that it can be maintained long term.
For example, updates to the API/proto should trigger a PR with the autogenerated changes, updates to dependencies should generate a PR, PR creation should trigger a validation pipeline, PR merges should push to maven central with suitable version management.
Client repo: https://github.com/project-kessel/relations-client-java
Acceptance Criteria
These conditions must be met for the epic to be considered complete. This provides a detailed definition of scope and the expected outcomes, written from a user's point of view.
- All of the tasks and stories attached to this epic should be closed.
Checklist
Checklist Item | Required | Notes or Comments |
---|---|---|
Workstream or external team dependencies? | Y / N | N |
ADR Required?
|
Y / N | N |
Testing plans
|
Y / N | ? |
Known dependencies?
|
Y / N | N |
Open Questions
Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed.
1.
|
Add github actions pipeline to deploy artifacts to maven central on merge |
|
Refinement | |
Unassigned |
2.
|
Create GPG signature for the kessel team to be used in automations |
|
Backlog | |
Unassigned |