Addon will still work for frodo.
If you do an update, we'll ask you to change xbmc.python to 2.1.0.
We don't force people to push an update just to change the version.
But if you want to do it, you are welcome.
Hope it clarifies.
Cheers
On Thu, Jan 3, 2013 at 1:42 PM, Joshua Welch wrote:
> als
also:
I'm really unsure, I should just up the version, indicate it is for frodo
and then resubmit? Mine currently shows on my frodo rc3 listing, does that
mean i should be good to go? I'm really confused on what I should do.
(liveleak 0.0.1)
Thanks and sorry I'm slow or whatever.
On Thu, Jan 3
Hopefully they will be updated sooner or later so comply with it. They will
keep functioning without any problems (under conditions that they already
functioned)
Martijn
Op 3 jan. 2013 13:33 schreef "Thomas Amland" het
volgende:
> And what will happen to the addons currently in the frodo repo th
And what will happen to the addons currently in the frodo repo that use
major.minor? Will they stay as they are or get removed?
--
mvh,
Thomas Amland
On Thu, Jan 3, 2013 at 1:13 PM, Martijn Kaijser wrote:
> It applies to every plugin, script, scraper, Web interface that want to
> be include
It applies to every plugin, script, scraper, Web interface that want to be
included in Frodo (do note that you must not use these in eden) repo.
Even if the code is the same you must differentiate between eden and frodo.
This should be one time to get a unified versioning.
If you use any of the m
Maybe you could clarify who this applies to. I have xbmc.python 2.0 in my
plugins and currently have the exact same revision of them in both the eden
and frodo repo. Does this apply to me? It's not clear what you mean by
depend on internal xbmc addons. How can any addon not import any of those
you
In case any one missed this email
Martijn
Op 19 dec. 2012 00:02 schreef "ronie" het volgende:
> Hi all,
>
> For a long time we have been using a major.minor.build version scheme
> for all addons.
> The only exception until now have been our internal addons.
>
> Over the past weeks we have made c
Hi all,
For a long time we have been using a major.minor.build version scheme
for all addons.
The only exception until now have been our internal addons.
Over the past weeks we have made changes to make sure all of our
internal addons
comply with this x.y.z version scheme as well.
If you are g
