That all makes sense, though to implement that we need a policy to remove deprecated API first. Removing non-private fields should be done by deprecating it first.

I am tracking [1] for this effort. I would like to have a look at early deprecated API use detection.

[1] https://issues.jenkins-ci.org/browse/JENKINS-31035

--
oliver

--
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/op.x6rlt6e0sbfict%40arch.
For more options, visit https://groups.google.com/d/optout.

Reply via email to