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 8b977a16c8bbf6b7b8d3e6f280b689e1bbfa25ee Merge: f15456e919 b11f6702b4 Author: Stephen Mallette <[email protected]> AuthorDate: Mon Aug 10 12:37:56 2026 -0400 Merge branch '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 5d9cc6bb44,ac12100d2d..1ddec85bcb --- a/docs/src/dev/developer/release.asciidoc +++ b/docs/src/dev/developer/release.asciidoc @@@ -366,7 -362,33 +377,30 @@@ the help of a PMC member for those step .. Update version numbers in `gremlin-examples/gremlin-dotnet/*/\*.csproj` to reference the new release version .. Update version numbers in `gremlin-examples/gremlin-go/go.mod` to reference the new release version .. Test that all root-level examples work correctly with the new published versions + . Perform beads administration tasks, as described in <<beads,Using Beads>>: + .. `bd dolt pull` to take in anything other committers have pushed. + .. Confirm that every subgraph belonging to the release is `pinned`. The pre-flight check should already + have established this, so anything still closed and unpinned at this point is work whose record was + never finished. + .. `bd gc --skip-decay --dry-run` to preview, then `bd gc --skip-decay --force` to reclaim storage. This + discards only chunks that nothing in the database can still reach. Beads, their field content and the + full Dolt commit history all survive, and `--skip-decay` is what holds back the single phase that would + delete beads. Expect the first run to recover a large fraction of the database and later runs + progressively less. + .. Note that the output of the previous step announces a phase named "Compact", which reports how many + commits are in history and squashes nothing. Squashing requires `bd compact` or `bd flatten` run + deliberately, and neither belongs to routine administration. There is no flag that suppresses the + reporting phase, as `--skip-dolt` suppresses only the reclamation that follows it. + .. `bd dolt push` to publish the result. + + + NOTE: `bd gc --skip-decay` is the only beads maintenance command that is run as routine administration. + `bd prune` and `bd purge` delete beads, `bd flatten` and `bd compact` discard commit history, and a bare + `bd gc` deletes every closed bead past its ninety day threshold. None of them recover storage that + `bd gc --skip-decay` does not, because deleting a bead writes a further commit rather than removing the + earlier ones. A bead left closed but unpinned is also far more likely to be a record nobody finished + pinning than one that deserves deletion. Should beads ever warrant removal, that follows the same path + as removing dead branches, which is a generated list posted for review on the dev mailing list. . Generate a list of dead branches that will be automatically deleted and post them as a DISCUSS thread for review, then once consensus is reached removed those branches. -. Set up the IO tests for the current `SNAPSHOT` as discussed in the <<io,IO Documentation and Testing Section>> - -Apache provides access to download statistics for release link:https://logging1-he-de.apache.org/stats/[here]. [[email-templates]] == Email Templates
