64 |
64 |
65 Major number change means that the new version is incompatible with the old one |
65 Major number change means that the new version is incompatible with the old one |
66 and any dependent of the prior version will require code changes to upgrade to |
66 and any dependent of the prior version will require code changes to upgrade to |
67 the new package. |
67 the new package. |
68 |
68 |
|
69 Major number rare changed (this can take a lot of year). |
|
70 |
69 Minor version component. |
71 Minor version component. |
70 ------------------------ |
72 ------------------------ |
71 |
73 |
72 Minor number change means that the new version is backward compatible with the |
74 Minor number change means that the new version is backward compatible with the |
73 previous version but has significant enhancements over the previous version. |
75 previous version but has significant enhancements over the previous version. |
74 |
76 |
|
77 Functional enhancement releases. Contain new or significantly changed |
|
78 functionality and/or layout. |
|
79 |
|
80 New releases are usually only published several times a year or less. |
|
81 |
75 Revision, micro, bugfix version component. |
82 Revision, micro, bugfix version component. |
76 ------------------------------------------ |
83 ------------------------------------------ |
77 |
84 |
78 Revision number is updated whenever a bugfix is applied to the build such that |
85 Revision number is updated whenever a bugfix is applied to the build such that |
79 it doesn't bring a compatibility change or introduce newer features. |
86 it doesn't bring a compatibility change or introduce newer features. |
|
87 |
|
88 Patches are released frequently (sometimes daily). |
80 |
89 |
81 Milestone markers. |
90 Milestone markers. |
82 ------------------ |
91 ------------------ |
83 |
92 |
84 * a (alpha) means new development is complete and code checkins are frozen. |
93 * a (alpha) means new development is complete and code checkins are frozen. |