-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Fedora 31, drop Fedora 29 #216
Conversation
Fedora will never have EPEL. This makes it easier to keep supporting Fedora.
Fedora 29 is EOL since November 26th. Since there's no actual code change, it'll still continue to work for users.
Puppet does not provide any packages for Fedora 31. |
Should we drop the acceptance tests for it or not list it as supported at all? |
Good question. Even if Puppet provides the required packages, facterdb might be the next problem. |
On the other hand, nothing has really changed between F30 and F31 so how much value do the unit tests with facterdb actually provide? |
I wonder how much sense it makes to test a rolling release. We do not do that with any other module. |
Fedora is not a rolling release. It has a very clear 6 month release schedule. this isn't for Fedora Rawhide and it's not like Arch. |
Good to know, but the Facts and Puppet packages will still not be available on time in the future. |
Puppet packages for Fedora 31 have been available a while now. I'm one of those peeps using this module on Fedora 31 (using a locally modified version), so would love to see this merged. |
Restarted the Fedora 31 builds |
@dhoppe any last comments? |
Fedora 29 is EOL since November 26th. Since there's no actual code change, it'll still continue to work for users. To make that happen, the Hiera hierachy is changed to allow setting variables per-OS.