EPEL Updating Puppet to 2.7.x

[Kevin Fenzi]

On Tue, 6 Aug 2013 12:30:32 -0400 (EDT)
Sam Kottler <skottler at redhat.com> wrote:

> Hi,
> 
> We've had this conversation at least once before, but I figured I
> would bring it up again [1].
> 
> You can see in Mike's original post that there a number of reasons we
> should bump to the 2.7 series in EPEL, but primarily it's because
> critical bug fixes aren't ending up in the 2.6 series any longer. I
> don't want to completely rehash the conversation in the old thread,
> but I think that it's important for EPEL to be providing updates on a
> maintained branch so I'd like to propose that both EPEL 5 & EPEL 6
> packages get bumped to 2.7. This plan will largely avoid the issues
> that come with the potentially tricky upgrade path for users between
> 2.x and 3.x.
> 
> Thoughts?

So, could you remind us again of the various interactions of the
versions? (or is there a doc on it?)

Ie, of 2.6, 2.7, 3.0, which versions clients can talk to which versions
servers? 

Also, is there any changes people would need to make to their puppet
manifests between 2.6 and 2.7?

In general I'm in favor of getting it updated... 

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/epel-devel/attachments/20130807/541af3df/attachment.sig>