Rocky Linux Pro rename - one disruption, customers told first, structural RLC names stay until there is a value or a problem

October 30, 2026 at 7:17 PMtechnicalhigh

Situation

Bjorn owned the RLC Pro to Rocky Linux Pro rename and Greg had no objection to Justin convergence doc. Peter set how it executes: Justin 8.10/9.2 convergence changes and the rename ship together so customers absorb one disruption; sales contacts every potentially affected customer first and only then does engineering flip its side (Justin could not action it that morning); structural RLC names (repos, Depot paths, CPEs, bootc and container names) stay as they are; and there is no hard company-wide switch - the public name can slide over a week or two. Jamie Brooks drives the project.

Reasoning

Breaking changes to customer automation cost trust, so bundle them and pay once. RLC as the Rocky Linux variant from CIQ is a stable internal identifier that lets the public brand evolve without breaking customers again. General rule in Peter words: do not change customer-facing structure until there is a value to changing it - let us have a problem first. Customers are told before anything breaks.

Additional Context

Confirmed by Peter without changes. RESF approved the Rocky Pro name unanimously on 10/26; Linux Foundation sublicense pending.

Observed Evidence

We want to do them at the same time so we only have this disruption once. / leaving everything RLC that is structural leaves us free to have a public-facing name that changes with time while our internal piping does not. / We are not going to coordinate a hard switch? We are going to let this slide over the course of a week or two?

Confidence Breakdown

30/35
Evidence
15/30
Pattern
15/20
Source
13/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering does not ship breaking changes ahead of go-to-market; customer contact gates the technical change.
Who Affected:Sales and CS (customer outreach), RAT and Linux teams, Marketing (announcement timing stays a Marketing call), customers with automation on 8.10/9.2.
Precedent:Internal identifiers are decoupled from public brand and only change when a real problem or value appears.
Consequences:Real breaking changes for 8.10/9.2 customers; cosmetic-only for 9.9/10.3.
Timing:Rights to the name landed the same week the convergence was ready, so combining them avoided a second disruption.

Source

reflection

AI Confidence

73%

Related Context

💬
#department-heads

slack

we will have sales reach out to all potentially affected customers over the next week. Only when that is done will we make the change on our side.

🎥
RLC to Rocky Linux Pro: strategy discussion

fathom

I would not change them until there is a value to changing them. / Let us have a problem first.

🎥
C-Suite Sync 10/27

fathom

Justin is chomping at the bit... the answer to that is going to be no. But we can start as a company actioning this, all on the go-to-market side.

Outcome

No outcome recorded yet.

Decision ID: f9e35e89-4397-4c32-a1af-407e073ef041