Hello all,
Now that puppet 2.7 is in EPEL61 (thanks Sam!), we can finally start
working toward dropping 2.6 support. I'd propose to keep 2.6 in our
testing matrix for a bit so people can upgrade their environments.
The next step would be to unpin puppetlabs-postgresql and upgrade it to
3.02. While we unpin, I'd also like to upgrade all our travis test
matrices to test 2.7, 3.0 and 3.latest.
Opinions?
> From: "Ewoud Kohl van Wijngaarden" <ewoud@kohlvanwijngaarden.nl>
> To: foreman-dev@googlegroups.com
> Sent: Monday, December 2, 2013 8:43:31 AM
> Subject: [foreman-dev] Puppet 2.6 support
>
> Hello all,
>
> Now that puppet 2.7 is in EPEL61 (thanks Sam!), we can finally start
> working toward dropping 2.6 support. I'd propose to keep 2.6 in our
> testing matrix for a bit so people can upgrade their environments.
>
> The next step would be to unpin puppetlabs-postgresql and upgrade it to
> 3.02. While we unpin, I'd also like to upgrade all our travis test
> matrices to test 2.7, 3.0 and 3.latest.
This means we need to tell people to enable squeeze-backports on Debian, right?
Anyhow, +1 to the plan outlined above.
Opinions?
–
You received this message because you are subscribed to the Google Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I'm not certain I follow these two paragraphs. How long will we keep
2.6 tested + supported?
I'm fine with moving to 2.7 as a minimum for Foreman 1.4, and happy to
require that in our installer modules with immediate effect.
–
Dominic Cleal
Red Hat Engineering
>
> > From: "Ewoud Kohl van Wijngaarden" <ewoud@kohlvanwijngaarden.nl>
> > To: foreman-dev@googlegroups.com
> > Sent: Monday, December 2, 2013 8:43:31 AM
> > Subject: [foreman-dev] Puppet 2.6 support
> >
> > Hello all,
> >
> > Now that puppet 2.7 is in EPEL61 (thanks Sam!), we can finally start
> > working toward dropping 2.6 support. I'd propose to keep 2.6 in our
> > testing matrix for a bit so people can upgrade their environments.
> >
> > The next step would be to unpin puppetlabs-postgresql and upgrade it to
> > 3.02. While we unpin, I'd also like to upgrade all our travis test
> > matrices to test 2.7, 3.0 and 3.latest.
>
> This means we need to tell people to enable squeeze-backports on Debian, right?
I think we already require that because in squeeze there's an ancient
2.6 version which we don't support. @Greg?
Anyhow, +1 to the plan outlined above.
Opinions?
> > Hello all,
> >
> > Now that puppet 2.7 is in EPEL6[1] (thanks Sam!), we can finally start
> > working toward dropping 2.6 support. I'd propose to keep 2.6 in our
> > testing matrix for a bit so people can upgrade their environments.
> >
> > The next step would be to unpin puppetlabs-postgresql and upgrade it to
> > 3.0[2]. While we unpin, I'd also like to upgrade all our travis test
> > matrices to test 2.7, 3.0 and 3.latest.
>
> I'm not certain I follow these two paragraphs. How long will we keep
> 2.6 tested + supported?
My idea was to wait a short period of time (say a week or 2) before was
drop 2.6 support. After that period we can upgrade dependencies which
had to be held back because of lacking 2.6 support. That also means
updating our testing matrices for all our modules as we discussed a
couple of times on IRC.
> I'm fine with moving to 2.7 as a minimum for Foreman 1.4, and happy to
> require that in our installer modules with immediate effect.
I suppose that works as well. People who upgrade their modules, should
also upgrade their puppet masters. People who run git versions are
unlikely to use 2.x anyway.
Indeed, it's required today as oldstable/Squeeze contains 2.6.2
(pre-param classes).
–
Dominic Cleal
Red Hat Engineering