Skip to content

docs(boost): sync RHDHPLAN-1508 OpenSpec from feature refinement - #5414

Merged
johnmcollier merged 2 commits into
redhat-developer:mainfrom
johnmcollier:codex/sync-rhdhplan-1508-openspec
Nov 3, 2026
Merged

johnmcollier merged 2 commits into
redhat-developer:mainfrom
johnmcollier:codex/sync-rhdhplan-1508-openspec

Conversation

@johnmcollier

@johnmcollier johnmcollier commented Oct 30, 2026 •

Copy link
Copy Markdown
Member

Summary

Sync the merged RHDHPLAN-1508 OpenSpec change from redhat-developer/agentic-feature-refinement (source commit ba2dbf1e141d7ded6a8ebe0a92eb5115e67f0cc8) into the Boost workspace. The six capability specs and supporting artifacts are copied from that change. The OpenSpec metadata uses Boost's spec-driven schema, and the source README and two Markdown files receive workspace provenance/formatting adjustments.

Archive the earlier ai-catalog-asset-governance draft so there is one active 1508 governance change. Remove the legacy 1508 feasibility and frontend reports, the old security OpenSpec area, and selected generated common/backend snapshot files. Update workspace guidance and historical references to match the cleanup. No active runtime package behavior changes.

Validation

  • yarn openspec:validate — 18/18 active Boost specs and changes passed
  • yarn prettier:check — passed
  • git diff --check — passed
  • Source comparison — all 14 source files present; only metadata, README, and Prettier formatting differ

✔️ Checklist

  • Changeset — not needed for documentation-only changes to unpublished specs and archived snapshots
  • Added or Updated documentation
  • Tests for new functionality and regression tests for bug fixes — no active runtime code changed
  • Screenshots attached — no UI changes

Signed-off-by: John Collier <jcollier@redhat.com>
@codecov

codecov Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.35%. Comparing base (0b024a2) to head (e4e5b82).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5414   +/-   ##
=======================================
  Coverage   65.35%   65.35%           
=======================================
  Files        2758     2758           
  Lines      110579   110579           
  Branches    31085    31085           
=======================================
  Hits        72264    72264           
  Misses      37739    37739           
  Partials      576      576           
Flag Coverage Δ *Carryforward flag
adoption-insights 87.31% <ø> (ø) Carriedforward from 206f4e3
ai-integrations 90.56% <ø> (ø) Carriedforward from 206f4e3
app-defaults 74.89% <ø> (ø) Carriedforward from 206f4e3
augment 46.67% <ø> (ø) Carriedforward from 206f4e3
boost 93.37% <ø> (ø)
bulk-import 73.12% <ø> (ø) Carriedforward from 206f4e3
cost-management 13.56% <ø> (ø) Carriedforward from 206f4e3
dcm 74.35% <ø> (ø) Carriedforward from 206f4e3
e2e-adoption-insights 60.00% <ø> (ø) Carriedforward from 206f4e3
e2e-extensions 62.42% <ø> (ø) Carriedforward from 206f4e3
e2e-global-header 52.43% <ø> (ø) Carriedforward from 206f4e3
e2e-homepage 61.25% <ø> (ø) Carriedforward from 206f4e3
e2e-intelligent-assistant 46.02% <ø> (ø) Carriedforward from 206f4e3
e2e-orchestrator 49.49% <ø> (ø) Carriedforward from 206f4e3
e2e-orchestrator-plugin 49.48% <ø> (ø) Carriedforward from 206f4e3
e2e-quickstart 54.83% <ø> (ø) Carriedforward from 206f4e3
e2e-scorecard 49.88% <ø> (ø) Carriedforward from 206f4e3
e2e-theme 16.43% <ø> (ø) Carriedforward from 206f4e3
extensions 58.11% <ø> (ø) Carriedforward from 206f4e3
global-floating-action-button 71.18% <ø> (ø) Carriedforward from 206f4e3
global-header 69.15% <ø> (ø) Carriedforward from 206f4e3
homepage 86.56% <ø> (ø) Carriedforward from 206f4e3
install-dynamic-plugins 84.02% <ø> (ø) Carriedforward from 206f4e3
intelligent-assistant 79.49% <ø> (ø) Carriedforward from 206f4e3
konflux 91.98% <ø> (ø) Carriedforward from 206f4e3
lightspeed 69.02% <ø> (ø) Carriedforward from 206f4e3
mcp-integrations 84.46% <ø> (ø) Carriedforward from 206f4e3
orchestrator 77.69% <ø> (ø) Carriedforward from 206f4e3
quickstart 65.83% <ø> (ø) Carriedforward from 206f4e3
sandbox 79.56% <ø> (ø) Carriedforward from 206f4e3
scorecard 92.32% <ø> (ø) Carriedforward from 206f4e3
theme 88.21% <ø> (ø) Carriedforward from 206f4e3
translations 7.91% <ø> (ø) Carriedforward from 206f4e3
x2a 79.43% <ø> (ø) Carriedforward from 206f4e3

*This pull request uses carry forward flags. Click here to find out more.


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0b024a2...e4e5b82. Read the comment docs.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@rhdh-qodo-merge

rhdh-qodo-merge Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Code Review by Qodo


View medium (2)
Remediation recommended
1. Readers see conflicting usage rules 🐞 Bug
Description
The new catalog-entity-visibility requirement says an entity reader can access usage details
without a separate grant, while the canonical ai-catalog-entity-extensions spec still requires the
Usage card to disappear when that grant is denied. When task 2.8 removes the existing gate and task
5.1 promotes only the new capability, implementers are left with incompatible acceptance criteria
for the same UI behavior.
Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The new whole-entity rule contradicts the existing canonical requirement to hide the Usage card without a usage-detail grant.

## Fix Focus Areas
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/catalog-entity-visibility/spec.md[19-27]
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/tasks.md[24-25]
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/tasks.md[47-50]
- workspaces/boost/openspec/specs/ai-catalog-entity-extensions/spec.md[114-125]

## Recommended Fix
Add an explicit modification and promotion task for the existing entity-extensions capability so its Usage-card requirements adopt the accepted whole-entity policy. Keep the UI cleanup and its tests aligned with that canonical-spec update.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗

2. Asset audit filters miss some mutations 🐞 Bug
Description
The provider-mutation event requirement makes the stable asset identifier optional, but the
audit-review scenario requires relevant events to be available when history is filtered for an
affected asset. If a provider emits a mutation without that identifier, the specified event has no
required asset correlation key for that filter; the change's own audit report marks this gap as
unresolved.
Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Asset-filtered audit review is required, but provider mutation events may omit the asset identifier needed to find them.

## Fix Focus Areas
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/ai-catalog-audit-events/spec.md[22-25]
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/ai-catalog-audit-events/spec.md[33-40]
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/tasks.md[32-36]

## Recommended Fix
Define mandatory correlation keys and matching semantics for each supported asset and connector filter, then test those queries. If asset correlation cannot be guaranteed, narrow the filtering scenario to the queries the emitted events can support.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗


View low (1)
Informational
3. Boost permissions lack the required prefix 📘 Rule violation
Description
The new OpenSpec defines ai-catalog.manage and related authorization identifiers such as
catalog.entity.read without the mandatory boost. prefix. The same unprefixed names are repeated
across the management, visibility, audit, and task specifications, so implementations following this
contract would introduce noncompliant permission identifiers.
Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

Issue description
The synced OpenSpec introduces Boost-owned permission identifiers such as `ai-catalog.manage` and `ai-catalog.admin` without the required `boost.` prefix, and also uses unprefixed authorization identifiers throughout the new specifications.

Fix Focus Areas
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/ai-catalog-management-permission/spec.md[5-52]
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/catalog-entity-visibility/spec.md[5-52]
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/tasks.md[18-45]
- workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/design.md[61-63]

Recommended Fix
Rename Boost-owned permission identifiers to names beginning with `boost.` throughout the proposal, design, specifications, audit material, and tasks. For standard external Backstage identifiers such as `catalog.entity.read`, explicitly document the external namespace exception if the naming policy permits it; otherwise define and consistently use a compliant Boost-scoped identifier.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗


@rhdh-qodo-merge

Copy link
Copy Markdown

