26.03.2016 15:46, Dmitry Yemanov wrote: > Or we may adopt a combined solution. For our own builds, both official > and snapshots, calculate the build number as commit count (as now, but > without storing in the repo). For external builds, gather LAST_COMMIT > and embed it into the version string*as date*. I.e. something like: > > Firebird-4.0.0.123-Unstable (official) > vs > Firebird-4.0.0.0-20160326-Unstable (unofficial) > > Port maintainers will either use our git-based scripts to get a proper > build number or fix the version string themselves with whatever > numbering they want. And for any non-official snapshots we will see them > as obviously non-official and still be able to determine what code > checkout they belong to. > > Does anyone think it looks better?
May be we can cut off two digits from year and use build number as YYMMDDHHm of the last commit everywhere?.. It still has the problem with two commits within 10 minutes and export between them but our workflow is not that dense. -- WBR, SD. ------------------------------------------------------------------------------ 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=278785471&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
