Project

Profile

Help

Story #6797

[epic] As a user, I can consume all the plugin prereq roles in the installer.

Added by mdepaulo@redhat.com 5 months ago. Updated 30 days ago.

Status:
ASSIGNED
Priority:
Normal
Assignee:
-
Category:
Installer
Sprint/Milestone:
-
Start date:
Due date:
% Done:

67%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

pulp_rpm_prerequisites exists because the installer has had a plugin neutral policy.

This policy was for very long misunderstood: It's not about avoiding favoritism to any plugins, it's about not tying the installer (which is tied to pulpcore releases) to plugin releases. So that say pulpcore 3.3 logic would be in pulp_installer 3.3 release, and so that pulp_cardboardbox 0.7 logic would be in the pulp_cardboardbox_prerequisites 0.7 role.

The team now agrees that this policy is counter-productive because:

  1. Having a role in a separate repo (not part of the pulp_installer collection) is extra work for developers, and for users.
  2. The only plugin that currently needs a prereq role, pulp_rpm, has version numbers and releases that correspond to pulpcore releases. pulp_rpm 3.3.z needs pulpcore 3.3.z, etc. So the pulp_rpm specific installation logic can be safely bundled in pulp_installer 99% of the time.

Subtasks

Task #6798: Document the new guidelines for plugin installation logicNEW

Actions
Refactor #6799: Merge the pulp_rpm_prerequisites role into pulp_installerCLOSED - CURRENTRELEASEfao89

Actions
Refactor #6903: Merge the galaxy_ng_prerequisites role into pulp_installerCLOSED - CURRENTRELEASEfao89

Actions

History

#1 Updated by bmbouter 5 months ago

  • Subject changed from As a user, I can consume all the plugin prereq roles in the installer. to [epic] As a user, I can consume all the plugin prereq roles in the installer.

#2 Updated by mdepaulo@redhat.com 5 months ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 74

#3 Updated by mdepaulo@redhat.com 5 months ago

  • Assignee set to fao89

#4 Updated by fao89 5 months ago

  • Status changed from NEW to ASSIGNED

#5 Updated by rchan 4 months ago

  • Sprint changed from Sprint 74 to Sprint 75

#6 Updated by rchan 4 months ago

  • Sprint changed from Sprint 75 to Sprint 76

#7 Updated by rchan 3 months ago

  • Sprint changed from Sprint 76 to Sprint 77

#8 Updated by rchan 3 months ago

  • Sprint changed from Sprint 77 to Sprint 78

#9 Updated by rchan 3 months ago

  • Sprint changed from Sprint 78 to Sprint 79

#10 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 79 to Sprint 80

#11 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 80 to Sprint 81

#12 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 81 to Sprint 82

#13 Updated by fao89 30 days ago

  • Assignee deleted (fao89)
  • Sprint deleted (Sprint 82)

I don't think the epic should be at the sprint, #6798 is already at the sprint

Please register to edit this issue

Also available in: Atom PDF