Description of problem: Today we have duplicate update of files each time we release a new build of ovirt-engine. First we update all pom.xml files to latest version that matches the new official tag, but we also update the 'version.mak' file with FIX_RELEASE=X, where X is usually the minor version which correlates to the version we used in pom.xml. For e.g, if ovirt-engine version on pom.xml is 3.6.8 then FIX_RELEASE=8. If version is 4.0.1.1 then FIX_RELEASE=1.1 So instead of updating version.mak manually each time and exposing it to human errors and rebase conflicts with downstream branches, we can easily get the value it needs from the pom.xml file If its possible to do inside the spec file or another place, I think it will simplify the build process and take us one step forward towards automation of the official builds. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Eyal, Based on comment #1 , can this RFE move to verified?