Versions Compared

Version Old Version 1 New Version 2
Changes made by

Brandon Riden

Brandon Riden

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Add your comments directly to the page. Include links to any relevant research, data, or feedback.

Page Properties
label


Status
Status
colourYellow
titleIn progress
Impact

Status
colourRed
titleHIGH

Driver~557058:da6320c4-4cb9-4d7b-8742-0dfa95644ddd 
Approver
Contributors
Informed
Due date
Outcome


Background

Restructure the current and future SIMP modules and RPM (metadata) names to match community standards, making our repositories and RPMs easier to manage, maintain, and understand.

...

This plan will result in a minor version bump for all updated modules since we would be changing the metadata.json or .spec file to update the names. If no changes are needed (such as simp-doc), no version bump would be necessary. 

Options considered


Option 1:

Update SIMP Repositories to match the structure:
'puppet-<module_name>'

'ruby-<module_name>'

'simp-<module_name>'


Pros and cons

(plus) standardized structure that the community understands

(plus) RPM names would match repo names, preventing confusion

(plus) Future modules would follow

existing

new structure

(plus) Ability to easily automate RPM builds and downloads with consistent naming scheme

(plus) Prevents having to dig to determine which RPM belongs to which repo (see simp-rsync and simp-rsync-skeleton)

(plus) Permanent redirects from Github prevent broken links

(minus) Documentation would need to be updated

(minus) Could be confusing for existing customers


Estimated cost
Status
colourYELLOW
titleMEDIUM

Action items

  •  Update SIMP Repositories to match naming scheme if necessary
  •  Update metadata.json or .spec file to match naming scheme if necessary
  •  Minor version bump for Repositories that had metadata.json or .spec file updates
  •  Update documentation to match the new naming scheme

...