Versioning is something that I am very passionate about and have spent a long time trying to come up with an easy to use versioning system. From what you have already said in your question it is clear that you have understood one important point, the assembly version numbers are not synonymous with the product … Read more
Think carefully about the requirements for revisions. Once your code-base has pervasive history tracking built into the operational system it will get very complex. Insurance underwriting systems are particularly bad for this, with schemas often running in excess of 1000 tables. Queries also tend to be quite complex and this can lead to performance issues. … Read more
You should start with version 1, unless you know that the first version you “release” is incomplete in some way. As to how you increment the versions, that’s up to you, but use the major, minor, build numbering as a guide. It’s not necessary to have every version you commit to source control as another … Read more
I fixed this by: Removing the MVC reference and add the correct reference to the project. Changing the Copy Local property of the reference to true. Update the bindingRedirect setting in web.config: web.config runtime section: <runtime> <assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″> <dependentAssembly> <assemblyIdentity name=”System.Web.Mvc” publicKeyToken=”31bf3856ad364e35″ /> <bindingRedirect oldVersion=”1.0.0.0-3.0.0.0″ newVersion=”3.0.0.1″ /> </dependentAssembly> … Changing the Copy Local setting will … Read more
This is such a difficult subject that it’s not even funny, and one that I have spent years providing consultancy support for. There are many best practices out there, but a most of them do not work in all situations. For example, many advocate the use of “xsd:any” to allow extensions, and that is just … Read more
You could selectively alter the library path. For complete transparency, keep both out of your usual path and then do library(foo, lib.loc=”~/dev/foo/v1″) ## loads v1 and library(foo, lib.loc=”~/dev/foo/v2″) ## loads v2 The same works for install.packages(), of course. All these commands have a number of arguments, so the hooks you aim for may already be … Read more
You should use the maven-release-plugin to release your artifacts. Than automatically all your versions will be incremented by the release-plugin. The exception might be if you are going from 1.0.3-SNAPSHOT to 1.1.0-SNAPSHOT . The timeline for developing with Maven is: 1.0.0-SNAPSHOT 1.0.0 1.0.1-SNAPSHOT 1.0.1 1.0.2-SNAPSHOT 1.0.2 .. To go for the step from a SNAPSHOT … Read more
For several of my projects I capture the subversion revision number, time, user who ran the build, and some system information, stuff them into a .properties file that gets included in the application jar, and read that jar at runtime. The ant code looks like this: <!– software revision number –> <property name=”version” value=”1.23″/> <target … Read more
This blog post advises using diff and patch. git stash approximately becomes svn diff > patch_name.patch; svn revert -R . git stash apply becomes patch -p0 < patch_name.patch Note that this doesn’t stash metadata changes or (I think) directory creates/deletes. (Yes, svn tracks those separately from directory contents, unlike git.)