The batch: the old level 1, and moving off it

Code level 1 used to mean the batch: stories were gathered on a release branch and reached main together, as a release. It is being replaced by trunk flow, in which each story lands on main by itself and a release is a separate act there (method). Both exist while projects move. This page records the old way in enough detail to recognise a project still on it and to move it; when the last one has moved it shrinks to a short example of what not to do.

What the batch was

One command, tp release, both integrated a story and versioned it, and what it did depended on what other stories were doing:

Stories in flight How they reached main Pull requests
one (a lone release) tp release on the story branch made the release commits (changelog, version) on that branch and opened its pull request into main; tp release on main tagged the merge 1
two or more tp release batch, or the second story's run, cut release from main, reverted the first story's release commits and retargeted its pull request; each story's pull request went into release; tp release on main made the release commit there and opened one pull request from release into main n + 1

The state this needed lived in release on the remote, in .tp-release.yml and .tp-release-inflight in the checkout, and in which pull requests were open into which branch.

Why it is dropped

A story reached main only as part of a release, so landing and releasing were one act. Every step therefore began by working out a state shared between stories: whether a batch was open, whose it was, who held the next version. Agents lost their place in it. release also received work before main did and was merged into it, which is the reverse of a trunk-based release branch.

Batch Trunk flow
A story reaches main inside a release by its own pull request, with no version
Command on a story branch tp release tp story land
tp release runs on story branches and main main only
Long-lived branches main, and release while a batch is open main
Release commits live on the story branch, or release a release/vX.Y.Z branch the tool cuts, merges and deletes
Which stories a release holds chosen, by opening a batch whatever has landed since the last tag
main between releases equals the last tag landed, unreleased work; releasable at every merge
Shared state to read first release, .tp-release.yml, open pull requests none: a story's next step never depends on a release

What carries over unchanged: story branches named story/<issue>-<slug>, the changes/<issue>.<kind>.md fragment per story, the version worked out from the fragments' kinds, and a main that refuses direct pushes.

Recognising a project on the batch

Sign Where
maturity.code is 1 or 2 and there is no maturity.flow: trunk task-plus.yml
a release branch, or pull requests into one the forge
.tp-release.yml or .tp-release-inflight the checkout
"tp release on the story branch opens the pull request" the project's agent instructions or README

A project at maturity.code: 0 is on neither: it commits on main and has nothing to move off.

Moving a project

The move is a story in the project, like any change of level, and it is the first story landed the new way.

  1. Bring the project to rest. tp maturity must print at rest. Finish the open batch with the old process, or clear what it lists (task-plus's at rest table gives the remedy for each item). Nothing in flight is carried across.

  2. Open the story and cut its branch from main.

  3. Declare the flow on that branch:

    # task-plus.yml
    maturity:
      code: 1
      flow: trunk
    
  4. Rewrite the project's instructions (agent instruction file, README, contributing notes) so they say: a story is landed with tp story land; tp release runs on main only; the story branch never touches the changelog or a version file.

  5. Check the build is a build: the check task leaves no tracked file modified, since under trunk flow that fails it (build).

  6. Write the fragment and land the story with tp story land.

  7. Clear what the batch left: delete release on the remote if it survives, and .tp-release.yml and .tp-release-inflight from checkouts.

  8. Release when wanted: tp release query on main names the next step.

When the transition ends

maturity.flow is a temporary key. Once task-plus and the level 1 projects have moved, task-plus makes trunk flow what code level 1 means and removes both the batch and the key; projects then delete the flow: line, and this page is cut down to the comparison table.