Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[docs-scanner] Scout release notes use future tense for completed retirements

Geschlossen Anfängerfreundlich
  • Stimmt etwas nicht?
#26,211 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
1/5
Geschätzter Aufwand
Unter einer Stunde
Anfängerfreundlichkeit
90/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
docker
Bereich
documentation

Rechercherichtung

Öffne content/manuals/scout/release-notes/platform.md und vergleiche den Eintrag vom 2026-07-01 mit den späteren Einträgen zur Einstellung vom 2026-07-30 und 2026-09-01. Aktualisiere oder entferne die früheren Deprecation-Hinweise, sodass die Release Notes die abgeschlossenen Einstellungen korrekt beschreiben und nicht länger den Eindruck erwecken, dass sie noch ausstehen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

File: content/manuals/scout/release-notes/platform.md

Issue

The Q2 2026 section (dated 2026-07-01) describes feature retirements using future tense, even though later entries in the same document confirm these retirements have already occurred:

The following is deprecated and will be retired on July 30, 2026:

  • Slack integration: Vulnerability and policy compliance notifications to Slack channels.

The following are deprecated and will be retired on September 1, 2026:

  • Notifications: In-product and email notifications about newly disclosed CVEs.
  • Amazon ECR integration: Automatically analyzed images pushed to ECR registries.
  • Azure Container Registry integration: Automatically analyzed images pushed to ACR registries.
  • Policies page in the Dashboard: Provided a visual interface in the Docker Scout Dashboard for tracking policy compliance.
  • SonarQube integration.

However, the document's own later entries (2026-07-30 and 2026-09-01) confirm these features were retired:

2026-07-30

The following Docker Scout feature was retired:

  • Slack integration: Integrate docker scout cves or docker scout policy into your CI pipeline...
2026-09-01

The following Docker Scout features were retired:

  • Notifications: In-product and email notifications about newly disclosed CVEs.
  • Native Amazon ECR integration: ECR is still supported using [docker scout watch]...
  • Native Azure Container Registry integration: ACR is still supported using the same options as ECR.
  • Policies page in the Dashboard: The docker scout policy command replaces this...
  • SonarQube integration.
Why this matters

Readers consulting the release notes to understand the current state of Docker Scout features will be confused by the 2026-07-01 entry saying features "will be retired" on dates that have already passed. This makes it unclear whether these features are currently available or not, forcing readers to scan through the entire document to reconcile the conflicting statements.

Suggested fix

Update the 2026-07-01 entry to use past tense and clarify that these deprecation notices were announcements made at that time, with the actual retirements occurring later. For example:

The following feature was announced for retirement on July 30, 2026 (retired as of that date):

  • Slack integration

The following features were announced for retirement on September 1, 2026 (retired as of that date):

  • Notifications
  • Amazon ECR integration
  • Azure Container Registry integration
  • Policies page in the Dashboard
  • SonarQube integration

Alternatively, consider removing the 2026-07-01 deprecation notices entirely since the actual retirement entries (2026-07-30 and 2026-09-01) provide the complete information readers need.

Found by nightly documentation quality scanner

Vorherrschende Sprache
Markdown
Sterne
4.7k
Forks
8.5k
Ø Merge
1 T. 21 Std.
Gemergte PRs (30 T.)
140

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus docker/docs

Alle Issues in docker/docs

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.