Development builds: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
>UNiversal
m (→‎Monthly build: this is more readable. =#FFB5B instead of =red)
>UNiversal
m (→‎Betas and release candidates: =#FFB5B5 is more readable than =red)
Line 71: Line 71:
After release candidates comes a final stable build that becomes XBMC v12, aka Frodo.
After release candidates comes a final stable build that becomes XBMC v12, aka Frodo.


{{highlight|color=red|ALWAYS BACKUP YOUR '''[[userdata|USERDATA FOLDER]]''' WHEN USING BETAS}}
{{highlight|color=#FFB5B5|ALWAYS BACKUP YOUR '''[[userdata|USERDATA FOLDER]]''' WHEN USING BETAS}}


http://mirrors.xbmc.org/releases/
http://mirrors.xbmc.org/releases/

Revision as of 12:10, 20 December 2012

Template:Frodo Frodo is the code name for the next version of XBMC, v12 (Frodo). These development builds, often called "pre-Frodo" or "pre-release" builds, are what will eventually lead to the final Frodo version. In contrast to the stable builds (v11, Eden) you don't have to wait for the release in order to benefit from new features or fixes that made it into XBMC.

THESE BUILDS OFTEN DO NOT WORK and are only for the brave users that do not fear bugs or crashes. They are mostly used for development. If you want a stable HTPC, this is not the place for you!

Nightly build

Nightly Builds are made on a daily basis and contain the most recent changes. They are also the most unstable of the development builds (until "feature freeze" where only bug fixes are made).

ALWAYS BACKUP YOUR USERDATA FOLDER WHEN USING NIGHTLY BUILDS

http://mirrors.xbmc.org/nightlies/



Also you can compile these builds yourself. See the appropriate Wiki article or Read Me for doing this:

Monthly build

Monthly builds are semi-stable nightly snapshots of pre-release builds.

XBMC developers have a merge cycle every month for new features and major changes. For ten days they add new features, then for the rest of the month they fix things. The monthly is then taken from a nightly just before they start adding features again.

ALWAYS BACKUP YOUR USERDATA FOLDER WHEN USING MONTHLY BUILDS

http://mirrors.xbmc.org/snapshots/

Betas and release candidates

When XBMC gets close to a stable release, public betas will be released. These are similar to nightlies and monthlies in that they still contain bugs, but are more stable and are encouraged to be tried out. At the point where XBMC reaches beta, most known bugs have been fixed, and developers are now looking for bugs they might not know about.

When XBMC beta gets to a point where it seems ready for a final release a "Release Candidate", or "RC", is released to flesh out any final bugs. Depending on any issues found, there may be multiple release candidates.

After release candidates comes a final stable build that becomes XBMC v12, aka Frodo.

ALWAYS BACKUP YOUR USERDATA FOLDER WHEN USING BETAS

http://mirrors.xbmc.org/releases/

Special notes about development builds

Bugs
As development builds are bleeding edge code you might find a bug here and there. In order to get rid of this bugs, it's important that these will be reported: HOW-TO:Submit a proper bug report.
Feature requests
If you have a feature that you think should be added to appear in the next stable version of XBMC, you can make a feature request: HOW-TO:Submit an official feature request.

Buildbot

Billy the buildbot. He makes the nightly and monthly builds of XBMC from git.

See also