Add in your .dpr ( for example above the begin of the main code) the line: {$R *.res} Then build your project. It will force a resource file (.res) to be created. This also allows you to set the version info in the project options. Update: I noticed that this ‘bug’ is fixed in Delphi … Read more
The major version number is all you need for a web service. Because your consumers are only concerned about backward incompatible changes, and (if you’re following semantic versioning correctly) those will only be introduced when a new major version is released. All other changes (including new features, bugfixes, patches etc.) should be ‘safe’ for your … Read more
First of all, if you are building a REST API and you have just started, you may want to consider using Restify instead of Express. While Express can certainly be used for this purpose, Restify has been designed with all the requirements for a REST API server: standardized exceptions, API versioning, etc. Thus said, I … Read more
Some good information from this article on Suzanne Cook’s blog on MSDN (posted 2003-05-30): When to Change File/Assembly Versions First of all, file versions and assembly versions need not coincide with each other. I recommend that file versions change with each build. But, don’t change assembly versions with each build just so that you can … Read more
Since I’ve been gathering data and doing tests, I’ll post my results as an updated chart in this answer: Awhile ago, I found out that newer versions of Xcode do not, in fact, support migrating from all older versions of Swift. I did explicitly test that Xcodes 10.2 through 11 don’t support Swift 3.x and … Read more
There are a couple of popular Maven plugins that accomplish this feat: Maven Release Plugin Build Number Maven Plugin The Maven Release Plugin from the Apache Maven Project is a bit overkill for simply updating the version number. Therefore use the latter plugin to create a version number (in the form of MAJOR.MINOR.BUILD; e.g., 3.1.4 … Read more
The build_info.properties file: build.major.number=00 build.revision.number=00 build.minor.number=00 The build.xml file: <?xml version=”1.0″ encoding=”UTF-8″?> <project name=”project” default=”current-number”> <property file=”build_info.properties”/> <property name=”build.number” value=”${build.major.number}.${build.minor.number}.${build.revision.number}”/> <target name=”current-number”> <echo>Current build number:${build.number}</echo> </target> <target name=”compile”> <antcall target=”revision”></antcall> </target> <target name=”dist”> <antcall target=”minor”></antcall> </target> <target name=”revision”> <propertyfile file=”build_info.properties”> <entry key=”build.revision.number” type=”int” operation=”+” value=”1″ pattern=”00″/> </propertyfile> </target> <target name=”minor”> <propertyfile file=”build_info.properties”> <entry key=”build.minor.number” type=”int” … Read more
There are two good answers for this (plus a lot of personal preferences; see gizmo’s comment on religious wars). For public applications, the standard Major.Minor.Revision.Build works best IMO – public users can easily tell what version of the program they have and, to some degree, how far out of date their version is. For in … Read more
You should create a new branch when you’re doing development work that is somewhat experimental in nature. So in your scenario definitely create a new branch and not a folder within master. If you created your sandbox work as a directory in the master, it’s going to reside there until you remove it using git. … Read more
Docker gives no semantic meaning at all to tag values. A tag can be any string value at all, and tags can be reused. The only special tag value is that if you just say imagename in a docker pull or docker run command, it is automatically interpreted as imagename:latest. Mechanically, you can give the … Read more