Auto-builds versions explained

Auto-builds will contain two versions of MythTV for each Mythbuntu release. When enabling auto-builds, you will be given these two options (ie. 0.22 and 0.23). The lower number is always the base version of MythTV that the release shipped with plus fixes. The higher number is what will become the next version of MythTV (ie. Mythbuntu 9.10 shipped with 0.22, 0.23 is the next version of MythTV). It is worth noting that the higher number starts out being built from trunk, then later on in the MythTV development cycle, gets built from upstreams fixes branch. (the switch happens when upstream creates a branch for it)

Please note that builds from "trunk" are not as optimized as regular builds to make it easier to debug them, so you may run into performance problems. By using the trunk builds, you sacrifice the stability afforded by a regular release cycles, so be sure to backup your database before starting. There is no returning to regular releases after enabling trunk.  As new releases happen upstream, trunk repos will be converted to stable and new repositories produced for trunk.

In some instances, a Mythbuntu release may only have a single version listed twice. This is due to the Mythbuntu release not being compatible with the release version+1. This happened with Mythbuntu 8.04 (0.21 is listed twice, 0.22 is not compatible with Mythbuntu 8.04)

Example

Mythbuntu 9.10 shipped with MythTV 0.22. Auto-builds contains two versions of MythTV for 9.10 (0.22 and 0.23). At the time of release, 0.22 was built from the upstream 0.22-fixes branch. At the start, 0.23 was built from the upstream trunk branch, then when upstream created the 0.23 branch to get ready for its release, auto-builds was moved to that branch. When upstream creates a 0.23-fixes branch, auto-builds will move 0.23 to that branch and that is where 0.23 will stay (it will not be moved again). Mythbuntu 9.10 will not get 0.24 through auto-builds.