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
I'd argue that without a maintainer, a plugin would be better off
archived until someone with sufficient interest to maintain it
volunteers.
On Fri, Jan 22, 2021 at 3:05 AM ogondza wrote:
>
> I understand it feels strange, though it is the second best thing we can do
> in case we lack a
I understand it feels strange, though it is the second best thing we can do
in case we lack a maintainer.
On Wednesday, January 6, 2021 at 5:53:37 PM UTC+1 msi...@cloudbees.com
wrote:
> I'd prefer if this plugin has an actual maintainer. Otherwise, this
> also seems like false advertising that
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.
On Wed, Jan 6, 2021 at 10:45 AM 'Gavin Mogan' via Jenkins Developers
wrote:
>
> If you do a release and there are new bugs are you going to handle
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
On Wed., Jan. 6, 2021, 6:03 a.m. Marky Jackson,
wrote:
> Same, no objections
>
> On Jan 6, 2021, at 6:01 AM, Mark Waite wrote:
>
Same, no objections
> On Jan 6, 2021, at 6:01 AM, Mark Waite wrote:
>
>
> No objections from me.
>
>> On Wed, Jan 6, 2021 at 2:18 AM Oliver Gondža wrote:
>> 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.
No objections from me.
On Wed, Jan 6, 2021 at 2:18 AM Oliver Gondža wrote:
> 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]
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
