What do we want to do with the plugin-proposals component on Jira?

9 views
Skip to first unread message

Tim Jacomb

unread,
Apr 17, 2026, 9:44:06 AM (21 hours ago) Apr 17
to Jenkins Developers
Hi 

I'm looking into what should be done with the plugin proposals component on Jira:

There's 84 open and 380 issues total. It's one of the biggest remaining components on Jira.

Quickly reviewing them, they're mostly feature requests not really a 'plugin proposal'. Most are quite old.

Questions if any one has got any feedback?
* Do we want to have a plugin proposal issue tracker going forward? We could have an issue form on the jenkins core issue tracker to get a structured one? Or a different repo for it?
* Do we want to migrate the existing ones in for completeness? Or we could archive them in Jira?

Cheers
Tim

Mark Waite

unread,
Apr 17, 2026, 11:07:33 AM (20 hours ago) Apr 17
to jenkin...@googlegroups.com
On Fri, Apr 17, 2026 at 7:44 AM Tim Jacomb wrote:
Hi 

I'm looking into what should be done with the plugin proposals component on Jira:

There's 84 open and 380 issues total. It's one of the biggest remaining components on Jira.

Quickly reviewing them, they're mostly feature requests not really a 'plugin proposal'. Most are quite old.

Questions if any one has got any feedback?
* Do we want to have a plugin proposal issue tracker going forward? We could have an issue form on the jenkins core issue tracker to get a structured one? Or a different repo for it?

I don't see any significant benefit to tracking plugin proposals.  I'd rather not clutter the Jenkins core issue tracker with plugin proposals.
 
* Do we want to migrate the existing ones in for completeness? Or we could archive them in Jira?

I think we should archive them in Jira without migrating them to any other location.

Mark Waite
Reply all
Reply to author
Forward
0 new messages