Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

StatusIN PROGRESS
StakeholdersChris Tessmer Nicholas Markowski Judith Johnson Jeanne Greulich 
Outcome
Due date
OwnerTrevor 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

Action items

  •  
  • No labels