The key to versioning JSON is to always add new properties, and never remove or rename existing properties. This is similar to how protocol buffers handle versioning. For example, if you started with the following JSON: { “version”: “1.0”, “foo”: true } And you want to rename the “foo” property to “bar”, don’t just rename … Read more
There is no cPickle in Python 3. Just import pickle. pickle will automatically use the C accelerator.
Starting with npm 6.4.0 you can use the –preid option of npm version like this: $ npm version prerelease –preid=alpha v0.1.1-alpha.0 $ npm version prerelease –preid=alpha v0.1.1-alpha.1 $ npm version prerelease –preid=alpha v0.1.1-alpha.2
The versioning is simply a mess: Java 1.0 and 1.1 were normal Then came Java 1.2, but you were supposed to call it “Java 2, JDK 1.2” This continued until 1.4 (There were also minor releases like 1.4.2) The next version was then supposedly “Java 5.0”, but there was still “1.5” all over the place … Read more
Yes, having art assets in version control is very useful. You get the ability to track history, roll back changes, and you have a single source to do backups with. Keep in mind that art assets are MUCH larger so your server needs to have lots of disk space & network bandwidth. I’ve had success … Read more
Files are distributed as part of a larger project. A file with individual build version x might be distributed as part of project version y. To elaborate: A.exe with product version 1.1 ships with files B.dll and C.dll. All start out with matching product and file versions. Then someone finds a serious bug in the … Read more
I completely agree; a URI expresses identity, identity doesn’t change when a new version is introduced. There might be new URIs for additional concepts, of course, and existing URIs might redirect … but including a “v2” in the URI smells RPCish to me. Note that this has got nothing to do with REST, really, as … Read more
I have done various audit schemes over the years and I am currently going to implement something like this: Person ———————————————— ID UINT NOT NULL, PersonID UINT NOT NULL, Name VARCHAR(200) NOT NULL, DOB DATE NOT NULL, Email VARCHAR(100) NOT NULL Person_History ———————————————— ID UINT NOT NULL, PersonID UINT NOT NULL, Name VARCHAR(200) NOT NULL, … Read more
The reason the two other answers contradict each other is that they’re both right (and worth reading), but they apply to different situations. If you’re releasing a library on PyPI, you should declare whatever dependencies you know about, but not pin to a specific version. For example, if you know you need >= 1.2, but … Read more
There is nothing wrong with checking in .project and .classpath. I would do so, if your build.xml isn’t able to create both of the files for you. As you said, it’s uncomfortable to miss these files when you try to create a new eclipse workspace. Before you check in .classpath you should be sure that … Read more