versioning

I have an executable on Linux that loads libfoo.so.1 (that's a SONAME ) as one of its dependencies (via another shared library). It also links to another system library, which, in turn, links to a system version, libfoo.so.2 . As a result, both libfoo.so.1 and libfoo.so.2 are loaded during execution, and code that was supposed to call functions from library with version 1 ends up calling (binary-incompatible) functions from a newer system library with version 2, because some symbols stay the same. The result is usually stack smashing and a subsequent segfault. Now, the library which links

We have a multi-module maven project that uses a profile that defines a buildnumber-maven-plugin to increment a build number and then check it into source control. If I define the plugin in the parent pom.xml it executes for all the child builds as well. Here's my parent pom.xml <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.webwars</groupId> <artifactId>parent</artifactId> <packaging>pom<

I believe that computers are the best things for doing repetitive tasks. I certainly am not, I either forget, or (mostly) don't do things in a consistent way - which isn't what I want. One of the things I am likely to do is forget to up the version information in the manifest when I publish a new version of an Android app. In the past I've worked with configured build systems that have a auto version numbering feature and I got use to it (or maybe I got lazy). I found this Stackoverflow post very useful in coming up with a solution, but it took me a while to fine tune it so it works just they

I'm starting to work with my model almost exclusively in WCF and wanted to get some practical approaches to versioning these services over time. Can anyone point me in the right direction? There is a good writeup on Craig McMurtry's WebLog . Its from 2006, but most of it is still relevant. As well as a decision tree to walk through the choices, he shows how to implement those changes using Windows Communication Foundation See "Versioning WCF Services: Part I" and "Versioning WCF Services: Part II" . See also: WCF Backwards Compatibility and Versioning Strategies – Part 1 WCF Backward

Say a development team includes (or makes use of) graphic artists who create all the images that go into a product. Such things include icons, bitmaps, window backgrounds, button images, animations, etc. Obviously, everything needed to build a piece of software should be under some form of version control. But most version control systems for developers are designed primarily for text-based information. Should the graphics people use the same version-control system and repository that the coders do? If not, what should they use, and what is the best way to keep everything synchronized?

I have a repository with only one branch ( master ). I'm the only contributor to my repo. I've recently added a tag , both locally and pushed to GitHub. After making what I though was the last necessary commit, but now I realize I should have made one more change/commit. So what I have is: commit 124 commit 125 commit 126 <-- tag v1.0 commit 127 and I want to move the v1.0 tag to the next commit, ie: 127 , both locally and in GitHub. How can I do that? Have you ever been to a book club where members do not all use the same edition of the "book of the week"? It's a nightmare, right? Moving a

I always used to check the windows versions by their major/minor build numbers. Strangely enough, Windows 7 and Server 2008 R2, both return the same major/minor version number combination. Confirm this by typing ver into a command prompt GetVersionEx. There is a chart of the version numbers and their associated editions here . Notice that the product type is different between 2008 R2 and Windows 7. This works, and correctly detects many Windows Product Editions, including Windows XP, Windows 7 (Home, Professional), Windows Server 2003, and Windows Server 2008, and contains code that should