docs: 0.1.0-alpha.3's notes - its changelog file opening with the experimental-build warning, its row, HANDOFF's alpha.3 lines, owner-only item 31 (D87) (alpha.3 PR-1) (#363)
The third alpha is the source of 0.1.0-beta.34 on .NET 11 RC3 (D87: right after beta.34, on RC3 because the train reached it before .NET 11's release on 2026-11-10). Its notes are on main as every release's are; the alpha branch takes them with the sync that follows this pull request (13_CI_CD §The alpha line). - docs/changelog/0.1.0-alpha.3.md: the experimental-build warning, the update from alpha.2 (the ledger copy, the Disclaimer 2.13 and the Privacy Policy 2.14 once, the Alpha notice's box again, schema 22 - which an alpha.2 cannot open), installing over a beta and going back, and what differs from the beta - the same as alpha.1 from beta.32. - CHANGELOG.md: its row in the Releases table. - docs/HANDOFF.md: START HERE's "0.1.0-alpha.3" lines (the sync by a merge commit, the switch unchanged, the first alpha whose ledger moves) and owner-only item 31, the third alpha on real hardware. No release line moves (README, ACCURACY, the Disclaimer's copy and LIMITATIONS keep naming the newest beta). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
44c031faca
commit
27f537a2d7
3 files changed
+61
No files matched your search
@@ -41,6 +41,7 @@ Newest first. Each file holds that release's section exactly as it stood here.
|
||||
|
||||
| Version | Date | Notes |
|
||||
|---|---|---|
|
||||
| `0.1.0-alpha.3` | 2026-11-06 | [`docs/changelog/0.1.0-alpha.3.md`](docs/changelog/0.1.0-alpha.3.md) |
|
||||
| `0.1.0-beta.34` | 2026-11-06 | [`docs/changelog/0.1.0-beta.34.md`](docs/changelog/0.1.0-beta.34.md) |
|
||||
| `0.1.0-alpha.2` | 2026-11-03 | [`docs/changelog/0.1.0-alpha.2.md`](docs/changelog/0.1.0-alpha.2.md) |
|
||||
| `0.1.0-beta.33` | 2026-11-03 | [`docs/changelog/0.1.0-beta.33.md`](docs/changelog/0.1.0-beta.33.md) |
|
||||
|
||||
@@ -148,6 +148,25 @@ the detour and 0.14–0.19 ns on the present's feature byte (#358's body; NFR-1'
|
||||
|
||||
**Owner-only:** item 30 — beta.34 on real hardware.
|
||||
|
||||
### 0.1.0-alpha.3 — the third alpha, the same day (D87)
|
||||
|
||||
`alpha` takes main at this pull request — `v0.1.0-beta.34` and these notes, no other change — by a merge commit, as
|
||||
`13_CI_CD` §The alpha line says. One file the switch holds moved on main — `legal/THIRD_PARTY_NOTICES.md`, its
|
||||
Streamline row (#358) — on a line the switch does not touch (the switch changes the *Transitive* row), so the merge
|
||||
takes both without a conflict (`git merge-tree` before the pull request); main's package set did not move, and the
|
||||
switch stays the first alpha's (SDK `11.0.100-rc.3.26522.148`, the three packages at `11.0.0-rc.3.26522.148`, the same
|
||||
NuGet licence texts) — the train reached it before .NET 11's release. Its gate on the 11 SDK must pass before the pull
|
||||
request into `alpha` is merged by
|
||||
hand (the branch has no auto-merge); the release runs from the signed tag `v0.1.0-alpha.3` on `alpha`, with its delta
|
||||
from alpha.2. Its notes are `docs/changelog/0.1.0-alpha.3.md`, which open with the experimental-build warning. It is
|
||||
the first alpha whose ledger moves (schema 22): the copy it makes first is the database as alpha.2 left it, and going
|
||||
back is to the newest beta, which opens schema 22.
|
||||
|
||||
- **The next alpha moves to .NET 11's release**: from 2026-11-10 the switch is SDK `11.0.100` and the packages `11.0.0`,
|
||||
and RC3 is out of support — move the alpha even if no beta comes.
|
||||
|
||||
**Owner-only:** item 31 — the third alpha on real hardware.
|
||||
|
||||
|
||||
## Owner-only — no PR can close these
|
||||
|
||||
@@ -372,6 +391,11 @@ the detour and 0.14–0.19 ns on the present's feature byte (#358's body; NFR-1'
|
||||
`Dlss_Basis_NeuralRendering_Format`, `Games_Filter_*`, `Games_Header_Filtered_Format`, `Filter_Clear`,
|
||||
`Compare_Filter_*`, `Compare_Count_Format`, `Compare_Count_Filtered_Format`, `Compare_ClearSelection`,
|
||||
`Compare_MidSession_Changed`, `A11y_Games_Filter_*`, `A11y_Compare_Filter_*`.
|
||||
31. **0.1.0-alpha.3 on real hardware** (D73, D87). (a) **The update from alpha.2**: Help ▸ Check for updates offers
|
||||
alpha.3 and *Restart to update* installs it; say whether it downloaded the delta or the whole package. (b) The terms
|
||||
window shows the Disclaimer 2.13, the Privacy Policy 2.14 and the Alpha notice with its box again, and Accept waits for
|
||||
the tick. (c) `%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.3.db` exists beside alpha.2's, and opens;
|
||||
the ledger it left is at schema 22. (d) Item 30's checks, on the alpha.
|
||||
**Answered 2026-08-05, do not re-ask:** remove `gameguard` and keep `guard` (approved
|
||||
over a red `Rules` gate, with the reasoning recorded in the merge commit); vendor NVAPI
|
||||
headers **and** `amd64/nvapi64.lib`; Windows 11 is the **measurement scope** only —
|
||||
|
||||
@@ -0,0 +1,36 @@
|
||||
<!-- The third alpha's notes (D73, D87), on main as every release's are; the alpha branch takes them with its sync. CHANGELOG.md lists every release. -->
|
||||
|
||||
## [0.1.0-alpha.3] - 2026-11-06
|
||||
|
||||
> ⚠ **EXPERIMENTAL BUILD — YOU USE IT AT YOUR OWN RISK.** This is an **alpha**: the source of `0.1.0-beta.34` built on
|
||||
> **.NET 11 Release Candidate 3** (SDK `11.0.100-rc.3.26522.148`, runtime `11.0.0-rc.3.26522.148`), a version of .NET
|
||||
> Microsoft has not finished, with the C# 15 compiler. It has not been tested the way a beta is, and it can crash, record
|
||||
> wrongly or fail to update in ways no beta has. **If you want results you can rely on, use the beta.** Before it runs it
|
||||
> shows the *Alpha notice* (`legal/ALPHA_NOTICE.md` 1.0), which you must accept, with its own box to tick.
|
||||
|
||||
**The third alpha: `0.1.0-beta.34` on .NET 11 RC3** — DLSS 5 and DLSS 4.5 named from what the game and the driver did,
|
||||
filters on Games and Compare, and a Games page that opens at once (the beta's notes, `docs/changelog/0.1.0-beta.34.md`,
|
||||
say what that brings). What an alpha is and how to go back: the user guide's *Alpha builds* page
|
||||
(`guide/11-alpha-builds.md`), and the *Alpha builds* section of `LIMITATIONS.md`.
|
||||
|
||||
**Updating from `0.1.0-alpha.2`:** Help ▸ Check for updates, then *Restart to update* with no game running — an alpha
|
||||
updates only to newer alphas. Before it first opens your database it copies it to
|
||||
`%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.3.db` (the newest three copies are kept). The terms window
|
||||
shows the **Disclaimer 2.13** and the **Privacy Policy 2.14** once and, as every time an alpha's terms window opens, waits
|
||||
for the Alpha notice's box to be ticked again; the notice itself stays 1.0. The ledger moves to schema 22, which an
|
||||
alpha.2 cannot open (the copy is the database as alpha.2 left it; going back is to the newest beta, which opens it); the
|
||||
detection rules move to `2026.11.2`.
|
||||
|
||||
**Installing it over a beta:** download `FrameLedger.App-alpha-Setup.exe` below, verify its hash against
|
||||
`SHA256SUMS.txt`, and let it replace the FrameLedger already installed; the Alpha notice is shown first. **Going back:**
|
||||
install the newest beta's `FrameLedger.App-win-Setup.exe` over it; your database stays where it is.
|
||||
|
||||
**Windows and your PC:** as for the first alpha — Microsoft supports .NET 11 on Windows 11 24H2 and later, and on Windows
|
||||
10 only in its LTSC and IoT editions; it needs a processor with SSE4.2 and POPCNT. .NET 11 RC3 is supported until .NET 11
|
||||
ships (10 November 2026); the next alpha moves to the final release.
|
||||
|
||||
### What differs from 0.1.0-beta.34
|
||||
|
||||
The same as `0.1.0-alpha.1` differed from `0.1.0-beta.32` (`docs/changelog/0.1.0-alpha.1.md`): the runtime and the
|
||||
compiler, the three libraries serviced with the runtime, what .NET 11 itself changes — and the part of FrameLedger loaded
|
||||
into a game is the beta's.
|
||||
Reference in new issue
Block a user