Update Tags for Packagist

[gordonbanderson]

The newest semantic version tag 2.0 is out of date with the current master branch, I'd prefer not to have to use dev-master. Could the current version be tagged with 2.1?

[gordonbanderson]

The tag 2.0 was added on 23/12/2014 so that's over a year without a composer update semver wise.

[micschk]

@gordonbanderson, I have lots of small tweaks of this module locally -- haven't had te time yet to properly update Git. Also, I have yet to take some time to look into SemVer... I've just given you push access, please go ahead and make the changes you require.

[gordonbanderson]

Regarding SemVer it took me a little while to get my head into it but it's actually quite simple.

If a version is likes of 2.0.0 then it will change as follows:

• 2.0.1 - a bug fix has been made on the 2.0.0 version. No functionality changes
• 2.1.0 - functionality has been enhanced, but in a backwards compatible non breaking manner (this is the change I was wanting to make which prompted this issue)
• 3.0.0 - new functionality is added that is not backwards compatible.

I can then do ```composer require "micschk/silverstripe-liveseo:~2" and provided semver is adhered to, whenever I update I know I will be updating to a version that is backwards compatible, i.e. things should not break :)

BTW I do not have rights to

• Update packagist for this module https://packagist.org/packages/micschk/silverstripe-liveseo
• Add packagist as a service hook in the module