This is an automated email from the ASF dual-hosted git repository. spmallette pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit b11f6702b494851a630ef7bcb2d42d37bded63be Merge: e8e5a3a1ef 5d19e40501 Author: Stephen Mallette <[email protected]> AuthorDate: Mon Aug 10 12:37:48 2026 -0400 Merge branch '3.7-dev' into 3.8-dev .beads/PRIME.md | 3 +++ docs/src/dev/developer/for-committers.asciidoc | 10 +++++++- docs/src/dev/developer/release.asciidoc | 34 ++++++++++++++++++++++++++ 3 files changed, 46 insertions(+), 1 deletion(-) diff --cc docs/src/dev/developer/release.asciidoc index 0ab181eabf,313b7d49b4..ac12100d2d --- a/docs/src/dev/developer/release.asciidoc +++ b/docs/src/dev/developer/release.asciidoc @@@ -135,10 -135,17 +135,21 @@@ during this period ... All tickets not marked "Fixed", "Done", or "Implemented" for their Resolution should not have a Fix Version assigned (use common sense when reviewing these tickets before removing the Fix Version as it is possible the incorrect Resolution may have been assigned). + .. Review the beads expected to land in this version, as described in <<beads,Using Beads>>, and ensure that: + ... Every bead belonging to work that has merged is `pinned`. Pinning is what makes a bead permanent, so a + subgraph left closed but unpinned is work whose record was never completed. + ... The release label on each bead matches the version under release. The label value must be quoted and + closed beads must be included, as in `bd query 'labels="xx.yy.zz"' --all`, because an unquoted version + number fails to parse and closed beads are hidden by default. + ... Each root carries a record bead for its JIRA issue, pull request, proposal or dev mailing list thread. + A small fix that never had one of these is a legitimate exception. + ... `bin/beads-report.py` reports nothing unexpected. Run it per root with `--root` to scope it to a single + subgraph. Its structural findings, such as a dangling edge, are defects, while the remainder are questions + rather than verdicts and a one-line fix will legitimately trip several of them. +. Determine if Upgrade Documentation requires the addition of a prompt that users can provide to an AI coding agent to +help them assess their upgrade task. Check the state of `docs/upgrade/prompts` to ensure there is an +`upgrade-x.y.z-helper.md` for the current version and that it is up to date/tested. When it is determined as valid, +ensure the prompt is reflected in the Upgrade Documentation itself. **This process needs to be refined.** . When all documentation changes are in place, use `bin/publish-docs.sh` to deploy a final `SNAPSHOT` representation of the docs and thus validate that there are no issues with the documentation generation process. Request review of the published documentation on the dev mailing list.
