On Wed, Feb 20, 2013 at 10:53 AM, Stephen Connolly
<[email protected]> wrote:
>>
>> On 20 February 2013 16:43, Les Mikesell <[email protected]> wrote:
>>>
>>> On Wed, Feb 20, 2013 at 10:26 AM, Fisher, Allen <[email protected]>
>>> wrote:
>>> > OK. I need some more help and to let a small rant loose.
>>>
>>> I agree on the rant - not so much on the choice to fix a security
>>> problem, but certainly about communicating the fact that updating
>>> _will break_ working systems and documenting how to make them work
>>> again. I can sort-of understand this on the trunk releases, but
>>> what's the point of having an LTS version here?
>>
>>
>> The whole point of LTS is to give you something where only *critical bugs*
>> and *security* fixes are applied during the life of the LTS. All other
>> changes are left for the next LTS.
>>
>
> Oh and I agree that the changelog should have had a link to the security
> advisory on the wiki, so that people would have been more aware of the
> changes required. I raised this with KK.
And, as this thread points out - we need a usable workaround for
win2008R2 slaves. I'm fine with installing some flavor of ssh if that
would work, but I can't be the first/only one to run into the problem.
Why is it a surprise?
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
