[skin.confluence] v5.0.4

[Hitcher]

Add-on details:

• General
  • Add-on name: Confluence
  • Add-on ID: skin.confluence
  • Version number: 5.0.4
  • Kodi/repository version: Omega
• Code location
  • URL: https://github.com/xbmc/skin.confluence/tree/Omega
  • Revision/tag: Latest
  • Branch: Omega

Description of changes:

• Add 'Check Previous Episode' layout
• Bump version

Checklist:

• [x] My code follows the add-on rules and piracy stance of this project.
• [x] I have read the CONTRIBUTING document
• [x] Each add-on submission should be a single commit with using the following style: [plugin.video.foo] v1.0.0

Additional information :

• Submitting your add-on to this specific branch makes it available to any Kodi version equal or higher than the branch name with the applicable Kodi dependencies limits.
• add-on development wiki page.
• Kodi pydocs provide information about the Python API
• PEP8 codingstyle which is considered best practice but not mandatory.
• This add-on repository has automated code guideline check which could help you improve your coding. You can find the results of these check at Codacy. You can create your own account as well to continuously monitor your python coding before submitting to repo.
• Development questions can be asked in the add-on development section on the Kodi forum.

[ronie]

updated, thx! https://github.com/xbmc/repo-skins/commit/98f49d09595bc29544141f16a43c8e402009ab43

let's keep an eye on it if it makes it into the repo this time.

[MikeSiLVO]

Every time my skin was updated in repo it would've populated by now. Since it hasnt yet I assume there is either a new repo issue with adding skins or some other unknown related to confluence...

Only big changes I notice that could be a contributing factor is the 720p --> 1080p conversion but I am only guessing on that.

There is also a v in the version number for 4.8.3 in the addon.xml

Is that marking it higher than 5.0.3/4??

[MikeSiLVO]

@ronie @Hitcher Maybe bump nexus to 4.8.4 without the v and see if helps? Not sure if v4.8.3 existing would cause further issue since it seems versioning uses alphabetical order so that would be above anything else using just numeric.

Alternatively, if that is the issue, then making Omega v5.0.5 or something could also work.

[ronie]

yeah.. you could be right there. i hadn't noticed this v made it's way into the version number.

i'd rather prefer to get rid of it instead of continuing with version="vX.X.X" i'll check what our server admins think of it..