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
I’ve found the option: composer install –ignore-platform-reqs Ignore platform requirements (php & ext- packages). Edit: You can skip the platform checks with this, but Composer will fetch packages based on given PHP version then. So when you need composer to also emulate a PHP version during depedency resolving, you can (and should!) use this in … Read more
Supporting historical data directly within an operational system will make your application much more complex than it would otherwise be. Generally, I would not recommend doing it unless you have a hard requirement to manipulate historical versions of a record within the system. If you look closely, most requirements for historical data fall into one … Read more
Let’s say you have a FOO table that admins and users can update. Most of the time you can write queries against the FOO table. Happy days. Then, I would create a FOO_HISTORY table. This has all the columns of the FOO table. The primary key is the same as FOO plus a RevisionNumber column. … Read more
Another solution for this old post (for those that it might help) : public class Version implements Comparable<Version> { private String version; public final String get() { return this.version; } public Version(String version) { if(version == null) throw new IllegalArgumentException(“Version can not be null”); if(!version.matches(“[0-9]+(\\.[0-9]+)*”)) throw new IllegalArgumentException(“Invalid version format”); this.version = version; } @Override … 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
Changing a method signature Kind: Binary-level Break Languages affected: C# (VB and F# most likely, but untested) API before change public static class Foo { public static void bar(int i); } API after change public static class Foo { public static bool bar(int i); } Sample client code working before change Foo.bar(13);
Here is a pure Bash version that doesn’t require any external utilities: #!/bin/bash vercomp () { if [[ $1 == $2 ]] then return 0 fi local IFS=. local i ver1=($1) ver2=($2) # fill empty fields in ver1 with zeros for ((i=${#ver1[@]}; i<${#ver2[@]}; i++)) do ver1[i]=0 done for ((i=0; i<${#ver1[@]}; i++)) do if [[ -z … 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.)
You can use: npm show {pkg} version (so npm show express version will return now 3.0.0rc3).