Skip to content

Commit d1a7dff

Browse files
mmckyclaude
andauthored
chore(quantecon): cut qe-v4 (book-parts, #26) (#32)
Bumps qe_version to qe-v4 and adds the book-parts entry (id: 4) to merged_features with its squash sha 5edc040. The git tag qe-v4 will be cut on the squash commit of this PR. Also moves the book-parts entry in UPSTREAM-PRS.yml from `status: planned` → `pending` and fills in its `commits` list with the now-known squash sha. Also syncs the VERSION.yml header comment to the new tag-cut workflow (metadata PR first, then tag) so it matches README §"Maintaining VERSION.yml". Previous comment text still described the legacy "tag-then-update" order and the "batched not per-PR" convention. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
1 parent 5edc040 commit d1a7dff

3 files changed

Lines changed: 30 additions & 12 deletions

File tree

quantecon/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Two tracked YAML files in `quantecon/` record orthogonal facts. Keep them in syn
1717

1818
Every time a feature PR lands on `main`, append a row to `merged_features` with its squash `merge_sha`. The `tag` field stays null until a `qe-v<N>` tag is cut over that feature.
1919

20-
Tags can be cut per-PR (one tag per feature, easy traceability) or batched at a checkpoint (one tag covering several merged features ready for downstream dogfooding) — pick whichever fits the cadence. To cut a tag, do the metadata update *first* so the tagged commit's tree is self-consistent:
20+
Tags can be cut per-PR (one tag per feature, easy traceability) or batched at a checkpoint (one tag covering several merged features ready to deploy to book-dp1 / book-dp2 for testing) — pick whichever fits the cadence. To cut a tag, do the metadata update *first* so the tagged commit's tree is self-consistent:
2121

2222
1. Open a doc PR updating `VERSION.yml`: bump `qe_version` to `qe-v<N+1>` and set `tag: qe-v<N+1>` on each previously-untagged entry in `merged_features` that is included in this tag.
2323
2. Squash-merge the doc PR.

quantecon/UPSTREAM-PRS.yml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,11 @@ upstream_candidates:
7575
`section: parts` ParentEntry: emits a Roman-numbered divider folder
7676
("Part I — Theory") and wraps chapter groups. Chapter counter
7777
continues across part boundaries (LaTeX `book` default).
78-
status: planned # PR #26 still open against our main
79-
commits: [] # populated once #26 squash-merges into main
78+
status: pending
79+
commits:
80+
- sha: 5edc040d
81+
local_pr: 26
82+
title: "Book parts: section: parts dividers with Roman labels"
8083
depends_on:
8184
- book-mode-with-section-scope
8285
upstream:

quantecon/VERSION.yml

Lines changed: 24 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -15,16 +15,24 @@
1515
# `merge_sha` and `tag: null`. The `tag:` field is filled in later when a
1616
# `qe-vN` tag is cut.
1717
#
18-
# Tags are cut at meaningful checkpoints (typically when a batch of
19-
# features is ready for downstream dogfooding), **not per-PR**. When
20-
# cutting a tag:
21-
# 1. Pick the `main` commit at the head of the batch
22-
# 2. Tag it `qe-v<N+1>` and push the tag
23-
# 3. Set `tag: qe-v<N+1>` on each previously-untagged entry in
24-
# `merged_features` that is included in the batch, then bump
25-
# `qe_version` to `qe-v<N+1>`
18+
# Tags can be cut per-PR (one tag per feature, easy traceability) or
19+
# batched at a checkpoint (one tag covering several merged features
20+
# ready to deploy to book-dp1 / book-dp2 for testing) — pick whichever
21+
# fits the cadence.
22+
# To cut a tag, do the metadata update *first* so the tagged commit's
23+
# tree is self-consistent:
24+
# 1. Open a doc PR updating this file: bump `qe_version` to `qe-v<N+1>`
25+
# and set `tag: qe-v<N+1>` on each previously-untagged entry in
26+
# `merged_features` that is included in this tag.
27+
# 2. Squash-merge the doc PR.
28+
# 3. Tag the resulting `main` commit:
29+
# git tag qe-v<N+1> <sha> -m "qe-v<N+1>: <summary>"
30+
# git push origin qe-v<N+1>
31+
#
32+
# Doing it in this order means anyone who `cat`s VERSION.yml at tag
33+
# `qe-v<N+1>` sees a self-consistent file (qe_version matches the tag).
2634

27-
qe_version: qe-v3
35+
qe_version: qe-v4
2836
upstream_base: 1.9.0
2937

3038
merged_features:
@@ -48,3 +56,10 @@ merged_features:
4856
local_pr: 28
4957
merge_sha: 80bb9ecf
5058
tag: qe-v3
59+
60+
- id: 4
61+
name: book-parts
62+
description: Book parts dividers (Roman-numbered) with continuous chapter counter
63+
local_pr: 26
64+
merge_sha: 5edc040d
65+
tag: qe-v4

0 commit comments

Comments
 (0)