| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[release] version bump to 13.0 alpha3 as we start new merge window.
|
|
|
|
|
|
[osx] - adapt osx packaging - make it similar to what we do on ios and a...
|
|
|
|
for consistency reasons
|
|
[release] version bump to 13.0 alpha2 as we start new merge window.
|
|
toprow
|
|
/Applications/AppleTV.app/com.apple.frontrow.appliance.xbmc\@720p.png - needed for ios6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
not really required so comment it out"
This reverts commit c31aca24e63b1b70a6e207f360f134f460cbe2d7.
buildbot needs this info, opps.
|
|
really required so comment it out
|
|
|
|
|
|
|
|
|
|
|
|
because AppleTV.app dyloads us.
|
|
|
|
|
|
|
|
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.
|
|
|
|
make sure it works
|
|
atv2 update prompt from killing us and flooding the forums with new user posts
|
|
then remove it. Added at request of Firecore
|
|
|
|
instead of relative
|
|
|
|
untether which uses a unionfs. We do both atv2 and iOS devices to keep things consistant
|
|
|
|
|
