Skip to content

Conversation

@maximiliankolb
Copy link
Contributor

@maximiliankolb maximiliankolb commented Sep 4, 2025

What changes are you introducing?

With Katello nightly, all Deb content will be in structured APT mode only.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Depends on PR 11487 in katello

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

FYI: I checked for broken links and further instances: there are none.

Contributor checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.16/Katello 4.18 (Satellite 6.18)
  • Foreman 3.15/Katello 4.17
  • Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4)
  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9; orcharhino 7.1 with Leapp)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • We do not accept PRs for Foreman older than 3.9.

Review checklists

Tech review (performed by an Engineer who did not author the PR; can be skipped if tech review is unnecessary):

  • The PR documents a recommended, user-friendly path.
  • The PR removes steps that have been made unnecessary or obsolete.
  • Any steps introduced or updated in the PR have been tested to confirm that they lead to the documented end result.

Style review (by a Technical Writer who did not author the PR):

  • The PR conforms with the team's style guidelines.
  • The PR introduces documentation that describes a user story rather than a product feature.

With Katello nightly, all Deb content will be in structured APT mode
only.

Depends on PR 11487 in katello
@maximiliankolb maximiliankolb added Waiting for code Requires merge of related code in another repository before it can be merged and removed Not yet reviewed labels Sep 4, 2025
@github-actions github-actions bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Sep 4, 2025
@github-actions
Copy link

github-actions bot commented Sep 4, 2025

@nadjaheitmann
Copy link

Looks straight-forward to me once the Katello PR is merged.

@maximiliankolb maximiliankolb added tech review done No issues from the technical perspective and removed Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing labels Sep 17, 2025
@quba42
Copy link

quba42 commented Oct 31, 2025

Note: Since the feature PR is now merged in time for Katello 4.19, we should aim to merge this PR before 3.17 is branched in this repo (or else backport to the 3.17 branch)

@quba42
Copy link

quba42 commented Oct 31, 2025

Note: I have also started a draft PR on adding Katello 4.19 upgrade notes here: #4452 My understanding is that this will exclusively be needed on the 3.17 branch. Katello is due to branch for 4.19 on 2025-11-11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs style review Requires a review from docs style/grammar perspective tech review done No issues from the technical perspective Waiting for code Requires merge of related code in another repository before it can be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants