v0.2 Planning: Key Decisions Needed

[db-tycoon-stephen]

Overview

Before proceeding with v0.2 implementation, we need to make decisions on:

1. Branch Strategy

Question: Where do feature PRs merge?

Option	Flow	Best For
A) Direct to main	feature → main, tag when ready	Simple projects
B) Release branch	feature → v0.2 → main	Milestone-based releases
C) GitFlow	feature → develop → release → main	Complex release cycles

Recommendation: Option B for milestone-based v0.2 release.

2. CI Strategy for Public Repo

Problem: Public repo has sanitized dummy credentials. snowddl-plan requires real Snowflake.

Option	Public CI	Private CI
A) Split CI	Unit tests + lint only	Full CI with snowddl
B) Test account	Full CI with test Snowflake	Full CI with prod Snowflake
C) Mocked only	All tests mocked	Full CI with real Snowflake

Recommendation: Option A - keeps public repo safe while maintaining full validation in private repo.

3. Automation Scope

Question: Should issue → PR automation run in public repo?

• Conservative: Manual PR creation, automation only in private
• Open: Full automation in public (requires careful permission design)

Blocked Issues

All v0.2 issues are blocked pending these decisions:

• CI: Create GitHub Actions workflow for pytest and pre-commit #2, CI: Add snowddl-plan to PR checks #3, Create PR template for SnowTower #4, Implement auto-labeling for PRs based on changed files #5, Create new-user-request issue template #6, Create changelog generation workflow #7, Create release workflow for GitHub releases #8

Draft PR

• PR feat: Add CI/CD workflows and PR template #9 is converted to draft, ready to proceed once decisions made

---

Please comment with your decisions on each item.

[db-tycoon-stephen]

Decisions Made

1. Branch Strategy: Release Branch

• Create v0.2 branch from main
• Feature PRs merge into v0.2
• When v0.2 is complete, merge v0.2 → main and tag

2. Public CI Scope: Unit Tests + Lint Only

• Run pytest (with mocked Snowflake)
• Run pre-commit (Black, Ruff, YAML validation)
• Skip snowddl-plan in public CI (no real credentials)

3. Issue Automation: Manual Only

• Issue templates capture structured info
• Humans create PRs manually from issues
• No automated PR generation in public repo

---

Next steps:

1. Create v0.2 branch
2. Update PR feat: Add CI/CD workflows and PR template #9 to target v0.2
3. Unblock issues CI: Create GitHub Actions workflow for pytest and pre-commit #2, Create PR template for SnowTower #4, Implement auto-labeling for PRs based on changed files #5, Create changelog generation workflow #7, Create release workflow for GitHub releases #8
4. Mark CI: Add snowddl-plan to PR checks #3 and Create new-user-request issue template #6 as descoped (require real Snowflake or automation)

[db-tycoon-stephen]

Decisions Made ✅

1. Branch Strategy: Release Branch

• Create v0.2 branch from main
• Feature PRs merge into v0.2
• When complete, v0.2 merges to main and gets tagged

2. Public CI Scope: Unit Tests + Lint Only

• Run pytest (mocked tests) and pre-commit
• Skip snowddl-plan in public repo (no real credentials)
• Full validation happens in private repo only

3. Issue Automation: Manual Only

• Issue templates capture structured info
• Human creates PRs manually
• Simpler and safer for public repo

---

Next steps:

• Create v0.2 branch
• Update PR feat: Add CI/CD workflows and PR template #9 to target v0.2
• Unblock feature issues

[db-tycoon-stephen]

Decisions made and documented. Work proceeding.