Hi all, I have not been very active, and would like to let someone else step forward and maintain the plugin.
https://github.com/jenkinsci/build-flow-plugin Though I have not been developing much on the plugin, I tried to spend my time gating changes and making sure - or trying to - that contributions meet a certain standard: - changes should belong in the plugin (as opposed to extending in yet another plugin) - changes should make sense - hacks are discouraged, - changes should be tested - probably the most important point. Being a maintainer can hurt people's feelings, their changes are important to them; they dogfood the product and it keeps moving things forward. Yet, sometimes changes are not technically sound, un-tested, risky and a maintenance hell. This is when you come in : try to review the code, question the design, try to investigate older similar proposals, and guide them to a successful change. Thanks, Damien -- 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/acebc956-be05-42bd-8e9a-ab529f09444c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
