Start 0.3.0 deveploment cycle.

The following notes apply:

a) We reserve versions 0.2.6 - 0.2.9 for any eventual bug fix release of
   0.2.5 we should need to cut in case we receive reports of errors or
   regressions. We will create a `0.2.5-maintenance` branch to perform
   this work there if needed.

   In retrospect, at least one of the 0.2.1 - 0.2.5 releases should have
   been named 0.3.0, etc. but alas. I didn'think about semver back then.

b) We will try to update the version (0.2.11, 0.2.12, ...) every time we
   implement a new feature in our path to 0.3.0. This way, if users
   install work-in-progress ZIP files from GitHub they can report us
   such version IDs and these versions still will increment monotonica-
   lly. I don't think we need to release these versions to the Kodi
   addons repo.

   We will set the version to 0.3.0 just before releasing it to Kodi
   addon repos.

addon.xml

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 <addon id="service.subtitles.subdivx"
        name="Subdivx.com"
-       version="0.2.5"
+       version="0.2.10"
        provider-name="cramm">
   <requires>
     <import addon="xbmc.python" version="2.14.0"/>

service.py

@@ -44,7 +44,7 @@
 __author__     = __addon__.getAddonInfo('author')
 __scriptid__   = __addon__.getAddonInfo('id')
 __scriptname__ = __addon__.getAddonInfo('name')
-__version__    = '0.2.5'
+__version__    = '0.2.10'
 __language__   = __addon__.getLocalizedString
 
 __cwd__        = xbmc.translatePath(__addon__.getAddonInfo('path')).decode("utf-8")