mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-23 20:25:56 +00:00
rcourtman
bd9063ed56
Releases are cut from the head of main since 2 October, but three things still made every release need hand edits before it could pass: - the control plane routed 6.5.x to the abandoned release/v6.5 line; - main lacked the published 6.4.4 to 6.4.6 packets, so rollback derivation on main still found 6.4.1; - the packet tests pinned prose from old 6.4.x notes (named highlights, issue numbers, one release's mobile decision) and the per-release sentences in the deployment-installability contract, which changes several times a day on main. Map 6.5 to main, carry the published packets over from release/v6.4, and keep the packet tests to what the release tooling generates: version pins, packet pointers, required sections and the rollback, signing and mobile sentences. Contract-Neutral: Release routing and release-packet test scope only; no runtime, install or public contract changes.
107 lines
5.3 KiB
JSON
107 lines
5.3 KiB
JSON
{
|
|
"version": "1",
|
|
"system": "pulse-release-control",
|
|
"execution_model": "direct-repo-sessions",
|
|
"agent_values_doc": "docs/release-control/internal/AGENT_VALUES.md",
|
|
"control_plane_doc": "docs/release-control/internal/CONTROL_PLANE.md",
|
|
"control_plane_schema": "docs/release-control/control_plane.schema.json",
|
|
"active_profile_id": "v6",
|
|
"active_target_id": "v6-release-reliability",
|
|
"legacy_release_lines": [
|
|
{
|
|
"version_prefix": "5.1.",
|
|
"prerelease_branch": "main",
|
|
"stable_branch": "main"
|
|
},
|
|
{
|
|
"version_prefix": "6.3.2",
|
|
"prerelease_branch": "release/v6.3.2",
|
|
"stable_branch": "release/v6.3.2"
|
|
},
|
|
{
|
|
"version_prefix": "6.4.3",
|
|
"prerelease_branch": "release/v6.4",
|
|
"stable_branch": "release/v6.4"
|
|
},
|
|
{
|
|
"version_prefix": "6.4.4",
|
|
"prerelease_branch": "release/v6.4",
|
|
"stable_branch": "release/v6.4"
|
|
},
|
|
{
|
|
"version_prefix": "6.4.5",
|
|
"prerelease_branch": "release/v6.4",
|
|
"stable_branch": "release/v6.4"
|
|
},
|
|
{
|
|
"version_prefix": "6.4.6",
|
|
"prerelease_branch": "release/v6.4",
|
|
"stable_branch": "release/v6.4"
|
|
}
|
|
],
|
|
"profiles": [
|
|
{
|
|
"id": "v6",
|
|
"lifecycle": "active",
|
|
"root": "docs/release-control/v6",
|
|
"prerelease_branch": "main",
|
|
"stable_branch": "main",
|
|
"source_of_truth": "docs/release-control/v6/internal/SOURCE_OF_TRUTH.md",
|
|
"status": "docs/release-control/v6/internal/status.json",
|
|
"status_schema": "docs/release-control/v6/status.schema.json",
|
|
"development_protocol": "docs/release-control/v6/internal/CANONICAL_DEVELOPMENT_PROTOCOL.md",
|
|
"high_risk_matrix": "docs/release-control/v6/internal/HIGH_RISK_RELEASE_VERIFICATION_MATRIX.md",
|
|
"subsystems_dir": "docs/release-control/v6/internal/subsystems",
|
|
"registry": "docs/release-control/v6/internal/subsystems/registry.json",
|
|
"registry_schema": "docs/release-control/v6/internal/subsystems/registry.schema.json",
|
|
"subsystem_contract_template": "docs/release-control/v6/internal/SUBSYSTEM_CONTRACT_TEMPLATE.md"
|
|
}
|
|
],
|
|
"targets": [
|
|
{
|
|
"id": "v6-rc-cut",
|
|
"profile_id": "v6",
|
|
"kind": "release",
|
|
"status": "completed",
|
|
"summary": "Hold Pulse v6 on the governed prerelease-cut target until RC publication is explicitly judged ready, while continuing to clear prerelease blockers, prove migration safety, and exercise the pre-RC high-risk gates.",
|
|
"completion_rule": "rc_ready"
|
|
},
|
|
{
|
|
"id": "v6-rc-stabilization",
|
|
"profile_id": "v6",
|
|
"kind": "stabilization",
|
|
"status": "completed",
|
|
"summary": "Once a real governed RC exists, keep Pulse v6 simple, accurate, and cleanly readable around that proven monitoring-first floor while broader control-plane expansion stays out of the default target until it is proven.",
|
|
"completion_rule": "manual",
|
|
"proof_scope": "none"
|
|
},
|
|
{
|
|
"id": "v6-ga-promotion",
|
|
"profile_id": "v6",
|
|
"kind": "release",
|
|
"status": "completed",
|
|
"summary": "Pulse v6 GA and the initial 6.0.x patch line shipped from the governed v6 release branch; after the v6 public cutover, main is the canonical latest-and-greatest branch for active development and stable release preparation.",
|
|
"completion_rule": "manual",
|
|
"proof_scope": "none"
|
|
},
|
|
{
|
|
"id": "v6-product-lane-expansion",
|
|
"profile_id": "v6",
|
|
"kind": "feature",
|
|
"status": "planned",
|
|
"summary": "Post-GA active development runs on main and promotes proactive Pulse Intelligence, policy-aware data governance, resource-change intelligence, action-governance, fleet-governance, agent-operable infrastructure onboarding, continuous discovery reconciliation, and agent-ready operations contract proof after the monitoring-first v6 floor; Patrol is the detection and investigation engine, Assistant is the contextual explanation, approval, and governed action surface, and agent-ready proof is API/CLI-first with MCP only as an adapter over canonical contracts. The planned product priority is a coherent Patrol-to-Assistant customer journey: explain the selected issue from current evidence, preserve governed approval and verification, and qualify useful outcomes for unhealthy services, backup or capacity risks, and supported VM or LXC actions before claiming broad Pulse Pro value.",
|
|
"completion_rule": "manual",
|
|
"proof_scope": "none"
|
|
},
|
|
{
|
|
"id": "v6-release-reliability",
|
|
"profile_id": "v6",
|
|
"kind": "maintenance",
|
|
"status": "active",
|
|
"summary": "Priority set on 10 September 2026: stability, consistent updates and fixing reported issues are the highest current objective, to rebuild user trust through dependable delivery. Prioritize resolving release blockers and verifying qualification, publication and customer delivery through the existing release process. Keep failed attempts owned through repair and verified recovery without repeated founder chasing. Release consistency remains unconfirmed until actual release and recovery evidence establishes dependable end-to-end delivery. A repaired component, passing source check or started retry does not establish this outcome. Feature expansion is not a current priority.",
|
|
"completion_rule": "manual",
|
|
"proof_scope": "none"
|
|
}
|
|
]
|
|
}
|