KernelPackageVersioning
Differences between revisions 4 and 7 (spanning 3 versions)
559
Comment:
|
716
converted to 1.6 markup
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
* ABI bumps cause no change to "Revision" or "Release": | * ABI bumps requires a "Revision" bump, but leaves "Release" unchanged: |
Line 13: | Line 13: |
{{{2.6.M.REL-ABI.REV}}} -> {{{2.6.M.REL-(ABI+1).REV}}} | {{{2.6.M.REL-ABI.REV}}} -> {{{2.6.M.REL-(ABI+1).(REV+1)}}} Note: In the rare event that a queued package fails to build, you must bump the version number in debian/changelog before re-queuing. |
For the kernel packages themselves, please use the appropriate git scripts, as detailed in KernelMaintenance. For linux-restricted-modules:
- New orig.tar.gz causes the "Release" to bump, but not the ABI. This also resets the "Revision":
2.6.M.REL-ABI.REV -> 2.6.M.(REL+1)-ABI.1
- Changes to packaging causes a "Revision" bump, but not "Release" or ABI:
2.6.M.REL-ABI.REV -> 2.6.M.REL-ABI.(REV+1)
- ABI bumps requires a "Revision" bump, but leaves "Release" unchanged:
2.6.M.REL-ABI.REV -> 2.6.M.REL-(ABI+1).(REV+1)
Note: In the rare event that a queued package fails to build, you must bump the version number in debian/changelog before re-queuing.
KernelTeam/KernelPackageVersioning (last edited 2010-06-30 18:08:13 by c-76-105-148-120)