Skip to content

Release process: v0.1 is the Pd baseline, v0.2 is gone #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zeyuyang42 merged 1 commit into from
Oct 17, 2026
Merged

Release process: v0.1 is the Pd baseline, v0.2 is gone #52

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/design/release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,8 @@ _Maintainer steps. User-facing install instructions live in `maxmsp/README.md` a
is the file the `release` job reads. A core change therefore cannot be forgotten by a host:
it was recorded when it landed, and the Pd file keeps accumulating while only Max ships.
- Before tagging, check the notes against git rather than memory. `<last>` is the host's
previous tag (`v0.2` for Pd until the first `pd-v` tag exists):
previous tag (`v0.1` for Pd until the first `pd-v` tag exists; it is the Pd 0.1 release and
the only pre-split tag left):
```bash
git log <host>-v<last>..HEAD --oneline -- core <maxmsp|puredata>
```
Expand Down Expand Up @@ -158,7 +159,8 @@ Then tag `max-v<ver>` as under *Ship* above.
- Pending "Breaking" items for the next Pd release: none recorded. (The `mc.` rename and the
`root` mode change were Max-only.)
- Rename `docs/releases/pd-next.md` to `docs/releases/pd-v<ver>.md` and check it against
`git log v0.2..HEAD --oneline -- core puredata` (rule 7; `v0.2` is the last Pd tag).
`git log v0.1..HEAD --oneline -- core puredata` (rule 7; `v0.1`, the Pd 0.1 release, is the
last Pd tag). Pd versioning starts properly with `pd-v0.3.0`.
- Bump `VERSION` in `puredata/zerr-meta.pd`. It is the only place the Pd version lives: the
Makefile compiles it in as `ZERR_PD_VERSION`, pd-lib-builder reads it as `lib.version`, and the
zip name carries it.
Expand Down
5 changes: 3 additions & 2 deletions docs/releases/pd-next.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
_Pending notes for the next Pure Data release (rule 7 in `docs/design/release-process.md`).
Renamed to `pd-v<ver>.md` when the version in `puredata/zerr-meta.pd` is decided. Lines added
since 2026-10-15 only; everything earlier since `v0.2` still has to be enumerated with
`git log v0.2..HEAD --oneline -- core puredata` before the first `pd-v` tag._
since 2026-10-15 only; everything earlier since `v0.1` (the Pd 0.1 release, the last Pd tag)
still has to be enumerated with `git log v0.1..HEAD --oneline -- core puredata` before the first
`pd-v` tag._

## Changed

Expand Down
Loading