On Fri, Aug 31, 2018 at 8:53 AM Daniel Beck <[email protected]> wrote: > [RPU is] the _only_ part that's required [to change plugin maintainership], > as it is where upload permissions are defined.
Well…effectively the new maintainer also needs write permission to the source repository. While it is technically possible to locally edit the `<version>` of a plugin and `mvn deploy` the result as a release, we would certainly not want to encourage people to do that. Same for cutting the release out of a non-@jenkinsci fork. (Not sure of the exact process when using Gradle but I imagine it is similar enough.) So I would treat updates to the GitHub access control metadata as a required part of any adoption process. -- 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/CANfRfr3c7tF6KduQkAB-rtejXxzB_rRDuhF0E_rJtFwS12%3Dqiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
