10 feature availability and how compatible these versions. |
10 feature availability and how compatible these versions. |
11 |
11 |
12 Marketing versioning. |
12 Marketing versioning. |
13 ===================== |
13 ===================== |
14 |
14 |
15 Marketing versioning schema used for marketing, advertising purpose. It is |
15 Marketing versioning schema used for marketing, advertising, branding purpose. |
16 usually inconsistent and can changed over the time. |
16 It is usually inconsistent and can changed over the time. |
17 |
17 |
18 Examples of marketing version schema: |
18 Examples of marketing version schema: |
19 |
19 |
20 * Years. |
20 * Years. |
21 * Ancient gods. |
21 * Ancient gods. |
51 * minor |
51 * minor |
52 * patch (patchlevel), micro |
52 * patch (patchlevel), micro |
53 * rev (revision) |
53 * rev (revision) |
54 * build |
54 * build |
55 * date |
55 * date |
56 :: |
56 * hotfix, fix |
57 |
57 |
|
58 Version components usually combined in such group:: |
|
59 |
|
60 major.minor.build |
|
61 major.minor.date |
|
62 major.minor.hotfix |
|
63 major.minor.hotfix.build |
58 major.minor.rev |
64 major.minor.rev |
59 major.minor.rev.build |
65 major.minor.rev.build |
60 major.current.age |
66 major.current.age |
61 |
67 |
|
68 Its conventional to have at least a major and minor number. |
|
69 |
|
70 Prefixing version with a "v" seems to be less common. |
|
71 |
62 Major version component. |
72 Major version component. |
63 ------------------------ |
73 ------------------------ |
64 |
74 |
65 Major number change means that the new version is incompatible with the old one |
75 Major number change means that fundamental change made in the architecture of |
66 and any dependent of the prior version will require code changes to upgrade to |
76 the system the new version is incompatible with the old one, upgrade between |
67 the new package. |
77 versions is non-trivial, and any dependent of the prior version will require |
|
78 code changes to upgrade to the new package. |
68 |
79 |
69 Major number rare changed (this can take a lot of year). |
80 Major number rare changed (this can take a lot of year). |
70 |
81 |
71 Minor version component. |
82 Minor version component. |
72 ------------------------ |
83 ------------------------ |
73 |
84 |
74 Minor number change means that the new version is backward compatible with the |
85 Minor number change means that the new version is backward compatible with the |
75 previous version but has significant enhancements over the previous version. |
86 previous version but has significant enhancements over the previous version |
|
87 (like new functionality or changed UI). |
76 |
88 |
77 Functional enhancement releases. Contain new or significantly changed |
89 Functional enhancement releases. Contain new or significantly changed |
78 functionality and/or layout. |
90 functionality and/or layout. |
79 |
91 |
80 New releases are usually only published several times a year or less. |
92 New releases are usually only published several times a year or less. |
81 |
93 |
82 Revision, micro, bugfix version component. |
94 Revision, micro, bugfix version component. |
83 ------------------------------------------ |
95 ------------------------------------------ |
84 |
96 |
85 Revision number is updated whenever a bugfix is applied to the build such that |
97 Revision number is updated whenever a bugfix or security patche is applied to |
86 it doesn't bring a compatibility change or introduce newer features. |
98 the build such that it doesn't bring a compatibility change or introduce newer |
|
99 features. |
87 |
100 |
88 Patches are released frequently (sometimes daily). |
101 Patches are released frequently (sometimes daily). |
89 |
102 |
90 Milestone markers. |
103 Milestone markers. |
91 ------------------ |
104 ------------------ |