On 03/17/2016 09:19 AM, Malahal Naineni wrote: > Kaleb, the tag you made V2.3.1 actually points to 2.3.0-1 version in its > src/CMakeLists.txt file. You should have at least changed > src/CMakeLists.txt file reflect V2.3.1 version before tagging.
Ugh. I forgot about that. :-( > > I back ported some patches on top of V2.3.0-1 and called it V2.3.1. To > avoid "tag" vs "actual version" confusion, we should do the following: > > 1. Move the existing V2.3.1 tag point to to actual V2.3.1 version. > 2. If #1 is not desired for some odd reason, I should at least make the > new version as V2.3.1-1 and tag it as V2.3.1-1. > > I am fine with #2, but we still leave some confusion if we don't do #1. For Red Hat and Fedora, 2.3.1-x means Release (or build) X of Version 2.3.1. Usually what this means for is is we use the 2.3.1 tar file and may make various changes to the RPM spec file (including applying patches) and these are 2.3.1-1, 2.3.1-2, 2.3.1-3, etc. over the life of 2.3.1 So for us it would be better if the next tag or release is V2.3.2. -- Kaleb ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Nfs-ganesha-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
