Time for a new release!

[faxm0dem]

I stumbled on an issue where my ignored paths were... ignored.
Please prepare a new release, thanks!

[Perdjesk]

+1 1.1.0...master

A cleaning of issues would be welcomed too. #422 and #417 (maybe?) seem to have been fixed.

[stig]

+1 I am not able to use the arrow_alignment check because of #416, which is fixed in master.

[akerl]

Bump. Would rock to get a new release cut, I'm running into issues with the linter not checking my files that are fixed on master, as well as config.relative not being settable in the Rakefile

[keithherron]

+1

[mterzo]

+1

[Kriechi]

👍

[cyberious]

👍 Overdue, if you don't want to maintain perhaps moving it to Puppet-Community or if somebody from PuppetLabs would want to take it over

[walkamongus]

👍

[albertux]

👍

[ghoneycutt]

Use this in your Gemfile to get the latest code.

gem 'puppet-lint', :git => 'https://github.com/rodjek/puppet-lint.git'

[cyberious]

I would prefer the latest releases in ruby gem and then we can also proxy these through artifactory or pulp instead of pulling from the internet at all times.

[cdenneen]

👍

[albertux]

for now use @ghoneycutt solution if you are using Gemfile

if you are installing puppet-lint in your system use:

gem install specific_install
gem specific_install -l https://github.com/rodjek/puppet-lint.git

[alex-harvey-z3q]

+1

[rnelson0]

@rodjek Can you publish a new version of the gem, either 1.2.0 or 2.0.0?

[rmestrum]

@rodjek Can you please publish a new version of the gem

[rnelson0]

It looks like we can now release a new gem. The question is, what should the version number be? 1.1.1, 1.2.0, or 2.0.0?

I think there have been too many changes to be a point release, and that there are no backwards incompatible changes but I don't have a full history on the impact of all the changes to be sure of either. I'll start reviewing changes in detail but would like to hear others thoughts as well.

[rnelson0]

There are also some 71 Issues and 25 pull requests, but a lot of users are pulling from master so I'm confident it could be published as is. If there are any that you believe must be resolved before a new gem is published, please mention them here.

[slm0n87]

+1

[albertux]

+1

[kylog]

@rnelson0 I agree that this isn't a 1.1.1. As for 1.2.0 vs 2.0.0, I took a scan through what's in master, and the only change that looked possibly to be breaking was #419, e.g. if someone were using --no-80chars-check or PuppetLint.configuration.send("disable_80chars").

Thoughts?

Mostly just psyched that we can release a new gem :)

[rnelson0]

That reduces the options to:

1. 1.2.0
2. 2.0.0

I don't see a way to do voting on GitHub. I am leaning toward 2.0.0 myself. If no-one has any complaints by Wednesday @ 1200 UTC, we'll push out version 2.0.0 to rubygems.

Edit: Thumbs up vote to see 2.0.0 on Wednesday. Thumbs down and a comment to see something else!

[ahpook]

@rnelson0 looks good to me, i added a +1 reaction to your post - if people have -1s they can give you a thumbs down!

[daenney]

I would prefer to see a 2.0.0 that included the necessary Puppet 4 related fixes but I guess that can be another bump. There's a bunch of fixes in master that we can really do with an actual release for.

[rnelson0]

@daenney I would too, but I think the backlog is pretty large right now and it's best to start the 2.x train then start merging them in as we clear it out.

[rnelson0]

Puppet-lint v2.0.0 is now available. Happy downloads! https://rubygems.org/gems/puppet-lint/versions/2.0.0

[rnelson0]

Thank you to everyone for your assistance in getting this release out!

[albertux]

Thank you @rnelson0