stan44/Project_Journal-Csharp_backend-Python-Frontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Page: WIKI_DEVELOPMENT_WORKFLOW
Pages
Home WIKI_API_CONTRACT WIKI_CLI WIKI_CUTOVER_RUNBOOK WIKI_DEVELOPMENT_WORKFLOW WIKI_GIT_WORKFLOW WIKI_MIGRATION_ACCEPTANCE_CRITERIA WIKI_SETUP WIKI_TROUBLESHOOTING WIKI_VAULTS Wiki Git Workflow
Clone
1
WIKI_DEVELOPMENT_WORKFLOW
stan44 edited this page 2026-02-22 02:29:36 -06:00
Table of Contents

Development Workflow

This page defines a lightweight workflow for a small team using phased migration and acceptance gates.

Recommended Board Columns

  • Backlog
  • Ready
  • In Progress
  • Review/Test
  • Done
  • Blocked

Card Template

Each work item should include:

  • Title
  • Owner
  • Scope (single feature or defect)
  • Acceptance IDs (if applicable)
  • Evidence required (test output, logs, screenshots, file refs)
  • Done condition

Example:

  • Title: Phase 1 persistence: fragment repository
  • Acceptance IDs: DOM-001, API-001 (and phase note)
  • Evidence: smoke tests + sidecar roundtrip output

Branching Guidance

  • Keep branches small and focused.
  • One branch per card when possible.
  • Avoid mixing migration phases in one branch.

Review Rules

  • No Pass status without evidence.
  • Any intentional behavior divergence must be documented.
  • Keep security-sensitive changes reviewable and explicit.

Release Gate Mindset

  • Passing local build is not enough.
  • Use acceptance criteria as the source of truth for phase completion.
  • Do not move frontend cutover work ahead of required parity gates.

Documentation Expectations

  • Update wiki pages when commands, dependencies, or behavior change.
  • Keep setup and troubleshooting pages current with real host issues encountered.
  • For local wiki editing and push flow, use WIKI_GIT_WORKFLOW.md.