Hi:
> decided to remove usage of __DATE__,
> .. replaced this with a build rev. from the genVersionHeader.pl
I think this is a move in a useful direction.
The build date was somewhat meaningless.
You typically look at the version info to know: Does this still include bug X? Does this already include feature Y?
A release number "1.2.3" was useful when releases happened once a year.
But as software is updated more frequently, and you can't wait for everybody to agree on the next release number to assign, you might be running with "1.2.4.SNAPSHOT".
The build ref, e.g. git commit code, would in that case tell you exactly what you have .. except it's a little hard to parse.
Perfect would be, I think, showing both the build rev and the commit date.
From the commit date, a human can quickly see if the snapshot is before or after some key date when bug X got fixed.
If it happens to be the same day, then you dig down into the git commit code.
Thanks,
Kay
- References:
- no more __DATE__ Michael Davidsaver via Core-talk
- Navigate by Date:
- Prev:
[Bug 1829919] Re: IOC segfaults when calling dbLoadRecords after iocInit Martin Konrad via Core-talk
- Next:
Jenkins build became unstable: epics-7.0 » linux32 #167 APS Jenkins via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
no more __DATE__ Michael Davidsaver via Core-talk
- Next:
Re: no more __DATE__ Konrad, Martin via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|