aboutsummaryrefslogtreecommitdiff
path: root/addons/xbmc.addon
diff options
context:
space:
mode:
authortheuni <theuni-nospam-@xbmc.org>2012-04-01 03:55:38 -0400
committertheuni <theuni-nospam-@xbmc.org>2012-04-03 20:03:03 -0400
commitb7bf6475986812a595bf48560a9e2f4cdc09d5af (patch)
tree3a70644522294d40f05e3a065f2165cf6061ffa4 /addons/xbmc.addon
parent5f8ba69b449c572dcffd4f7a62bd25019edd9101 (diff)
release: version bumps for 12.0 alpha1
Each merge window will be defined as an alpha release. Thus, the first commit in the next merge window should be a bump to 12.0 alpha2. For internal versioning that cannot be handled with strings, we use currentvers + .9 instead, so that versions are always incrementing. It's not nice to mix, but since they're for dev use only, confusion should be minimal. xbmc.addon will be 11.9.1 for the first alpha in the 12.0 release series, 11.9.2 for the second, etc. This way final release will be 12.0.0 as expected. configure.in is handled the same way.
Diffstat (limited to 'addons/xbmc.addon')
-rw-r--r--addons/xbmc.addon/addon.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/addons/xbmc.addon/addon.xml b/addons/xbmc.addon/addon.xml
index ce7f05ac5b..a85612ed2f 100644
--- a/addons/xbmc.addon/addon.xml
+++ b/addons/xbmc.addon/addon.xml
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<addon id="xbmc.addon" version="11.0" provider-name="Team XBMC">
+<addon id="xbmc.addon" version="11.9.1" provider-name="Team XBMC">
<requires>
<import addon="xbmc.core" version="0.1"/>
</requires>