0.3.0 Better release planning

[kaimys]

Better Release Planning

Version 0.3.0 substantially improved release planning. The develop branch is now the standard, and the /release skill merges it back to the main branch. It also performs other release steps, such as bumping the version, closing tickets, writing release notes, tagging the release on GitHub, and moving all tickets from "Done" to the "Released" column.

The release board has also been upgraded. You can now change the release target for an entire column, thereby moving all tickets from release v0.4.0 to v0.5.0, for example. You can also reorder the cards on the release board.

Finally, the dispatch/ folder contains the Dispatch workflow scripts, the wiki link, and the canonical skills. Now, the Dispatch setup is collected in one folder.

Order a release by hand

Cards can now be dragged into build order inside a version column on the Release Plan tab. The order lives in its own frontmatter property, so it never fights the Kanban tab's order, and it is off by default: set Release order property (e.g. release_rank) in the board settings to turn it on. A version line's header also offers Copy release order to Kanban, which seeds the Kanban order once from the release order.

#48

Slip a whole release from its header

Right-click a version line's header and choose Retarget release… to move every open card of that line to another version in one step, instead of editing version_target note by note. If any card of the line is already Done or Released, nothing is changed.

#63

Version columns write one spelling

A drop on a version line now writes its highest known patch as vMAJOR.MINOR.PATCH, whether the line came from your planned versions or was discovered from the cards. Before, a discovered line wrote 0.4, which created a second GitHub milestone beside v0.4.0. Existing values are left as they are.

#53

Drops and keys go where you aimed

• A sliced drop lands next to the card you dropped it on. With a slice active, a Kanban drop was positioned by counting only the visible cards, so it landed somewhere else in the full column, or did not move at all. Both tabs now position a drop by the visible card it lands next to.
  BUG00008 A sliced Kanban drop lands at the wrong position #79
• A click sets the keyboard focus. Clicking a card now outlines it and keeps the board focused, and [ / ] only move the card that is visibly outlined. Before, a key could move a card you could not see was selected.
  BUG00006 A mouse click cannot set the board's keyboard focus #73

Finished is not shipped

A Released column after Done separates the test plan is signed off from a version carrying it has shipped. Released counts as complete in a version's progress, rather than being excluded from it.

#43

One folder for a project's setup

dispatch-setup 0.6.0 gathers a project's shared Dispatch setup into one dispatch/ folder: the workflow files, the repo-side scripts, the project settings and a git-ignored link to the vault. Re-running setup on an older project migrates it, and it never removes the old vault link before the new one exists.

#37

Behind the scenes, this project's own wiki is now checked for dead links and property drift with the Obsidian CLI. That is tooling for this repository and changes nothing in the plugin.

#38

Upgrading

No migration of your notes and no configuration change is required. minAppVersion stays at 1.7.2.

Download main.js, manifest.json and styles.css below into <vault>/.obsidian/plugins/dispatch/, or install Dispatch from Obsidian's community plugin directory. Desktop only.

Full changelog: 0.2.5...0.3.0

---

This discussion was created from the release Better release planning.