On Wed, Mar 8, 2023 at 5:13 AM Mark Waite <mark.earl.wa...@gmail.com> wrote: > I made that mistake with a plugin that I adopted a few months ago. It's last > release had been done many years ago. I adopted it and made the flawed > assumption that the master branch was in good condition, ready to release. I > released a new version of the plugin from the master branch and was then > dismayed to have reports from users that the new release included a > regression. I reverted most of the changes that had been made on the master > branch in those intervening years and released a new version of the plugin > without those regressions.
Worse, I once adopted a plugin whose previous maintainer had not merged a security fix back to the main branch, meaning that releasing the main branch would have reintroduced the security issue. Thankfully, I noticed that before doing a release. In general, I would advise new maintainers to carefully review the diff from the last release up until the current point in time to ensure that they are prepared to deal with any regressions when doing the next release. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpP5fF61M_VvgsGEcZtCZbLWub_Tg1z2e8s35MPeND41Q%40mail.gmail.com.
