The roadmap and Maintaining record the first dry run on GitHub's windows-2025 runner: it built Rock 21.0.2, ran SQL Server 2025, passed verify on all three packages, and passed the gate, with a 66-minute Packages job

Author: jonedmiston

docs/maintaining.md

@@ -171,7 +171,7 @@ The workflow needs the following before it can publish. A dry run needs only the
 
 #### 1. GitHub Actions minutes
 
-The repository is private, so every job uses the organization's Actions minutes, and Windows minutes cost more than Linux ones. If GitHub refuses to start jobs with "recent account payments have failed or your spending limit needs to be increased," an organization owner must fix it in the organization's Settings > Billing and plans, with a budget for Actions. This happened on 2026-10-21 and was fixed the same day.
+The repository is private, so every job uses the organization's Actions minutes, and Windows minutes cost more than Linux ones. If GitHub refuses to start jobs with "recent account payments have failed or your spending limit needs to be increased," an organization owner must fix it in the organization's Settings > Billing and plans, with a budget for Actions. This happened on 2026-10-21 and was fixed the same day. A dry run uses about 70 minutes of Windows time for each Rock release, plus a few minutes for the loader.
 
 #### 2. The Azure identity
 

docs/roadmap.md

@@ -37,9 +37,9 @@ Where the project stands: the team's working list. Update this page whenever som
 
 - **The Sample Data Installer block in Rock**, built in the Rock repository against the loader package. It shows Core 1, Core 3, and Full 7 as cards from the dataset catalog and downloads the chosen package from a hosted `index.json`, beside the old sample data block.
 - **Communications** (decisions 90 to 96; see [Communications](communications.md)). Email, texts, and push with very large mass sends, opens and clicks, SMS conversations, one-to-one messages, and messages tied to steps. Slice 1 is written on the `communications` branch: the design, calibration part 7, and the church app stub. Next: run part 7 on calibration sources, then the setup slice.
-- **The release workflow** (decisions D-release-1 to D-release-4; see [Publishing a release](maintaining.md#publishing-a-release)). `.github/workflows/release.yml` builds each Rock release in `release/rock-releases.json`, writes and verifies every package, and runs the publishing gate. On a version tag it pushes the loader to nuget.org and uploads the packages, receipts, and index to Azure, the index last. What is left:
+- **The release workflow** (decisions D-release-1 to D-release-4; see [Publishing a release](maintaining.md#publishing-a-release)). `.github/workflows/release.yml` builds each Rock release in `release/rock-releases.json`, writes and verifies every package, and runs the publishing gate. On a version tag it pushes the loader to nuget.org and uploads the packages, receipts, and index to Azure, the index last. A dry run on GitHub's `windows-2025` runner on 2026-10-22 built Rock 21.0.2, ran SQL Server 2025, passed verify on all three packages, and passed the gate. Its Packages job took 66 minutes (about 30 to build Rock, 6 for SQL Server, and 28 for verify). A self-hosted runner stays a fallback. What is left:
   - The one-time setup in [Maintaining](maintaining.md#one-time-setup): the Azure identity and its role, nuget.org trusted publishing, and the `release` environment with its approvers and variables.
-  - A dry run on GitHub's Windows runners, to prove they can build Rock and run SQL Server for verify. Until then, a self-hosted runner is the fallback.
+  - The first real release, to prove the Publish job.
   - Change the Rock 21.0.2 entry from a develop commit to its tag once Rock tags it.
 
 ## Waiting on a decision