deploy-plugin maintainer inactive

[Robin Jansohn]

It seems that @frekele 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.

[Oleg Nenashev]

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

[Robin Jansohn]

Hi Oleg,

thanks for the quick reply. I don't really know my way around Google mailing lists, how do I CC someone? I've forwarded your reply to the maintainer but I guess that is not what you meant?

Kind regards,

Robin

[Oleg Nenashev]

Added Leandro to Cc

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/Z35x2qyFHDg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/49676620-fbd2-4c50-b78b-0ef20feb0c83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Robin Jansohn]

Two weeks have passed. What happens next?

[Oleg Nenashev]

We can transfer the permissions now.

Please provide your JIRA and GitHub IDs.

On Thu, Jul 18, 2019 at 11:22 AM 'Robin Jansohn' via Jenkins Developers <jenkin...@googlegroups.com> wrote:

Two weeks have passed. What happens next?

--

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/Z35x2qyFHDg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e4da6940-676c-410e-80e2-7e29e003c29c%40googlegroups.com.

[Oleg Nenashev]

Also, please submit a pull request to  https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-deploy.yml in order to get release permissions.

Doc: https://github.com/jenkins-infra/repository-permissions-updater#requesting-permissions 

[Robin Jansohn]

While I can take over for now I have to mention that I will be on parental leave from August on (6 months) and won't be having much time to maintain the plugin.

If you still think this is a good idea:

Jira ID: jansohn

GitHub ID: jansohn

On Thursday, 18 July 2019 11:26:30 UTC+2, Oleg Nenashev wrote:

We can transfer the permissions now.

Please provide your JIRA and GitHub IDs.

On Thu, Jul 18, 2019 at 11:22 AM 'Robin Jansohn' via Jenkins Developers <jenkin...@googlegroups.com> wrote:

Two weeks have passed. What happens next?

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/Z35x2qyFHDg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to jenkin...@googlegroups.com.

[Oleg Nenashev]

Thanks for the clarification and the disclaimer! There is enough time to cut a release and to address feedback if something goes horribly, so I think it would be better than keeping the plugin in limbo. If you have some time to periodically check for new issues, it is also better than the current state. Of course, family first :)

If you are concerned about an impact of the changes, you could just integrate the changes and make other improvements (documentation, fixes, etc.) without actually doing a release.

Best regards,

Oleg

To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8870bb3f-1617-46f1-ab46-70d54c9d5286%40googlegroups.com.