PR Summary by Qodo

Sync RHDHPLAN-1508 RBAC OpenSpec and archive the earlier draft

📝 Documentation ⚙️ Configuration changes 🕐 40+ Minutes


AI Description

• Import six RHDHPLAN-1508 capability specs as Boost’s active, spec-driven governance change.
• Archive the earlier draft and distinguish historical references from current planning.
• Flag permission-name and provider-audit differences with Jira for reconciliation before
 implementation.
Diagram

graph TD
  Source["Merged refinement"] --> Active(["Active OpenSpec"]) --> Specs["Six capability specs"]
  Active --> Status["CURRENT.md"] --> Jira["Jira reconciliation"]
  Archive["Archived draft"] --> Status
  Archive --> History["Historical analyses"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Revise the existing draft in place
  • ➕ Avoids maintaining two change directories and redirecting historical references.
  • ➖ Obscures which requirements belonged to the earlier draft.
  • ➖ Makes comparison with the merged source contract harder.
2. Wait for Jira reconciliation before importing
  • ➕ Avoids presenting a disputed permission and audit contract as the active change.
  • ➖ Delays source synchronization and review of the exact merged contract.

Recommendation: Keep the imported change separate and archive the draft: this preserves provenance and historical traceability. Treat the active spec as planning only, and resolve the documented Jira differences and open audit-correlation warning before implementation.

Files changed (32) +654 / -38

Documentation (30) +648 / -37
RHDHPLAN-1508-feasibility-report.mdPoint the feasibility report to the active governance change +1/-1

Point the feasibility report to the active governance change

• Replaces the superseded draft reference with the new RBAC and versioning OpenSpec.

workspaces/boost/RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/specifications/JIRA-analysis/RHDHPLAN-1508-feasibility-report.md

RHDHPLAN-1508-frontend-coverage.mdIdentify historical frontend coverage as archived +4/-2

Identify historical frontend coverage as archived

• Clarifies that the coverage table describes the earlier draft and names the current follow-on change.

workspaces/boost/RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/specifications/JIRA-analysis/RHDHPLAN-1508-frontend-coverage.md

RHDHPLAN-1513-defer-from-2-1-staging-and-jira-impact.mdUpdate the current RBAC scope reference +1/-1

Update the current RBAC scope reference

• Points readers to the newly active governance OpenSpec rather than the archived draft.

workspaces/boost/RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/specifications/JIRA-analysis/RHDHPLAN-1513-defer-from-2-1-staging-and-jira-impact.md

cross-feature-frontend-summary.mdRetarget historical story references to the archive +6/-6

Retarget historical story references to the archive

• Updates the frontend story table to cite the archived specs it originally summarized.

workspaces/boost/RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/specifications/JIRA-analysis/cross-feature-frontend-summary.md

rhdhplan1505-1-staged-issues.mdSeparate current scope from archived task citations +21/-19

Separate current scope from archived task citations

• Names the new OpenSpec as the follow-on model while redirecting historical task and spec citations to the archived draft.

workspaces/boost/RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content/specifications/JIRA-analysis/rhdhplan1505-1-staged-issues.md

README.mdRecord source provenance and implementation caveats +13/-0

Record source provenance and implementation caveats

• Identifies the merged source commit and warns that permission naming and provider-audit scope must be reconciled with Jira.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/README.md

audit.mdImport the refinement audit report +31/-0

Import the refinement audit report

• Preserves the historical audit and notes that audit-event correlation remains unresolved; conditional bundle tasks address the earlier task-coverage warning.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/audit.md

design.mdDocument the refined authorization design +104/-0

Document the refined authorization design

• Defines Catalog-based whole-entity access, existing RBAC administration, management-permission compatibility, direct version policy, audit ownership, and bundle authorization boundaries.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/design.md

explore.mdCapture evidence and accepted scope decisions +55/-0

Capture evidence and accepted scope decisions

• Compares Jira criteria with platform behavior and the accepted refinement, including the deferred inheritance and bundle-serving dependencies.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/explore.md

journal.jsonlPreserve the refinement decision journal +12/-0

Preserve the refinement decision journal

• Records the PM scope decision and the resulting revisions to the imported planning artifacts.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/journal.jsonl

proposal.mdDefine the six-capability governance proposal +49/-0

Define the six-capability governance proposal

• Sets the proposed authorization scope, explicit non-goals, dependencies, and planned long-lived capability specs.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/proposal.md

spec.mdSpecify RBAC and provider audit outcomes +40/-0

Specify RBAC and provider audit outcomes

• Requires existing RBAC policy-change auditing and provider synchronization events through RHDH audit facilities, without duplicating evaluation events.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/ai-catalog-audit-events/spec.md

spec.mdSpecify management-permission compatibility +52/-0

Specify management-permission compatibility

• Defines global ai-catalog.manage, one-release ai-catalog.admin compatibility, and separation from entity visibility and RBAC policy-management authority.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/ai-catalog-management-permission/spec.md

spec.mdSpecify direct version policy and inheritance deferral +29/-0

Specify direct version policy and inheritance deferral

• Requires direct Catalog policy per entity until RHDHPLAN-1507 supplies a model and a reviewed follow-up establishes inheritance semantics.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/asset-version-policy/spec.md

spec.mdSpecify whole-entity Catalog visibility +52/-0

Specify whole-entity Catalog visibility

• Makes catalog.entity.read the single gate for discovery and details, defines deny-by-default behavior, and retains a p95 latency threshold.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/catalog-entity-visibility/spec.md

spec.mdSpecify existing conditional-policy use +57/-0

Specify existing conditional-policy use

• Scopes access using provider metadata and existing Catalog conditions, with RBAC administration as the control plane and custom rules reserved for proven gaps.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/conditional-asset-access/spec.md

spec.mdSpecify read-time SkillBundle member authorization +50/-0

Specify read-time SkillBundle member authorization

• Requires canonical Catalog checks before exposing members and blocks bundle-serving implementation until its ownership and API contract is approved.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/specs/skill-bundle-authorization/spec.md

tasks.mdPlan implementation and promotion checkpoints +51/-0

Plan implementation and promotion checkpoints

• Tracks Jira reconciliation, authorization and audit verification, conditional bundle work, performance checks, and promotion of accepted specs.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/tasks.md

README.mdExplain the archived draft's successor +7/-0

Explain the archived draft's successor

• Identifies the synced OpenSpec as the active successor and retains the earlier draft for traceability.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/README.md

audit.mdPreserve the earlier draft's audit +0/-0

Preserve the earlier draft's audit

• Moves the audit artifact into the archive without content changes.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/audit.md

design.mdPreserve the earlier governance design +0/-0

Preserve the earlier governance design

• Moves the superseded design into the archive without content changes.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/design.md

proposal.mdPreserve the earlier governance proposal +0/-0

Preserve the earlier governance proposal

• Moves the superseded proposal into the archive without content changes.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/proposal.md

spec.mdArchive the earlier audit-logging spec +0/-0

Archive the earlier audit-logging spec

• Retains the prior audit requirements as historical planning material.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/specs/audit-logging/spec.md

spec.mdArchive the earlier conditional-policies spec +0/-0

Archive the earlier conditional-policies spec

• Retains the prior conditional-policy requirements as historical planning material.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/specs/conditional-policies/spec.md

spec.mdArchive the earlier default-deny configuration spec +0/-0

Archive the earlier default-deny configuration spec

• Retains the prior default-policy requirements as historical planning material.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/specs/default-deny-config/spec.md

spec.mdArchive the earlier graduated-visibility spec +0/-0

Archive the earlier graduated-visibility spec

• Preserves requirements from the earlier draft; the new v1 contract excludes graduated visibility.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/specs/graduated-visibility/spec.md

spec.mdArchive the earlier SkillBundle-filtering spec +0/-0

Archive the earlier SkillBundle-filtering spec

• Retains the prior bundle-filtering requirements as historical planning material.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/specs/skillbundle-filtering/spec.md

spec.mdArchive the earlier version-cascade spec +0/-0

Archive the earlier version-cascade spec

• Preserves prior cascade requirements; the active change defers inheritance pending an entity-model contract and follow-up design.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/specs/version-policy-cascade/spec.md

tasks.mdPreserve the earlier governance task list +0/-0

Preserve the earlier governance task list

• Moves the superseded tasks into the archive so historical issue references remain traceable.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/tasks.md

CURRENT.mdIdentify the active RBAC plan and unresolved Jira drift +13/-8

Identify the active RBAC plan and unresolved Jira drift

• Replaces the former draft with the synced change in Boost's status guide, preserves the release boundary, and flags permission-name and provider-audit differences before implementation.

workspaces/boost/specifications/CURRENT.md

Other (2) +6 / -1
.openspec.yamlRegister the imported change with Boost's schema +5/-0

Register the imported change with Boost's schema

• Declares the change a draft using Boost's spec-driven OpenSpec schema.

workspaces/boost/openspec/changes/ai-catalog-rbac-versioning-policy/.openspec.yaml

.openspec.yamlMark the earlier governance change archived +1/-1

Mark the earlier governance change archived

• Changes the moved draft's OpenSpec status from draft to archived.

workspaces/boost/openspec/changes/archive/2026-10-30-ai-catalog-asset-governance/.openspec.yaml

@rhdh-qodo-merge

Copy link
Copy Markdown

Important

The /generate_labels command by Qodo was deprecated on the 1st of October 2026 and is no longer available. We recommend switching to the latest Qodo review capabilities. Learn more

@gabemontero gabemontero left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My scan of the new openspec content came up with no issues to report @johnmcollier - lgtm

I would encourage you to be more aggressive with the "legacy content". In particular:

  • just delete all the RHDHPLAN-1508 openspec content currently under workspaces/boost/RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content ... AI and I see that list as the 2 top level 1508 docs, RHDHPLAN-1508-feasibility-report.md and RHDHPLAN-1508-frontend-coverage.md; then, I would just delete the security-safety-governance openspecs
  • then there is the code generated with the prior openspecs
plugins/ai-catalog-common/src/permissions.ts
plugins/ai-catalog-common/src/index.ts
plugins/ai-catalog-common/src/index.test.ts

plugins/boost-backend/src/ai-catalog/CatalogAssetLoader.ts
plugins/boost-backend/src/ai-catalog/CatalogAssetLoader.test.ts
plugins/boost-backend/src/ai-catalog/routes.ts
plugins/boost-backend/src/ai-catalog/routes.test.ts
plugins/boost-backend/src/ai-catalog/rules.ts
plugins/boost-backend/src/ai-catalog/rules.test.ts
plugins/boost-backend/src/ai-catalog/index.ts

plugins/boost-backend/src/plugin.ts
plugins/boost-backend/src/index.ts

plugins/boost-backend/src/ingestion/routes.ts
plugins/boost-backend/src/ingestion/routes.test.ts

if you think you'll reference those in any way when you re-generate code with you new openspecs, then keep them for that. If you are going to generate code solely with the new openspecs, go ahead and delete this code under workspaces/boost/RHDH-2-1-Legacy-Content/Pre-RHDHPLAN-15xx-Content with this PR

then lastly, I see you requested a review from @rohitkrai03 .... definitely get his take on this PR, make sure the frontend is OK with where we are landing with you changes, before we merge.

thanks

Signed-off-by: John Collier <jcollier@redhat.com>
@sonarqubecloud

sonarqubecloud Bot commented Nov 2, 2026

Copy link
Copy Markdown

@gabemontero gabemontero left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm @johnmcollier

per my previous comment, let's get a review form @rohitkrai03 on this if at all possible before merging

@rohitkrai03 rohitkrai03 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@johnmcollier
johnmcollier merged commit 973b01b into redhat-developer:main Nov 3, 2026
28 checks passed
JslYoon pushed a commit to JslYoon/rhdh-plugins that referenced this pull request Nov 3, 2026
…hat-developer#5414)

* docs(boost): sync RHDHPLAN-1508 OpenSpec

Signed-off-by: John Collier <jcollier@redhat.com>

* docs(boost): remove obsolete 1508 legacy artifacts

Signed-off-by: John Collier <jcollier@redhat.com>

---------

Signed-off-by: John Collier <jcollier@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants