Repository navigation
Add development and release process documentation - #275
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Unresolved issues affect deployment reproducibility, release traceability, and workflow accuracy.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 2
Open (4)
What changed in this PR
Adds documentation for Databus branching, deployments, releases, version traceability, and audits.
Changes:
- Defines branch workflows.
- Documents development and production deployment processes.
- Describes release versioning and audit responsibilities.
| File | Summary |
|---|---|
DEVELOPMENT.md |
Adds development and release process documentation. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| 2. A release is prepared, including the appropriate version/tag. | ||
| 3. `dev` is merged into `main`. | ||
| 4. A production Docker image is built from the released `main` version. |
| Each production release should be uniquely identifiable by a version and/or Git tag. The release should provide a clear relationship between: | ||
|
|
||
| **Git commit/tag → Docker image → deployed service** | ||
|
|
||
| This makes it possible to determine exactly which source-code version is running in production and to reproduce or roll back a deployment if necessary. |
| The repository uses three types of branches: | ||
|
|
||
| * **`main`** — production branch containing the currently released and production-ready version. | ||
| * **`dev`** — development branch containing the current integration and development version. | ||
| * **`feature branches`** — temporary branches created from `dev` for individual features, fixes, or other changes. |
|
|
||
| **https://databus.dev.dbpedia.link/** | ||
|
|
||
| **Open question:** How frequently should the development instance be deployed — on every commit, daily, weekly, or according to another schedule? |


No description provided.