Skip to content

tracking: WAVE_04 integration testing in dev #114

Description

@hyde-repo

tracking: WAVE_04 integration testing in dev

Wave: WAVE_04 (since 2026-06-05)
Cross-repo umbrellas: range42/range42-playbooks#69, range42/range42#198, range42/range42-catalog#178

This issue tracks the integration testing of WAVE_04 for range42/range42-ansible_roles-debug-devkit. Companion umbrellas exist on range42/range42-playbooks, range42/range42, and range42/range42-catalog.

Workflow

range42 uses a wave-based release train workflow :

internal fix or contributor PR -> land on dev -> integration test -> PR dev to main -> release

WAVE_04 spans range42/range42-playbooks, range42/range42, range42/range42-ansible_roles-debug-devkit, and range42/range42-catalog.

Cycle A - 2026-06-05 (open) - no sub-issues this cycle

No devkit-specific work scoped in Cycle A. The umbrella stays passive and is kept open for cross-repo coordination so all 4 wave anchors remain visible from the playbooks, range42, and catalog umbrellas ; sub-issues will land here only if devkit changes surface during integration testing of the new scenarios (misp_lab, dev_deployer_ui_lab, kunai_lab) on a real Proxmox.

Sub-issues landed on dev :

  • (none this cycle)

Status : passive umbrella, no sub-issues this cycle, awaiting integration testing on a real Proxmox.

Cycle B - 2026-06-14 (no contributor PR activity on this repo)

The bundles framework PoC (Cycle B activity) is concentrated on range42/range42-playbooks (#89 + #100, both landed on the feat-scenario-bundles-refactor branch). This repo has no companion changes for this cycle. Status : passive, nothing to release for this cycle.

Closure

Closed once the dev to main release PR for range42-ansible_roles-debug-devkit is merged. PR body should include Closes for any companion sub-issues opened during the wave. If no devkit change lands, the umbrella may close with only the _waves-testing.md bump commit (acceptable per cross-repo byte-identity convention).

Merge order across WAVE_04 : TBD - will be decided once the cohort scope is firmed up.

Failure list

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions