Versions and features

Versions

A version is a label on a card, such as 1.0. It is only a label: there is no list of versions to keep, and no dates.

It does three things:

• list_cards and claim_next can be narrowed to one version.
• Ready cards are handed out by version first. See What is next.
• The board groups the cards that are to do under their version.

A leading v is dropped, so v1.0 and 1.0 are the same label.

Features

A feature is a named group of cards that ship together, finer than a version. You make one with create_feature or from the board, and put a card on it when the card is made or later. A card is on one feature or none.

list_features shows each feature with how many of its cards are done.

Feature branches

By default a feature is a label and nothing more: every card is cut from your main branch and proposed back to it.

A project can instead give each feature a branch of its own, such as feature/billing. Then:

• A card on the feature is cut from the feature’s branch, and its pull request goes into that branch.
• A card is tracked as merged into the feature’s branch separately from merged into main. A card that waits on another for the same file is let through when that work reaches its own base or main, whichever comes first.
• When the feature’s cards are done and merged into its branch, the feature is proposed to main as one pull request.

This keeps a run of related cards out of main until they are ready together. Like the other git rules, it is a setting of the project with no control on the board yet. See Git rules.