Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Foundation I: make download, installation and update recovery clear

Aperta
  • Qualcosa non va?
#287 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
html, javascript, swift
Ambito
desktop, documentation, release

Direzione di ricerca

Start with section 6 of docs/mac-foundation.md, then read WorkbenchUpdates.swift, WorkbenchUpdateDriver.swift, site/index.html, site/release.mjs, docs/updating.md and the existing release/installer tests. Implement the decided download, installation and update-recovery scope without replacing Sparkle or the signed release workflow. Done means meeting I1/I2/U2 with the specified fresh-install and signed-update evidence, including failure, retry and data-preservation checks.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Complete the customer journey from the public Workbench download to a correctly installed app, and make installation/update refusal understandable without losing the working app or saved material. This closes package I of the focused Mac foundation under #7. It does not replace Sparkle or the signed release workflow.

Decided scope

  • Keep the signed/notarized ZIP, the existing Workbench/Sparkle update owner and current release pipeline. Consume merged #271's one-action update UI.
  • Align the landing/download/help copy with released hardware/OS requirements, version and edition. First install uses the person's home Applications folder; replacement keeps the existing Applications location, including /Applications. Give exact Finder directions without requiring Terminal or knowledge of ~. Do not silently move/delete duplicate installations or migrate Preview data into Stable.
  • Correct unverified setup-duration promises. The primary ordinary update is Update to [version]; Settings remains the place for manual checks/preferences. A first non-speech job must not trigger model setup.
  • Known Downloads/read-only/translocation refusal gives quit, move, reopen and retry instructions using the existing surface. Authorization refusal leaves the prior app/data usable and offers a deliberate retry/help route. Distinguish known network, disk, signature and compatibility errors; unknown failure is not proof of corporate policy. No authorization loops or security-setting bypass.
  • Existing busy deferral, save-before-restart, retained user update preferences, exact edition/signing identity and previous-package recovery remain authoritative. Failed/cancelled download or replacement never claims the installed version changed; post-relaunch verification establishes success. Binary rollback must respect storage compatibility.

Acceptance

I1/I2/U2 in docs/mac-foundation.md are required before calling this complete. Observe a real browser-downloaded install on a suitable fresh account/environment, open the actual installed edition, perform the chosen useful job and reopen its saved result. Separately verify an actual old-to-new signed Sparkle update, busy/failed-save deferral, refusal/cancellation/retry and preserved data/preferences. Tests cover typed failure/unknown cases; native evidence covers applicable real location/authorization/relaunch behavior. No account-free first-use claim is established by an already trusted developer Mac.

Record source, edition, build, archive identity, environment and exact limits in #7's existing release evidence. Older #134 update evidence is valuable but not automatic acceptance of #271 or a newer candidate. #2 is contributor fresh-clone setup and remains separate. #15 owns speech download/first-use; #165 owns manual copy/paste; #282 owns the small receipt gate, not this UI implementation.

Implementation starting points: WorkbenchUpdates.swift, WorkbenchUpdateDriver.swift, site/index.html, site/release.mjs, docs/updating.md, existing release/installer tests. Layout and error factoring remain flexible. No custom installer, DMG migration, new settings section, background monitor, account or telemetry.

Specification and evidence: docs/mac-foundation.md section 6 and docs/research/mac-foundation-2026-10.md coverage audit. This issue is build-ready scope, not a claim the changed experience is implemented or natively accepted.

Lingua principale
Swift
Stelle
0
Fork
1
Merge medio
12h 29m
PR unite (30g)
201

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Ship-Work/workbench

Tutte le issue di Ship-Work/workbench

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.