From: "Oleksandr Gavenko (aka gavenkoa)" <gaven...@gmail.com>
Date: Fri, 7 Oct 2011 08:05:45 -0700 (PDT)
Local: Fri, Oct 7 2011 11:05 am
Subject: How maintain revision/build component in version?
After reading a lot of articles/QAs/FAQs/books I become to think
that [MAJOR].[MINOR].[REV] is most useful versioning schema to
describe compatibility between project version (versioning schema
for developer, does not for marketing).
MAJOR changes is backward incompatible and require changing
MINOR changes is backward compatible. Mark introduction of new
REV for security/bug fixes. Backward and forward compatible.
At my job many project depend on internal libraries which stored
Path to dependent libraries include version component and hard
QUESTION: Is it usual practice to include path to libraries to
QUESTION: That is best: include version number in library name or
If you include only [MAJOR] you can inline libary name in sources
If you include [MAJOR].[MINOR] component every minor changes
I think that include [REV] was not needed. You only need to
QUESTION: I plan to realize such schema: package releases to
and created symlink to
from previous path. So every dependent project does not need make
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.