Deprecating the Jenkow-plugin?

[Baptiste Mathus]

Hi,

See https://wiki.jenkins-ci.org/display/JENKINS/Jenkow+Plugin

I propose to deprecate this plugin for the following reasons:

• His author added a comment stating:
  The Jenkow plugin is not under active development any more.
• This plugin hasn't been released nor committed for more than 2+ years 
  
• There are only 7 installations in the world
• There're far more active alternatives today with the workflow and even build flow plugin.

I'll proceed on roughly 48h from now if nobody objects (~sunday). 

Please note that adding the deprecation label will have the effect that the Jenkow plugin will not be visible anymore from the Update Center.

Cheers

--

Baptiste

[Slide]

+1

--
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/CANWgJS78WJ98UYofG2CAi_4m5MR_EMF62aqrj91F%3DtipoQDJ5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Andrew Bayer]

+1

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVehbe-CSMLuZAz8Nci-c3%2B8ar8Y5fkAHQSCp1FuKoTNtw%40mail.gmail.com.

[Christopher Orr]

On 20/11/15 15:29, Baptiste Mathus wrote:
> *Please note that adding the deprecation label will have the effect that
> the /Jenkow plugin/ will not be visible anymore from the Update Center.*

Note that this also means that the infobox will stop being populated soon.

Therefore the deprecation notice on the wiki page, which says "The code
is still available", won't be helpful, as the GitHub link will soon
disappear.

Just something to think about if you're considering making a standard
wiki macro for this stuff (I briefly saw an IRC conversation on that
topic earlier) :)

From the good old Nabaztag example [0], a macro would probably need
something like this as configuration fields:

* Last known source code URL
* Archive link (just needs the artifact ID)
* Reason for removal (optional)
* Alternative plugins (optional)

Regards,
Chris

[0]:https://wiki.jenkins-ci.org/display/JENKINS/Nabaztag+Plugin

[Baptiste Mathus]

Done. 

IMO, that fact you reminded us Christopher makes having a macro for the "plugin-deprecated" label [1] a bit more than useful. (with the link to the last known sources as you say).

Having the std macro unpopulated because of that label makes reviving a plugin a bit harder than needed.

[1] for details, see discussion http://echelog.com/logs/browse/jenkins/1447974000 and http://echelog.com/logs/browse/jenkins/1448060400

--
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/564F8B4C.7020007%40orr.me.uk.

For more options, visit https://groups.google.com/d/optout.

--

Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !