Moving project tracking to GitHub, plus two v0.2.2 scope calls

[db-tycoon-stephen]

This thread collects a few project decisions in one place, so the reasoning lives next to the code instead of in chat or on a separate board. It covers two things: moving tycoon's project tracking from Jira onto GitHub, and what goes into the v0.2.2 release. Both came out of a backlog review this week. Each question is closed-ended with a recommended option, and anyone following the project is welcome to weigh in.

@JesuFemi-O these are your calls as roadmap owner, ideally by Wednesday 10-07, since question 4 sets what goes into v0.2.2 (due 10-09). Reply with letters (for example 1A 2A 3A 4A 5A) plus anything you'd change.

Project tracking moves to GitHub

The Jira board mostly mirrored GitHub, its sync never ran, and keeping both accurate costs a sweep every release. Stephen wants GitHub to be the single place we track work.

Already done: the Jira-only tickets were triaged. The live ones became #347, #348 (docs site, assigned to you), #349 and #350; the rest were closed with a note saying why. City work has a new theme: city label. #351 tracks removing the Jira sync workflow once this is agreed.

1. Layout: A) one Projects board (Status, Release, Initiative) plus milestones per release (recommended); B) milestones and labels only; C) Projects board only.

2. The remaining Jira tickets that mirror a GitHub issue: A) close them with a pointer (recommended); B) leave Jira as a read-only archive.

3. Your rewrite epic in Jira: A) close it, since #81 and #84 to #88 already carry the milestones (recommended); B) keep it until M4 ships.

4. v0.2.2 scope against 10-09

Already merged on the branch: the venv core and init venv build, MotherDuck md: targets, the filesystem data-loss fixes, --max-records, tycoon.yml comment preservation and the Rill path fix. Still to land are small fixes, chiefly #352 (#345, the quoted-token gap in redact_secrets), plus #299/#300 and the docs PRs.

• A) Ship on the date with what's approved by 10-07. If venv layers 4 to 7 (feat(gh-263): project-local sources dir (4/7) #267, fix(gh-264): install source deps into the project venv (5/7) #268, feat(gh-265): warn on the old environment model (6/7) #269, fix(gh-272): --no-prompt auto-installs a catalog source (7/7) #273) and fix(gh-259): tycoon init creates a new dbt project inline, not sibling #260 aren't approved by then, they move to v0.2.3 together, not as a partial stack. (Recommended.)
• B) Slip about a week so the environment model ships whole.
• C) Ship on the date and merge whichever venv layers are approved.

5. City stack (#303, #304, #305, #282)

• A) Move all of it to v0.2.3. None of the PRs are reviewed yet, and bug: city sim tests import the removed town_plan._bfs, breaking #256's test collection #338 blocks ci(PTC-120): collect the renderer suite in the default pytest run and count its coverage #256. (Recommended.)
• B) Tests and render fixes (test(PTC-125): add core simulation tests (generator, layout, town plan) #248 to fix(PTC-127): parse achievements block and render unknown coverage #251) in v0.2.2; the CI gate and help in v0.2.3.
• C) Keep all of it in v0.2.2.

The longer-range plan (v0.2.3 contents, the v0.3.0 theme, close candidates) is drafted. I'll open it as its own thread once v0.2.2 is out.

[JesuFemi-O]

1A 2A 3A 4A 5A

4 and 5 got a closer look before landing on the recommended option, not just a rubber stamp:

4A. The venv stack (#266-273) is 6 of 7 merged already, and #273 is clean, CI green, back in your queue, so the scenario A was hedging against has mostly resolved itself. #260 is the real open question: CHANGES_REQUESTED and DIRTY (actual conflicts, not just waiting on re-review), so it realistically isn't landing clean by 10-07 either way. A's "ships in v0.2.3 if not approved in time" is the right call for it.

5A. Checked the five PRs behind it (248, 249, 250, 251, 256): none have a review on them yet, not even changes-requested, and #338 is still open and blocking #256's test collection. B would mean reviewing and merging two stacked chains from a cold start in under three days. Not worth rushing city-sim code through review to hit the date.

Will have 248/249/250/251/256 reviewed tonight regardless of the v0.2.3 target, since they're sitting in my queue either way.

[db-tycoon-stephen]

Thanks, applied as answered:

• 4A: v0.2.2 ships 10-09. Move downloaded source code from the global sources dir to project-local #263, Install a source's dependencies into the project's own venv #264, Warn when a project is still on the old, global environment model #265, --no-prompt silently skips downloading a catalog source #272 and bug: redact_secrets doesn't mask a quoted motherduck_token value #345 are on the v0.2.2 milestone, along with the two migrate/install-hint fixes (fix(gh-359): point install hints at a command that exists #360, fix(gh-358): carry deps and scaffolding on sources migrate #361) and the release-notes PR (docs(gh-362): draft the v0.2.2 release notes and tidy the CHANGELOG #363, draft). fix(gh-272): --no-prompt auto-installs a catalog source (7/7) #273 re-verified at c41c4bc: both findings are fixed.
• 4A, fix(gh-259): tycoon init creates a new dbt project inline, not sibling #260: fix(gh-259): tycoon init creates a new dbt project inline, not sibling #260 and its issue tycoon init creates a new dbt project as a sibling repo by default #259 moved to v0.2.3.
• 5A: the city issues (chore: delete the retired v5 city planner and its tests #281, tycoon-city renders its help differently from every other tycoon command #282, OSI generator claims MotherDuck support it doesn't have #298, city: bring the simulation test suite and city docs across (PTC-125) #303, city: vehicles and guests never draw, and the HUD shows 0% documented (PTC-127) #304, ci: collect the city renderer tests and gate the shipped web bundle (PTC-120) #305, bug: city sim tests import the removed town_plan._bfs, breaking #256's test collection #338) and PRs (test(PTC-125): add core simulation tests (generator, layout, town plan) #248 to ci(PTC-120): collect the renderer suite in the default pytest run and count its coverage #256, feat(gh-282): tycoon-city renders its help like every other tycoon command #287, docs(gh-323): add a mental model of the city map #331) moved to v0.2.3. Your reviews tonight still help, they just land there.
• 1A to 3A: I'll set up the Projects board and close the mirrored Jira tickets after v0.2.2 ships, so it doesn't compete with release week. chore: remove the Jira sync workflow and PTC- key handling once Jira is sunset #351 tracks removing the sync workflow.

Written by Claude for Stephen.