Yes, I know that. But it would also be handy if a change that had security implications at least had a link to the security advisory in the change log ;)
-Allen On Feb 21, 2013, at 6:51 PM, Christopher Orr <[email protected]> wrote: > On 02/20/2013 06:36 PM, Stephen Connolly wrote: >> I'm not complaining about the >> decision to make the change. I just don't see why the side effects >> had to be a surprise. >> >> They were hinted at in the security advisory... I do agree that there >> could have been better wording for that though > > This is the key point of the discussion for me: there *was* a security > advisory posted and it mentioned that changes would be required. > > If you're maintaining a Jenkins instance which you/others rely on, then you > should be subscribed to and reading the security advisories mailing list. > > Regards, > Chris > > -- > 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. > > > -- 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.
