Bump needed ruby version for forge release

[bastelfreak]

Our current release part in the .travis.yml:

  on:
    tags: true
    # all_branches is required to use tags
    all_branches: true
    # Only publish if our main Ruby target builds
    rvm: 1.9.3
    condition: "$FUTURE_PARSER = yes"

We should bump that, we don't test on 1.9.3 anymore. Which version do we want to target here? 2.3.0? I would use that one because it does rubocp + spec tests. But then we may remove 2.3.0 from the allow_failures category.

[jyaworski]

We do test on 1.9.3 via jruby-193mode.

[bastelfreak]

Do we want that a jruby version as our main target?

[jyaworski]

In my opinion, yes. It's puppetserver 1.1.3, which is the 'latest stable' per-se on 3.x.

[rnelson0]

It doesn't matter which rvm, really, you just want it to be unique. It was set to 1.9.3 because `FUTURE_PARSER` isn't unique, then one build succeeds and another generates an error, marking the build as failed which shows up in the badges.

[rnelson0]

This does need to be changed before its closed. There is currently no 1.9.3 in the matrix so no new builds will deploy. Changing it to 2.2 should work. On a tablet right now though.

[bastelfreak]

ahhhhhh

[bastelfreak]

so we talked so much about semantic versioning in the last days. Should we add a new tag to this repo and if so, is this a minor or patch release? I would vote for patch.

[rnelson0]

Patch

Rob Nelson
[email protected]

[juniorsysadmin]

Always update PATCH for modulesync_config tags

[bastelfreak]

I pushed 0.5.1.