Versions Compared

Version Old Version 5 New Version Current
Changes made by

Brandon Riden

Kendall Moore

Saved on

Key

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

...

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, as well as changing any dependencies to match the new naming scheme, adding obsoletes to prevent issues with the name change. If no changes are needed to the name, metadata or spec, or obsoletes, no version bump would be necessary. 

Options considered


Option 1:Option 2:

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

'rubygem-<module_name>'

'simp-<module_name>'

Status Quo
Pros and cons

(plus) Community recognized/used structure

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

(plus) Future modules would follow 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

(plus) No work to be done

(minus) Organizational structure remains confusing and not easily discoverable

(minus) Different names for repo, module, and RPM for same upstream 

Votes

20
Supporters:Brandon
Kendall
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
  •  Add necessary obsoletes
  •  Update code to fix references to old names
  •  Minor version bump for Repositories that had metadata.json or .spec file updates
  •  Update documentation to match the new naming scheme

...