Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-12 Thread Baptiste Mathus
Inline. Le 4 janv. 2016 3:31 PM, "Christopher Orr" a écrit : > > Hi all, > > > On 04 Jan 2016, at 12:03, Daniel Beck wrote: > > On 04.01.2016, at 11:29, Tomas Bjerre wrote: > >> I am also developing plugins for Stash/Bitbucket Server

Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-04 Thread Daniel Beck
On 04.01.2016, at 11:29, Tomas Bjerre wrote: > I am also developing plugins for Stash/Bitbucket Server and I must say that > their approach is much better. They have the Atlassian Marketplace where > plugins are published if they have a clear use case, the people at

Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-04 Thread Nigel Magnay
> > > Can't we let people do what they want instead of forcing people to deal > with code they don't want to. We are actively harming jenkins community by > overly policing plugins. > > ​A thousand times this. I was about to say "you can, there's no need to fork into jenkinsci, just release from

Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-04 Thread Tomas Bjerre
I am also developing plugins for Stash/Bitbucket Server and I must say that their approach is much better. They have the Atlassian Marketplace where plugins are published if they have a clear use case, the people at Atlassia can successfully test that use case and it is documented properly.

Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-04 Thread Christopher Orr
Hi all, > On 04 Jan 2016, at 12:03, Daniel Beck wrote: > On 04.01.2016, at 11:29, Tomas Bjerre wrote: >> I am also developing plugins for Stash/Bitbucket Server and I must say that >> their approach is much better. They have the Atlassian Marketplace

Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-03 Thread Surya Gaddipati
Can't we let people do what they want instead of forcing people to deal with code they don't want to. We are actively harming jenkins community by overly policing plugins. Not only is this heavy handed process extremely inefficient ( I stopped caring about my plugin after begging for it to be

Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-03 Thread Tomas Bjerre
I dont want to maintain this plugin. I tried to but in my opinion it should be re-written completely. A library for parsing reports should be developed in a separate project and used in that new plugin. The code quality is poor and alot of time is needed to manage all the submitted issues.

Re: Plugin Hosting Request: Violations Reboot Plugin

2016-01-03 Thread Baptiste Mathus
Hi Tomas, Are you still considering working on that plugin? You've released the experimental versions some 6 months ago. Do you think it's ready to be released as 0.8. I'm asking because as of that PR of mine 5 days ago , the

Re: Plugin Hosting Request: Violations Reboot Plugin

2015-06-01 Thread domi
-1 I think its very strange to complain about the maintenance state of a plugin and therefore fork the same and release it with the reason to mark it as unstable… this will simple just lead to an other unmaintained plugin with no additional value for any user. my 2c Domi On 01 Jun 2015, at

Re: Plugin Hosting Request: Violations Reboot Plugin

2015-06-01 Thread Tomas Bjerre
I totally agree! I just dont see it happen. Its been almost 3 years since last release. I don't feel comfortable with taking descisions on what PR:s to merge. How much testing to do before release. Setting coding standard... Den måndag 1 juni 2015 kl. 06:17:13 UTC+2 skrev Richard Bywater: -1

Re: Plugin Hosting Request: Violations Reboot Plugin

2015-06-01 Thread Stephen Connolly
Just cut releases with (next major version)-alpha-01 until you are confident enough An -alpha- version number will only show in the experimental update centre which needs to be added explicitly by adventurous users. On Monday, June 1, 2015, Tomas Bjerre tomas.bjerr...@gmail.com wrote: I

Re: Plugin Hosting Request: Violations Reboot Plugin

2015-06-01 Thread Tomas Bjerre
Ok nice! I'll make an attempt at working for a release in the main repo. You can consider the hosting request as revoked. Den 1 jun 2015 16:50 skrev Stephen Connolly stephen.alan.conno...@gmail.com: Just cut releases with (next major version)-alpha-01 until you are confident enough An

Re: Plugin Hosting Request: Violations Reboot Plugin

2015-05-31 Thread Richard Bywater
-1 for creating a forked version. If there is an issue with the existing plugin I'd much rather see it being worked on to bring it up to standard rather than creating a completely separate plugin which could lead to confusion amongst users. My 2 cents... Richard On 10:30AM, Mon, 1/06/2015 Tomas

Re: Plugin Hosting Request: Violations Reboot Plugin

2015-05-31 Thread Tomas Bjerre
Ok, but something needs to be done here. The current version was released on 12 oct 2012. The current version in Maven repos is from 22 feb 2010. The open issues dates back to 2011. Even PR:s from 2011 has not yet been merged. It seems the project is more or less dead right now... I don't have