/
Correlate version numbers between the metadata.json and the RPM spec files.

Correlate version numbers between the metadata.json and the RPM spec files.

Mar 10, 2016

Status

DONE

Stakeholders

@Chris Tessmer @Nicholas Markowski @Judith Johnson @Jeanne Greulich 

Outcome

Everyone seems to like this idea so Semantic Versioning 2.0.0 is where we're going!

Due date

Mar 11, 2016

Owner

@Trevor Vaughan 

Background

Now that we're Forge-compatible, we really need to correlate the version numbers between the RPMs and the metadata.json files.

I am proposing that we move to a Ruby-style semantic versioning construct which will mean that the -X part of the RPM spec file will only be used for items that only affect the RPM release and not the Forge release.

In other words: 

X.Y.Z-R

X -> Breaking Change
Y -> New Features
Z -> Bug Fixes
R -> RPM Only

Pros

  • This should be simple to automate for:

    • linting/validation

    • (eventually) RPM spec file generation

  • The existing modules won't take much work to normalize since we used this convention while creating the missing metadata.json files during SIMP-398 and SIMP-667.

Cons

  • Our zeal for order may snuff out a minuscule-but-still-free avenue for creativity, thus hastening the day when life will be uniformly dull and joyless.

Action items