Bumblebee Versioning

General versioning

Bumblebee version are numbered x.y.z-n, where:

• x increases when a major change is released (ACPI support, nouveau support, ...)
• y increases when some other new features are released and starts at 0 each times x increments
• z increases when a general bugfix is released and starts at 0 each times y increments

Until here, this is common to all distros.

After that, we've got:

• n increases when a distro specific fix (e.g. alternatives in Ubuntu) is released and starts at 1 each times z increments

Versioning in Ubuntu PPAs

Stable PPA

Bumblebee version are named x.y.z-n~distroppam, where:

• x, y, z and n are as above
• distro is lucid, maverick, natty or oneiric
• m increases if there is only a change in the bumblebee-ppa build script and starts at 1 each times n increments

Dev PPA

Bumblebee version are named x.y.z-n+gityyyymmdd.gitrevision~distroppam, where:

• x and y are for the using the next release number (e.g. if stable is 2.4, dev is 2.5 or 3.0)
• z is constant to 0 here (bug fixes here are part of the development)
• n indicates the numbers of builds done for this version
• yyyy is year of the build
• mm is month of the build
• dd is day of the build
• gitrevision is ... git revision !
• distro is as above
• m is incremented if there is change in the build script specific to dev branch and restarts when we release the version (in order to track the number of changes done to the build script while developing a version)

Versioning in ArchLinux AUR

Stable release

The versioning system will follow the general x.y.z for the package version. The '-n' will refer only to changes in the PKGBUILD or the maintainer scripts.

Develop branch (git)

This package will always be named "bumblebee-git". The version number depends on the date and is set automatically by makepkg at build time:

bumblebee-git yyyymmdd

Where:

• yyyy is the year when the git repository is cloned by makepkg
• mm is the month when the git is cloned
• dd is the day when the git is cloned.