[dev.icinga.com #12658] Decide whether or not to drop support for Puppet 3.x and below

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12658

Created by arioch on 2016-09-06 11:36:53 +00:00

Assignee: (none)
Status: Closed (closed on 2016-09-09 09:12:55 +00:00)
Target Version: v0.2.0
Last Update: 2016-09-09 09:12:55 +00:00 (in Redmine)

---

... due to new language features in Puppet 4 that break the older versions.

[icinga-migration]

Updated by bsheqa on 2016-09-07 08:14:35 +00:00

• Target Version set to v0.2.0

[icinga-migration]

Updated by Reamer on 2016-09-08 00:07:26 +00:00

Please do not drop puppet 3 support.

I think we can drop it in later versions.

[icinga-migration]

Updated by bsheqa on 2016-09-08 07:50:59 +00:00

Here's my point of view about that:

As Puppet 3 will probably reach its end of live by the end of this year, it’s tempting to drop support for it in this module. Arguments like parameters.pp are not longer 'best practice' in modules and types will help in testing and development are completely valid. On the other hand, moving from Puppet 3 to 4 is a huge step for most of the environments out there today. Quite the contrary, it does not look like people will stop using Puppet 3 in the near future. Abandoning support for it would exclude many people from using this module. Therefore, even if there are reasons to only support version 4 of Puppet, in my opinion it’s also important to keep current Puppet 3 users. Being able to run on both versions is a good compromise at this time and leaves us every option open for the future.

[icinga-migration]

Updated by bsheqa on 2016-09-09 09:12:55 +00:00

• Status changed from New to Closed
• Done % changed from 0 to 100