On Mon, Jul 18, 2022 at 2:48 PM Alexander Brandes <[email protected]> wrote: > Although, I don't think we need two bots alongside for different package > ecosystems, when one bot can do both.
We do if we want to optimize globally (organization-wide) rather than locally (repository-wide) for decreased cognitive load, as I already explained in my last post. And successful long-term maintenance involves carefully managing cognitive load, so I think we do want to optimize globally. Combining multiple Java dependency updates together is indeed an advantage, but I do not think it is a compelling enough advantage to deviate from the technology stack we already use to manage Jenkins plugin Java dependencies given the concomitant permanent increase in cognitive load associated with using two different technology stacks concurrently for the same purpose (managing Java dependencies). If combining multiple Java dependency updates together is the only advantage, then I would be in favor of changing the technology stack used for managing Jenkins core Java dependencies if and only if the technology stack used to manage Jenkins plugin Java dependencies were also changed. -- 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/CAFwNDjrHUe4mN-oN529FVXKHOrdYXWyp_BphCqW5TC5qkNo8sQ%40mail.gmail.com.
