On 27.10.2015, at 11:17, Nigel Magnay <[email protected]> wrote:
> And as someone else pointed out - it's far harder picking over all the > @deprecated obsolescence in core than it is visually parsing the code. Good news, everyone! http://jenkins-ci.org/content/jenkins-20-proposal-introduce-policy-api-deprecation (Let's continue that particular discussion in https://issues.jenkins-ci.org/browse/JENKINS-31035 ) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/86557B75-5A3B-4FF1-B3BC-069ADE6ACEFD%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
