Hi Robin, Thanks a lot for the fix! It is shocking to see a non-compilable code in the master branch. Regarding the request, right now we have no process for marking plugins for adoption without an explicit confirmation from the previous maintainer. We can only transfer ownership after a 2 week timeout if the maintainer is no responsive. Please CC him in this thread.
More info about the process: https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin BR, Oleg On Monday, July 1, 2019 at 11:39:37 AM UTC+2, Robin Jansohn wrote: > > It seems that @frekele <javascript:> has given up maintaining the plugin > https://github.com/jenkinsci/deploy-plugin as PRs are open for over 1.5 > years without being merged *“[…] because the master branch contains > several errors.”* ( > https://github.com/jenkinsci/deploy-plugin/pull/30#issuecomment-367475275 > ). > > > > I’ve created a PR (https://github.com/jenkinsci/deploy-plugin/pull/34) > which fixes the current master branch almost two weeks ago but I got no > reaction from the maintainer. > > > > I think the plugin should be marked for adoption. I also hope that as a > short term solution someone with write access can merge the PR to fix the > master and publish a new release so people can finally use the pipeline > functionality. > -- 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/24b0eeb3-5ea8-4fa5-8e19-6cd74f31444b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
