Nigel Kersten <ni...@puppetlabs.com> writes:
> On Wed, Nov 24, 2010 at 4:35 PM, Daniel Pittman <dan...@rimspace.net> wrote:
>> Gary Law <gary...@garylaw.net> writes:
>>> On 24 November 2010 23:50, Nigel Kersten <ni...@puppetlabs.com> wrote:
>>>> I mentioned this in an earlier thread, but here's a dedicated one.
>>>>
>>>> We made a big change between 0.24.x and 0.25.x where we moved from
>>>> XMLRPC to REST.
>>>>
>>>> How do people feel about us dropping all XMLRPC support from 2.7.x,
>>>> such that it only supported Puppet clients 0.25.x and higher?
>>>
>>> That depends on the support model (for bug fixes) puppetlabs is prepared to
>>> support.  I'd be inclined to support all recent client releases under a year
>>> old at a minimum. Longer for the real enterprisey conservative shops.
>>> Remember, a fair few places in the UK are still-running-IE-6 shops.
>>
>> One of the bits of feedback I have had from various folks out in the wider
>> world is that (right or wrong) they already feel that Puppet has a pretty 
>> fast
>> upgrade cycle and a very poor backward compatibility story.
>>
>>> My firm would be happy for a six month release/patch cycle, but we're not
>>> change averse. Others firms I've worked for are.
>>
>> *nod*  I think that the Debian maintainers would be less than thrilled at
>> support for the versions in Debian/stable being dropped totally, and users of
>> Debian would be unthrilled with needing something out of backports to talk to
>> their newer Puppet server.
>
> To clarify, I'm not saying we're dropping support for people running those
> versions, just dropping support for 2.7.x server to talk to 0.24.x clients
> and earlier.

As long as that clarification is in the final announcement, folks should
hopefully be a bit less unhappy about the change, indeed. :)

[...]

> I'm suggesting this for 2.7.x. Are people really likely to be running
> 2.7.x servers with 0.24.x clients?

Well, it would be convenient for me to be able to do that, because then my
host rollout would be "install the upstream package, and have puppet manage
the process of self-updating to our own packages".

Not essential, though, and:

> I think I would advise people that's not a particularly wonderful
> combination anyway, given how much code is shared between the server and the
> client.
>
> If you're packaging puppet servers to run 2.7.x, you've already done
> all the work to package puppet clients for 2.7.x.

...I tend to agree with this.
        Daniel
-- 
✣ Daniel Pittman            ✉ dan...@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to