On Thu, May 21, 2026 at 4:22 AM Ullrich Hafner <[email protected]> wrote:
> Is there a simple way to fill the @since tags in the code base when a > plugin uses CD? > For https://www.jenkins.io/doc/developer/plugin-development/mark-a-plugin-incompatible/ we do document https://www.jenkins.io/doc/developer/publishing/releasing-cd/#noting-incompatible-changes Do you actually need `@since` tags? They are useful in Java Platform APIs since you might reasonably want to run on some different Java versions and so want to check if you are using something you should (though `-release` verifies this anyway). For everything else I have always found them useless. Either I have already updated my library dependency to a version containing the new API, in which case I can freely use it—why should I care whether older releases included this API?—or I have not, in which case the API would not be offered in my IDE to begin with. -- CONFIDENTIALITY NOTICE:_ This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email._ -- 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1Gur8H%2BuSH9Wf-HYz6NdeU5Q2F_9C-k5uBmWEKCXvfig%40mail.gmail.com.
