Issues, Projects, Milestones, and Releases
Document: INF-109Type: Guide / SOPStatus: ApprovedOwner: Engineering OperationsVersion: 4.2.0Updated: 2026-07-17
Issue Types
| Type | Use |
|---|---|
| Bug | Incorrect behavior |
| Feature | New capability |
| Enhancement | Improvement to existing capability |
| Documentation | Manual, README, or operating knowledge |
| Security | Private handling required; do not disclose sensitive details publicly |
Recommended Project Workflow
Backlog → Ready → In Progress → Review → Testing → Done
Each item should have an owner, priority, target product, expected outcome, and acceptance criteria.
Labels
Use a small, consistent label set: bug, feature, documentation, security, priority:high, status:blocked, and product labels such as product:studio-board.
Release Process
- Confirm all included work is merged and tested.
- Update version and changelog.
- Create an annotated Git tag, for example
v3.2.0. - Create the GitHub Release from the tag.
- Summarize additions, changes, fixes, known issues, and rollback notes.
- Attach approved release artifacts only when needed.
- Verify deployment and record the release in the Manual.
git checkout main git pull --ff-only git tag -a v3.2.0 -m "Cloudberrie Manual v3.2.0" git push origin v3.2.0