I recently looked at Basil's PR migrating deprecated EE8 APIs to EE9: https://github.com/jenkinsci/jira-plugin/pull/635.
Thank you for taking on this task—it’s much appreciated! While reviewing the PR, I noticed a naming convention that I had hoped we’d moved past, hence my stupid comment in the PR. This led me to discover https://github.com/jenkinsci/stapler/pull/482, which had been reviewed by several contributors without raising concerns about the class naming. I decided it might be worth starting a discussion about this. 😊 Wouldn’t it enhance readability and maintainability to follow a consistent naming convention, such as the approach Jetty uses? Specifically, this could mean creating a dedicated package for such migrations. This way, we ensure clarity and maintainable organization for the future. Ref: https://github.com/jenkinsci/jira-plugin/pull/613/files#diff-424c14a1c2b58da4b0795ac30fb529b8b0c021a59ed356f0a68297c0083d8f78R29 Regards, Radek -- 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/d289d22c-d75b-45b1-bef3-6a7342640bbcn%40googlegroups.com.
