Skip to content

Add development and release process documentation - #275

Merged
m1ci merged 1 commit into
mainfrom
m1ci-patch-1
Sep 25, 2026
Merged

m1ci merged 1 commit into
mainfrom
m1ci-patch-1

Conversation

@m1ci

@m1ci m1ci commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Copilot AI lite review requested due to automatic review settings September 25, 2026 08:23
@coderabbitai

coderabbitai Bot commented Sep 25, 2026

Copy link
Copy Markdown

Review in Change Stack →

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 7e1df8e0-9855-4dc5-95c6-6925c7d5635f

📥 Commits

Reviewing files that changed from the base of the PR and between 5028040 and 42ff4b5.

📒 Files selected for processing (1)
  • DEVELOPMENT.md
 ________________________________________________________________________________________________________________________________________
< Use assertions to prevent the impossible. Assertions validate your assumptions. Use them to protect your code from an uncertain world. >
 ----------------------------------------------------------------------------------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@m1ci
m1ci merged commit e42e4a9 into main Sep 25, 2026
1 of 2 checks passed
@m1ci
m1ci deleted the m1ci-patch-1 branch September 25, 2026 08:25

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 Medium severity · 2 Low severity

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.

Comment thread DEVELOPMENT.md
Comment on lines +44 to +46
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.
Comment thread DEVELOPMENT.md
Comment on lines +55 to +59
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.
Comment thread DEVELOPMENT.md
Comment on lines +7 to +11
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.
Comment thread DEVELOPMENT.md

**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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants