Repository navigation
0.8.0: Release 0.8.0 #93
Description
Release: 0.8.0.
Owners: Anders (@andersalm) and Sasha (@SashaMIT). Required.
Goals, scope and release order: milestone 0.8.0. After the first signed install everything comes from inside ElastOS (#217).
Test releases (0.8.0-alpha.N) vs final 0.8.0
Canaries (0.8.0-alpha.N) come from develop. Each gets one comment here naming the exact commit, its accepted scope and its gates: develop CI on that commit, the named installed journey, signed canary publication, Anders's and Sasha's runs. Release notes for every canary are in elastos/CHANGELOG.md; the newest 0.8.0-alpha.N comment here names the latest canary. A canary does not tick any box below; the boxes are the final 0.8.0 gates.
Done means
Release acceptance: Each exposed feature works clearly from start to end, including recovery. Keep unfinished or confusing features hidden until their complete journey passes. Hiding a feature does not complete its task; source checks alone do not establish installed acceptance.
- Every goal issue's Done means passes on one release candidate, including Home on phones (Required: Home on phones #92).
- Isolation: S0 (except Seed: run the seed service under its own account without sudo or Docker #174, moved to 0.8.1) plus honest docs (State actual isolation in docs, manifests and release notes #170); S1-S2 in 0.8.1 (Required: Isolation as promised #173).
- The release PR to main passes the required checks and one approving review.
- Source version, tag, platform artifacts and signed release agree on 0.8.0
and the exact source commit. - The 0.8.0 release installs fresh, and the last alpha updates to it in System, with Undo working, on Mac, Linux x86-64 and Jetson. Test: on each machine, run the install command on a clean account. On a Home on the last alpha, update in System, then Undo, then update again; sign-in and data are kept.
- Existing stable-channel installs signed by the retired key (0.7.1 and earlier) reach 0.8.0 by re-running install.sh, which re-trusts the new maintainer key (Replace the maintainer release key and keep signing off the public server #186, 0.8.0 publication: sign one release for both stable and canary #335); proof on Mac, Linux and Jetson. Test: on Mac, Linux and Jetson with 0.7.1 installed, re-run the install command; it installs 0.8.0 and keeps identity and data. (Moved from G1 Install and update: Signed update #89 on 7 Oct: canary cannot carry it.)
- GitHub (main, tag) and signed distribution refer to the same accepted release inputs. (Moved from UP-06: Produce the exact signed test candidate #112 on 8 Oct: main and tags change only at the real 0.8.0 release.)
- Anders approves the exact publication and seed change. The release
custodian signs the accepted build. The seed publishes and runs it; website
installs work. - Sasha accepts the final experience, approves the final user-facing release text and publishes the release summary.
The current milestone and the goal issues own the remaining work. #410 owns the Community first-run repair. Accepted After 0.8.0 deferrals keep their recorded scope; the approved post-publication checks remain required.
Acceptance record
- Candidate (21 Oct): the alpha.25 train
release/train-0.8.0-rc10, current local headeaf6c6f8874cda99107c9474e4dbb2ea0d1aa23b. This is the only place the candidate head is recorded; goal issues point here. More reviewed fixes may follow until the Fri 23 Oct 16:00 UTC freeze. The published canary is 0.8.0-alpha.24 at3beb816438fd567145a8d725e22465bd83277cf0. - Exercised checks: the train Linux pre-push gate passed on
eaf6c6f88(24m28s,release-train-0.8.0-rc10-20261021-113720.log). Since the earlier PASS on7823a7334, the train adds smoke test commits (0fe1cf34f,6891cb5e5,a678c17f6), the First-time setup dead-ends at the passkey step on Windows and Linux #452 board security-key doc (f40c1036e, Codex doc452 PASS) and the Assistant Copy fix (5a816608f,eaf6c6f88, Codex copy1 FAIL, then copy2 PASS). These are source results; installed and device acceptance remain separate gates. - Latest status: coherency audit 21 Oct 00:18 UTC, train update 21 Oct 04:33 UTC, train update 21 Oct 06:26 UTC. Earlier candidate records (alpha.22
9be009b17, alpha.2363f57e341, rc10f674ff637) remain in the comments above for history. - Decisions: Anders signs alpha.25 and 0.8.0 himself, as for alpha.24; the separate signing account (Replace the maintainer release key and keep signing off the public server #186 Box 1) moves to after 0.8.0 (decision). The repo move to
elastos/elastos-runtimeis on hold: Anders presents the plan first and then decides the timing (21 Oct). The earlier after-publication plan (6282268533) is history. Hosted AI (0.8.0: Hosted AI with owner approval #85, Mac only) is a stretch goal with cutoff Thu 22 Oct 18:00 UTC. - Reviews: by Wed 28 Oct Irzhy (
irzhywau) reviews PR Release 2.0.0 (source 7bc3704b5, package run 41375420248) #375 (formal release review for the frozen candidate, existing request), Home cannot start, update or show Recovery with a file over 16 MiB (or 64 MiB total) in Library folders #444 and 0.8.0: Hosted AI with owner approval #85. - Installed evidence: goal issues retain their accepted receipts. Carry a result only after checking the final candidate's changes to that journey. Installed acceptance on signed alpha.25 is pending.
- Remaining gate: the Done means above still apply. Freeze one reviewed candidate, qualify the exact develop source and matching package, and complete the affected installed journeys. Seed reboot (G2 Getting connected: Seed safe and reliable #83), Jetson fresh install (G1 Install and update: Install, sign in and recover #88) and the named offline update check (UP-07: Accept updates on Mac, Linux and Jetson #113) retain their approved post-publication order.
- Next owner: OMP owns source integration, the push gate and build coordination. Anders signs. Exact publication, main/tag and seed approvals remain separately required; Sasha owns final experience acceptance.
Activity
andersalm commentedon Sep 29, 2026
Retained integrated-release checks: exercise unsaved drafts, concurrent document saves, deep links, picker acknowledgements, approval handoffs, visible app launch, focus/close and repeated System Save. Report source, installed and human results separately.
Remote inference, remote Browser composition, group identity, Windows support and executable-Component adoption need their own later scope and owners. Historical notes do not add them to the current release. Product writing should explain Runtime authority, identity, content and transport separately and tie support claims to the accepted release. GitHub issues now own the work record.
andersalm commentedon Sep 29, 2026
Irzhy, please confirm this proposed tidy-up of Project #3. The changes below wait for your approval.
Put Followup Release 0.7.1 — Protected Content Follow-Up #51, feat(protected-content): provision installed custody and chain prerequisites #52 and 0.7.1 integration: protected-content provisioning, Home first-run seed, Home Agent on the typed model contract #58 in milestone 0.7.1 because the 0.7.1 code depends on them. feat(protected-content): provision installed custody and chain prerequisites #52 and 0.7.1 integration: protected-content provisioning, Home first-run seed, Home Agent on the typed model contract #58 are already merged, so keep them Done. Add milestone 0.7.1 to fix(update): observe isolated Mac hop accurately #79 and Bind local chat to engine context limits #80; both already belong to the project. Remove the 30 September 2026 due date and agree on a date at Friday's meeting.
Add Protected-content UI/UX parity gaps vs feat/dkms-esp-port: protect any file type, Creator app, open-through-decryption #42 to Project [PARKED — v0.3.2+ track] Mac VZ branch refresh against v0.3.0 (rebase complete, not for v0.3.1 merge) #3; its link under protected-content parent After 0.8.0: Protected content #91 is already in place. Add Protected content: align expiry deadlines when resuming Wallet approval #81 and Protected content: resume playback after pending Wallet approval #82 to milestone 0.7.2 and Project [PARKED — v0.3.2+ track] Mac VZ branch refresh against v0.3.0 (rebase complete, not for v0.3.1 merge) #3, as sub-issues of After 0.8.0: Protected content #91.
Change the base of Fix/0.7.1 security #76 to
feat/0.7.1-integration. It currently targetsupstream/0.7.1-dev, the same base as Integrate 0.7.1 setup, local models and unified Assistant for review #64, so its review includes changes inherited from Integrate 0.7.1 setup, local models and unified Assistant for review #64. The proposed base lets reviewers see the security changes against the integration work they depend on.Use these status definitions: Backlog = planned; In progress = draft or active; QA / Review = ready for review; Done = merged or included; Abandoned = closed without landing. Apply these definitions consistently, including In progress for draft PRs Fix/0.7.1 security #76, fix(update): observe isolated Mac hop accurately #79 and Bind local chat to engine context limits #80.
Ask the authors to close the included or replaced PRs: Irzhy (@irzhywau), dKMS/dDRM foundation on the ESP substrate (inspired from flint-5.0) #15, feat(logger): port elastos-logger crate from PR #15 #25 and feat(protected-content): installed inactive e2e proof — three custody replicas + repair after loss (ELACITY-2298) #60; Sasha (@SashaMIT), feat(model-provider): offers/runs contract, openai_compat + h3_video adapters (stacked on collaboration-candidate) #17, feat(content): gba-nonogram content capsule on 0.7-dev #26, 0.7.1 candidate review: Assistant mode controls, Library dark menu, window snap, light-bar logo #65, docs(roadmap): plan attested hosted inference as a model-provider backend #66 and Alignment gate: two-platform installer contract, shared Browser revision 2.1, stale passkey wording #69; Anders (@andersalm), docs: reconcile the 0.7.1 release queue around five user journeys #63. feat(protected-content): installed inactive e2e proof — three custody replicas + repair after loss (ELACITY-2298) #60 is included through Integrate 0.7.1 setup, local models and unified Assistant for review #64. Each author should record where the work landed or what replaced it. Use Done for included work and Abandoned for work replaced without landing.
Keep only three views: 0.7.1, 0.7.2 and My items. Create the two milestone views and keep My items. Remove Backlog, Priority board, Team items, Roadmap and Focus. Priority currently has no options, and Roadmap has no dates.
This issue comment replaces the local tidy-up note. The requested changes still wait for Irzhy’s confirmation; none are applied by this migration.
andersalm commentedon Sep 29, 2026
The standing workflow is published in PR #115 at
ef208304. Its eight checks passed. GitHub issues own status, acceptance and proof. The complete-user-journey rule is in every release-row and LA/UP Done means, including the closed source-only tasks while preserving their proof limits.Useful content from 48 Markdown work notes was moved into matching issue comments or matched to existing acceptance. Those notes were deleted. Five build, reconstruction and test-kit documents remain with their artifacts. Raw receipts and the tldraw board JSON were preserved; the board hash is unchanged. Private seed security details stay private. The Project #3 tidy-up is recorded above and still awaits Irzhy's confirmation.
andersalm commentedon Sep 29, 2026
The draft v0.7.1 release now describes the user journeys in plain words and links to milestone 0.7.1. Internal status, branch stacking, board rows and run links were removed. Protected content is explicitly planned for 0.7.2. Sasha’s approval of the final text remains an unchecked acceptance item here. The release remains a draft; publication and the tag retain their approval gates.
andersalm commentedon Sep 29, 2026
Standing rules are published in PR #115, now at
ef208304. The PR changes onlyAGENTS.md.GitHub issues own work status, acceptance and proof. A final review removed the remaining ambiguity about branch selection: the owning issue records the approved base, and fetched refs verify it. The final wording passed independent review, Home entropy and diff checks. Irzhy is requested as reviewer; CI is running for the latest commit.
Useful work notes have been moved to their issues. The 47 reviewed Markdown work notes in
output/were removed. Six package, fixture or reconstruction documents remain with their artifacts. The board JSON is unchanged. The Project #3 tidy-up proposal remains here for Irzhy's confirmation.andersalm commentedon Sep 29, 2026
PR #115 at
ef208304now passes all eight required CI checks: https://github.com/Elacity/elastos-runtime/actions/runs/36607840945. Its diff remains AGENTS.md only. Irzhy is requested as reviewer.The final local cleanup check passed after the DGX kit's old note link was replaced with the evidence comment in #97. The board JSON remains unchanged.
andersalm commentedon Sep 29, 2026
Applying Anders's issue-driven workflow in PR #115: each lane takes its lowest-numbered open, unblocked task, with one active task per lane. Issues receive progress and proof before reports. Draft PRs keep review requests clear; Anders receives the reviewer names when a PR is ready. Test Homes stop when their tests end. PR #115 will merge into the approved models branch after current-candidate checks and independent review.
Project #3 cleanup belongs to #122 and Irzhy. This task will leave that cleanup to him.
andersalm commentedon Sep 29, 2026
PR #115 now contains the lane, issue-first reporting, draft-review and test-Home cleanup rules at
a8ed54239866d166075dd9c9e2edc4ca29a593de. Independent review found no issues. Local entropy, Rust formatting and diff checks passed. Current CI: https://github.com/Elacity/elastos-runtime/actions/runs/36620848639. The six specified drafts have no review requests. The approved merge target isfeat/0.7.1-models; merge follows successful current-candidate checks.andersalm commentedon Sep 29, 2026
PR #115 at
a8ed54239866d166075dd9c9e2edc4ca29a593dechanges onlyAGENTS.md. Independent agent review accepted the lane queue, issue-first reporting, reviewer handoff and test Home cleanup rules. The reported local entropy, Rust formatting and diff checks passed.CI run 36620848639 passed all eight expected checks for that exact commit:
source-gate,lint,test-elastos,test-capsules,custody-harness-smoke,source-home-linux (ubuntu-24.04),source-home-linux (ubuntu-24.04-arm)andsource-home-macos. The tag-only release publication job was skipped as configured for a PR.Anders approved a normal merge into
feat/0.7.1-modelsafter those checks and independent agent review. The target is still501b411c11d5e38e424077a03d99476172a1a77f, an ancestor of the reviewed candidate. GitHub reports a clean, mergeable PR. The next step is to mark it ready and merge through the API with the reviewed head SHA required to match. Release acceptance remains open in this issue.andersalm commentedon Sep 29, 2026
PR #115 merged into
feat/0.7.1-modelswith normal merge commitb1a22a6ec0c0aed2a8df44cc4cdf98618eadd61b. The merge API required the reviewed heada8ed54239866d166075dd9c9e2edc4ca29a593deto match. The task branch and its history remain intact.CI run 36620848639 passed all eight expected checks for that head:
source-gate,lint,test-elastos,test-capsules,custody-harness-smoke, Linux x86-64 source-home, Linux ARM64 source-home and macOS source-home. The tag-only release publication job was skipped as configured. Independent agent review accepted the final policy changes. Anders authorized this docs-only merge into the models branch.The base advanced from
501b411c11d5e38e424077a03d99476172a1a77ftoe80269cefb63626f4db8cff82d7d972f3d48b502through PR #119 between the final base check and the merge. Post-merge verification confirmed that both base commits had identicalAGENTS.mdbytes. The merge adds onlyAGENTS.mdto that new base, with the exact reviewed file blob64c470978f0bad2cc35d5a2330a9f56c49e413bc. The two merge parents are the new base and the reviewed head.The agent-process change is integrated. Release acceptance and the remaining release journeys stay open in #93; this merge records policy integration and exact-head CI proof.
185 remaining items
andersalm commentedon Oct 27, 2026
0.8.0-alpha.27 replaces 0.8.0-alpha.26 as the next candidate (27 Oct, OMP)
Anders accepted alpha.26 from
5b67f035e(6448018228). Later on 27 Oct he decided to add more changes before signing: fixes from the installed review of the apps on 27 Oct, in Library, Documents, Archive, Marketplace, Chat, People and the update check, and a way to add a contact by DID. The alpha.26 signing input stays unsigned and unpublished. This decision replaces the rule of one fix-only alpha.26 (respin rule).alpha.27 builds on
5b67f035e, so the alpha.26 delta (6445346459) stays in. The alpha.27 qualification comment names the exact SHA, the train branch, the CI and package runs, and the complete delta. Anders confirms that SHA before signing, as for every candidate. The acceptance rows planned for alpha.26 move to the signed alpha.27, together with rows for the new changes. The stable security check in the plan (6420781957) runs on the alpha.27 SHA, and the dates in that plan follow alpha.27's qualification. Anders sets the new go/no-go date. The CI update journey still starts from alpha.25, the release on canary now.The train CI run on
5b67f035e(40484525098) failed in one job,source-home-linux (ubuntu-24.04). In both attempts the job stopped while it downloaded 64.8 MB of Ubuntu packages: the runner's mirror was slow, and each of the three tries reached the 90-second limit inscripts/ci-apt-prerequisites.sh. Train runs find no package cache, so they always download; develop runs restore the cache. The product code passed the other 15 jobs of that run. The train run on the parente751c2109(40457380400) and the develop run on5b67f035eitself (40494653141) passed every job. Qualification uses the develop run, and the alpha.27 train run repeats this job.andersalm commentedon Oct 28, 2026
0.8.0-alpha.27 qualified from
9693ace3f(trainrelease/train-0.8.0-rc10; alpha.26 was qualified but not signed, and alpha.27 replaces it)source-home-linuxfailed once in the installed model journey and passed on its automatic rerun) and package 40663818569 (attempt 1) attest 0.8.0-alpha.27 from9693ace3f123de913ec8e351ecf46b6fc5565136. Train CI 40656051607 PASS; musl precheck PASS; cargo-audit clean.5b67f035e), each with a cross-family review PASS, plus a Codex review of the integration (every conflict resolution) and of the notes:9693ace3fand the two commits before it: Library opens Archive again, Download file saves without leaving the page, and another Home's known device DID is refused (found by the box test on5fedd6b82).5fedd6b82: adding by DID passed end to end with Discovery off, and Chat files passed up to "File is ready"; two regressions were found, both fixed in9693ace3f. The rerun on9693ace3fis in progress.Next: the box test result on
9693ace3f, then Anders confirms9693ace3f, thenalpha-after-approval.shand signing.andersalm commentedon Oct 28, 2026
Signing waits for a new candidate with Anders's 28 Oct fixes (28 Oct, OMP)
alpha.27 qualified from
9693ace3f(6467379059), and Anders does not sign that build. On 28 Oct he tested a source Home built from it and asked for fixes first: the publisher labels in Marketplace, the Documents list and its status line, the shared-file prompt in Chat, and contact names and requests in People. Each fix goes onto9693ace3fafter its review passes, and the integration head becomes the next candidate. Its SHA, CI, package run and qualification will be posted here, and Anders confirms that SHA before he signs. The security check for stable (6420781957) covers the same SHA.andersalm commentedon Oct 29, 2026
Preview for testing before signing: branch
preview/080-alpha26at8557c988bis up (00:50 COT). It is the 0.8.0-alpha.26 candidate as tested on 28 Oct, minus tonight's last fixes (contacts-only sharing, Sharing dialog removed, Approval Lens and System's Apps & Services removed, entropy-review fixes). Build a separate test Home from it withscripts/build-and-setup-source-home.shand the platform restart script. Findings here, please. The final alpha.26 candidate follows on develop after qualification.andersalm commentedon Oct 29, 2026
0.8.0-alpha.26 candidate:
8a74b669c88fd462878193b7e026e64b25483465(develop, trainrelease/train-0.8.0-rc10). It supersedes the unsigned5b67f035e(old alpha.26) and9693ace3f(alpha.27); neither was signed and alpha.27 is not used. It adds Anders's 28 and 29 Oct testing fixes: People pages and add by DID, Library "Share with contacts" (contacts only, while shared; no Sharing dialog), Chat Attach in Community, Documents Autosave off, the file service offline (#498, #500), Services, Approval Lens and System's Apps & Services hidden, a smaller default install (hidden components stay installable with--with), and the Chat unread fixes (direct and Community).Evidence so far:
9693ace3fto8a74b669c:a28integ1FAIL atfbd5bd166(one release-note claim; the clause is gone after7dbe65cc3).a28integ2PASS onfbd5bd166..6d96323a6.a28integ3FAIL on6d96323a6..d6723712e: the Unpublish claim (closed by1e5bf1766, read ina28integ4) and a contact-removal retry (closed by the contacts fix;dupe4PASS, picked as05f375e30).a28integ4FAIL ond6723712e..5f65bee37with one release-note finding ("Stop sharing" needed the identical-file exception);notes2PASS on372fb40f1closed it.ci1FAIL at57627f88con the canary workflow fixture, moved to G1 Install and update: Signed update #89 (comment 6496632905) as a gate before the release PR to main. Lane reviewsunread1andinstall1FAIL;final2SOURCE PASS on57627f88c..cc7a9bc94closed both.final3SOURCE PASS oncc7a9bc94..8a74b669c.57627f88c: success (Apple silicon, Linux x86-64 and ARM64, seed).57627f88c: 15 jobs passed, 1 failed, 1 skipped. The failed job istest-capsules(a Library smoke fixture). The fixture fix is the candidate's last commit; the qualification CI below checks it.test-capsulesfixture and alsosource-home-linux (ubuntu-24.04): the installed Marketplace Get and Assistant reply journey stopped with "finite journey live child left its unit census". Its cause is not yet proven (#433 6501731773).8a74b669c(author run): source Homes built on a Namespace Linux box, three Homes and a local Community node. 129 checks passed, 1 failed and 14 were not reachable; findings: 0 blocker, 1 bad, 5 polish. Journeys 2 to 8 passed (Community Attach, Stop sharing, non-contact refused, no-session reads refused, Documents row actions, add by DID, System trims). The unread-dot check (direct and Community) and the fresh-install check also passed. A source Home has no signed model catalog, and the update journey was out of scope for this run. Journey 1 (share a .md with contacts, the contact saves it to Library and downloads it) failed at Save to Library. Its cause is not confirmed; the author suspects from the video that the click landed on the window above Documents. Journey 1 stays open until its focused rerun returns. Installed acceptance with the release installer is a separate check.Known and tracked: #497, #498, #500, #505.
andersalm commentedon Oct 29, 2026
0.8.0-alpha.26 qualified from
8a74b669c88fd462878193b7e026e64b25483465(18:10Z): develop CI 40916013126 success (attempt 1) and package 40916022132 (attempt 1) with both Linux musl jobs bound to this version and commit; the Namespace musl precheck on the same commit also passed. Final box runs on this commit (explore-source-8a74b669c-localcommunity-20261029T1626Z and …T1740Z, 3 Homes + Community node): all 10 journeys PASS; polish in #506. Next: Anders's approval of this exact SHA, then the seed upgrade, the offline-Kubo seed checks, signing and canary.andersalm commentedon Oct 29, 2026
0.8.0-alpha.26 ready to sign (18:45Z) after Anders's approval of
8a74b669c88fd462878193b7e026e64b25483465: the seed runs this release's Runtime with Kubo offline; a fresh Ubuntu 24.04 install throughinstall.shagainst it installed 0.8.0-alpha.25 (37 components) andelastos update --checkfetched the signed head over Carrier. Unsigned input prepared (signing-input.json sha2562668bee1ea3821123cad1af13e4b4d72eb8456da8106f6824017973d5d907c7a). Next: signing, verification, the Community node upgrade and an add-by-DID check, then canary.andersalm commentedon Oct 29, 2026
0.8.0-alpha.26 is live on canary (public head names it at 20:05Z): release
Qme6gL354vXFPEyhDuod2u89JgVw6GBTh8UZrj5FKZYyXj, headQmcMDQ4ycMvb9pRFgrFctfywsAPTDTn6pj5AJNDHUgYeLb(previous alpha.25QmVAGsL25vrRftVC2UoBSfABmP9EZ21aD6Zz7rg7DdafB1). The served release-head.json and install.sh are byte-equal to the signed set; verify-signed 10/10 before publication.Seed acceptance:
elastos update --checkpassed.elastos.communitywith two fresh Homes from8a74b669c(run explore-source-8a74b669c-20261029T1912Z): add by DID delivered in 20.1 s and accepted; a Community post arrived in 3.7 s.elastos --version0.8.0-alpha.26).8a74b669c(CI 40916013126) passed the update from the published alpha.25 to a CI-signed build of this source. verify-signed includedinstall-release --checkfrom alpha.25.The publish first stopped because the seed's disk was 99% full with old release staging. Old staging (alpha.7 to alpha.22 and older upgrade inputs) was removed; the removal did not touch the seed's Kubo repository, which stores its own blocks (filestore off). The publication script stops the seed's Home service while it writes. After the first attempt, the service started again at 19:46:51Z. During the second attempt, a box check got two 502 answers from the public release head before it named alpha.26. Continuous availability was not measured. For the intermittent
source-home-linux (ubuntu-24.04)census failure, the evidence points to the CI harness, not the product (#433 comment 6505709156).Update 30 Oct 01:04Z, signed update and Undo through the live seed (Linux x86-64, fresh Ubuntu 24.04 container on a Namespace box):
install.shinstalled 0.8.0-alpha.26;elastos update --rollback-to QmVAGsL25vrRftVC2UoBSfABmP9EZ21aD6Zz7rg7DdafB1installed 0.8.0-alpha.25 (rc 0);elastos updatethen installed 0.8.0-alpha.26 (rc 0) and--checkreports it up to date. Versions only: Home was not started in this container, so no sign-in or data checks. Anders's own canary Home update (start version, result, final version, Home opens) is still to be recorded here.Update 30 Oct 01:32Z, end-to-end test of the published releases (run explore-0.8.0-alpha.26-20261030T0122Z, Linux x86-64, two Ubuntu 24.04 containers on one Namespace box, live elastos.community): a Home on 0.8.0-alpha.25 (installed, then
--rollback-tothe signed alpha.25 head) with an account, a Document, a Library file, a Community post and a Profile name updated to 0.8.0-alpha.26 through System > About > Update in 43.7 s; it came back signed in with all four kept. The test browser used a virtual passkey, so no passkey dialog was visible at the approval step. A fresh install took 66 s through first open, sign-up and the Recovery Kit prompt. Between the two Homes: add by DID delivered in 21.3 s; direct messages both ways; a file shared with a contact opened in Documents; after Stop sharing a new fetch is refused and an already fetched copy opens; a Library file posted in Community reached the other Home; unread dots clear when the conversation opens. Corrected 30 Oct 02:09Z: The tester reports 47 steps passed in the tested scope. Saved Library required Refresh; #506 remains open. The first Community-file FAIL was reassessed by the author as a wrong expected file. Not tested on the signed release: Mac and Jetson, Undo with a running Home, Recovery, the passkey prompt at Update, Assistant, Browser, local and hosted models, large Library files and network changes.andersalm commentedon Oct 30, 2026
Installed acceptance, Jetson (aarch64), signed 0.8.0-alpha.26 (
8a74b669c, canary headQmcMDQ4ycMvb9pRFgrFctfywsAPTDTn6pj5AJNDHUgYeLb), 30 Oct 11:01-11:19 UTC, over SSH. The device was already on alpha.26 with Home running (port 8090 answering), so the starting alpha.25 state was made with Undo.elastos update --head-cidalpha.25 head--rollback-toalpha.25 head, Home runningelastos updatealpha.25 → alpha.26QmcMDQ4y…update --checkelastos updateNot covered here: sign-in and data checks in a browser (no before-and-after data comparison was taken), Recovery, models. A terminal update or Undo stops Home and prints the command to start it again; it does not restart Home itself (#509, for 0.8.1). Two processes from 16 Oct (an earlier update controller and its restart script) are still running on the device; they did not interfere.
andersalm commentedon Oct 30, 2026
Installed acceptance, Linux x86-64, signed 0.8.0-alpha.26 (
8a74b669c, headQmcMDQ4ycMvb9pRFgrFctfywsAPTDTn6pj5AJNDHUgYeLb), 30 Oct 11:03-11:22 UTC: two fresh Ubuntu 24.04 containers on a Namespace box, installed with the public install.sh (66 s and 64 s), liveelastos.community, headless Chromium with a virtual passkey. Adds to the end-to-end run in comment 6507156249.elastos update --rollback-tothe alpha.25 head exited 0 after 50.5 s and left Home stopped with the command to start it; started by hand, Home came up on alpha.25 still signed in, data kept, the DID-added contact hidden as documented. System > About > Update back to alpha.26 took 41.8 s; signed in, data kept, the contact back.Not covered: restoring from a Recovery Kit; the old unencrypted file that needs migration (#444 set); several GiB in total (this run had 360 MiB of files, 482 MB on disk). A terminal update or Undo stops Home and does not restart it (#509, for 0.8.1).
elastos source showprintsHead CID: unknownright after a fresh install, as INSTALL.md describes; after a System update it shows the head.Added 30 Oct (OMP): script flags checked against the evidence. The test script marked six steps as failed. Three Recovery status steps expected a status label: at
8a74b669c, System shows an empty label once the Kit is set up and can be downloaded (capsules/system/browser/system.jslines 2780-2781), and each of the three showed the protected-folder report with no error. One Document step expected "Saved" in the status line; the same Document was found on alpha.25 and again on alpha.26. The two Undo steps record the terminal stop in #509.andersalm commentedon Oct 30, 2026
Stable security check, timing changed: grook recorded at 06:16 COT today (30 Oct) that, by Anders's decision, the ElaWarden rescan of
8a74b669cis done after the release, not before the 0.8.0 go/no-go. It replaces the "before the go/no-go" timing in comment 6420781957 (the owners and the per-finding Codex call stay; part 1 there, the High findings with no hold and the #444 auth review, was done earlier). Each finding from the rescan still gets its hold or no-hold call, and every hold gets a fix, in 0.8.1 or a later fix release. This check stays open here until those calls and fixes are recorded.andersalm commentedon Oct 30, 2026
Later decision, 30 Oct: Anders chose 2.0.0-rc.1 for the next test-channel candidate, replacing the alpha.1 name in the earlier plan below. Wallpaper, finished Assistant replies and proper Browser resizing remain open until their complete journeys pass. Renaming the candidate approves no source commit; all existing release gates remain.
Update 30 Oct (OMP): new alpha, release Monday as 2.0.0.
Anders decided on 30 Oct: the UI problems in #511 go into a new alpha, and the stable release moves to Monday 2 Nov under the name 2.0.0 instead of 0.8.0. The new canary is 2.0.0-alpha.1, so testers update across the same version jump as the stable release. Monday is a target, not a commitment: it holds only if the checks below pass.
What changes in the plan above:
fix/a26-ui-findings) and the version rename. The alpha.26 package run is no longer the stable input; one new package run builds 2.0.0-alpha.1 and 2.0.0 from the new commit.The rows in this plan stay: installed acceptance on the new alpha (Mac, Linux and Jetson, including Anders's own update), the 0.7.1 reinstall path, the group's testing, go/no-go, an approving review of #375 on its new head, the main merge and the v2.0.0 tag before stable prepare and signing, then the checks after publication. The security rescan still runs after the release, now on the 2.0.0 source. The alpha.26 results stay on record as evidence for the code the fixes do not touch.
Update 30 Oct: rc.1 and remaining qualification. The requested canary name is now 2.0.0-rc.1, replacing 2.0.0-alpha.1 in the plan above. The successor is still being assembled; the prior candidate is not an accepted stable package input. The successor push stopped at the committed behaviour gate. Its replacement still needs exact-head review, completed checks and packages, and installed acceptance. Build capacity admission also remains open: available space above the reserve does not establish the next command's expected peak. The integration owner must record that admission under the shared build lease before further allocating build work. Browser resizing remains work in progress, with no approved postponement. Earlier signing-time estimates are withdrawn. All existing release acceptance, approval and post-publication duties stay in force.
andersalm commentedon Oct 31, 2026
2.0.0-rc.1 qualified from e4179b0: develop CI 41175923006 (attempt 2; test-capsules first failed on a runner out of disk) and package 41175925539, both green, including Mac and both Linux musl builds.
Not in rc.1: the installer folder repair (#368) and Browser free resize (#87); both stay required for 2.0.0. Signing waits for Anders's scope decision and exact-SHA approval.
andersalm commentedon Oct 31, 2026
2.0.0-rc.1 is on canary (31 October 2026, about 15:00 UTC).
andersalm commentedon Nov 2, 2026
2.0.0 stable published (2 Nov 2026)
7bc3704b5e181e5aa435c2b2cafbd73a996932ef, tagv2.0.0on that commit; package run 41375420248; release-package PR Release 2.0.0 (source 7bc3704b5, package run 41375420248) #375 merged into main (review rule lifted once, restored and verified).verify-signed.sh 2.0.0 2.0.0-rc.2: 10 PASS, VERIFIED.QmfKYcyaECzckWSHHXbWTdQHc4FNRQXjz2vh3YQ4RCQon8, headQmYbAEVvKj9B6zi3Au3XfwssU2ukH3VsPz5BFMdmiK4A7j, previous head rc.2Qmea2gPE.... Servedrelease-head.jsonandinstall.shbyte-equal to the signed files. Website deployed from v2.0.0, every served file equal to the source (install-heading padding fix deployed after, PR from fix/website-install-heading).Checks after publication (real installs from the live seed)
elastos source switch-channel default canary; without it Undo is refused by the channel guard (stable Home, canary head)elastos updaterc.2 -> 2.0.0LC_ALL=C(channel stable, Home healthy, passkey kept); without it refused, #517elastos updaterc.2 -> 2.0.0Logs:
~/omp-inbox/install-review/stable-runs.md(Main's Mac).New issues found today
LC_ALL=C).