Skip to content

Conversation

jiridanek
Copy link
Member

https://adr.github.io/

Description

$ brew install adr-tools
$ adr init docs/architecture/decisions

How Has This Been Tested?

This will be tested in production.

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

…e on this project with the help of adr-tools

```
$ brew install adr-tools
$ adr init docs/architecture/decisions
```
@openshift-ci openshift-ci bot requested review from atheo89 and jstourac January 22, 2025 13:25
@openshift-ci openshift-ci bot added the size/s label Jan 22, 2025
@jiridanek
Copy link
Member Author

There's already a place for these, it's in

https://github.com/opendatahub-io/architecture-decision-records/tree/main/architecture-decision-records

and there are subdirectories for individual components there.

@jiridanek jiridanek closed this Jan 22, 2025
@jiridanek jiridanek reopened this Mar 22, 2025
Copy link
Contributor

openshift-ci bot commented Mar 22, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jstourac for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added size/s and removed size/s labels Mar 22, 2025
@jstourac
Copy link
Member

There's already a place for these, it's in

https://github.com/opendatahub-io/architecture-decision-records/tree/main/architecture-decision-records

and there are subdirectories for individual components there.

My question is - why do we want to do such a thing in our separate repository instead of having this in the common place where other components have these documents themselves too?

@jiridanek
Copy link
Member Author

My question is - why do we want to do such a thing in our separate repository instead of having this in the common place where other components have these documents themselves too?

We'd probably want to have a subdirectory in the shared repo. Either one subdirectory named after workbenches component of ODH, or one for notebooks and one for kubeflow-notebook-controller.

My inclination is all in one directory, named after ODH component.

@harshad16
Copy link
Member

Great initiative
apologies for missing this.
reviewed the PR: opendatahub-io/architecture-decision-records#91
we can proceed to include more ADRs there.

jesuino pushed a commit to jesuino/notebooks that referenced this pull request Jun 17, 2025
…lux/component-updates/component-update-odh-pipeline-runtime-datascience-cpu-py311-ubi9-n-v2-22

Update odh-pipeline-runtime-datascience-cpu-py311-ubi9-n-v2-22 to 3ade9a0
@atheo89
Copy link
Member

atheo89 commented Jul 18, 2025

closing this PR in favor opendatahub-io/architecture-decision-records#91

@atheo89 atheo89 closed this Jul 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants