Bug 765358 (GLUSTER-3626)

Summary: configure.ac version not getting set in release tags
Product: [Community] GlusterFS Reporter: Joe Julian <joe>
Component: buildAssignee: Amar Tumballi <amarts>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.3CC: gluster-bugs, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joe Julian 2011-09-25 05:45:50 UTC
When checking out any release version from the git tree, my expectation was that AC_INIT would have the correct version number for that release.

Comment 1 Amar Tumballi 2011-09-26 04:09:26 UTC
Joe,

Each release is made with a release script from our git repo, and then we tag the git with corresponding release version. If we have to keep changing AC_INIT() version in configure.ac, we need one more commit per qa release, which should go through the whole patch process.

We are not planing to change the version inside our git repo per releases, instead the source-code available with the release tarball will have the proper version set.