Bug 765358 (GLUSTER-3626) - configure.ac version not getting set in release tags
Summary: configure.ac version not getting set in release tags
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-3626
Product: GlusterFS
Classification: Community
Component: build
Version: 3.2.3
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-25 05:45 UTC by Joe Julian
Modified: 2013-12-19 00:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.