Releasing JCasC support for ghprb-plugin

[Oliver Gondža]

Hey, there is a long anticipated feature merged in in the plugin[1][2],
but no maintainer appears to be active to cut a release.

Are there any objections if I step in a do the release?

[1] https://github.com/jenkinsci/ghprb-plugin/pull/731
[2] https://issues.jenkins-ci.org/browse/JENKINS-55793
--
oliver

[Mark Waite]

No objections from me.

--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f3e65b25-477d-a780-ceae-eb8dec945f40%40gmail.com.

[Marky Jackson]

Same, no objections 

On Jan 6, 2021, at 6:01 AM, Mark Waite <mark.ea...@gmail.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtETdyEZtHzG2%2BLGBHyBmKHZPTjLQffozt16GWYb%3DP_htg%40mail.gmail.com.

[Gavin Mogan]

If you do a release and there are new bugs are you going to handle them?

Without a maintainer it seems like deploying to prod and not monitoring afterwards.

Gavin

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CE90DAE5-AF7D-452E-BAAB-6DD82A6B0B5A%40gmail.com.

[Matt Sicker]

I'd prefer if this plugin has an actual maintainer. Otherwise, this
also seems like false advertising that the plugin is still supported
by anyone.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dut0W%3DJyR48uxTvPpUgZg2vS1nRsAtHREKW%2BGsbjfXRX%3Dw%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

[ogondza]

I understand it feels strange, though it is the second best thing we can do in case we lack a maintainer.

[Matt Sicker]

I'd argue that without a maintainer, a plugin would be better off
archived until someone with sufficient interest to maintain it
volunteers.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8c9149bf-b71b-4184-a280-2280ad1eeb66n%40googlegroups.com.

[Oliver Gondža]

CCing the latest appointed maintainer.

On 25/01/2021 18.55, Matt Sicker wrote:
> I'd argue that without a maintainer, a plugin would be better off
> archived until someone with sufficient interest to maintain it
> volunteers.

We have plenty of plugins that are crucial to thousands of users with no
active maintainer. It is far from ideal, but yet the way it is.

I am concerned that if we insist of someone adopting plugins in order to
move some issue forward, we will only encourage people to make reckless
commitments and as a result have more plugins with _inactive_
maintainers appointed (since they would become maintainers to fix an
issue or two, but will not provide long term mainenance) and higher
maintainer fluctuation.

oliver