ok Christoph as there is no real active committer I'll do the release

thanks a lot


On Tue, Jul 28, 2015 at 10:35 PM, Christoph Kutzinski <[email protected]> wrote:

> I can release the plugin, but I really feel any kind of responsibility as
> a maintainer of the plugin. So IMO you could just release it by yourself.
> Regarding the question of core compatibility: I usually update to previous
> before the current LTS release. The newest LTS seems too new to me most of
> the times and don't want to force users to be that much up-to-date.
>
>
> Am 28.07.2015 um 19:26 schrieb Arnaud Héritier:
>
>> Hi all,
>>
>>    We discovered an incompatibility between the wsclean plugin 1.0.4 and
>> the folder plugin
>>    See https://issues.jenkins-ci.org/browse/JENKINS-29682
>>    By a side effect of the cleanup done by @kutzi several years ago (
>>
>> https://github.com/jenkinsci/wsclean-plugin/commit/244e0e0264cf8e92b681048bc5d70ea7e44efd5b
>> ) the master branch is already the fixed and just needs to be released.
>>
>> tspengler or kutzi could you release it ?
>>
>>    I had a look at the plugin and this one is old and not really
>> maintained (the last release was done in January 2010 ...)
>>
>>    It raises the question to the updates to do on such old plugin. On my
>> side I did few updates (core compatibility 1.424 instead of 1.328) but
>> it is arbitrary
>>
>> https://github.com/aheritier/wsclean-plugin/commits/master
>>
>>    Do we have some rules about this ? When we are doing a release are we
>> always trying to target the oldest version possible of Jenkins or could
>> we just take care to be compatible with releases of the current LTS (or
>> the one before).
>>
>>    What do you think ?
>>
>> cheers,
>>
>> --
>> -----
>> Arnaud Héritier
>> http://aheritier.net
>> Mail/GTalk: aheritier AT gmail DOT com
>> Twitter/Skype : aheritier
>>
>> --
>> 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 [email protected]
>> <mailto:[email protected]>.
>> To view this discussion on the web visit
>>
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_QNpyYFqy%3D1QxYbu%3D945fka%3DZ-u0pxhDMvYOMB05tv-w%40mail.gmail.com
>> <
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_QNpyYFqy%3D1QxYbu%3D945fka%3DZ-u0pxhDMvYOMB05tv-w%40mail.gmail.com?utm_medium=email&utm_source=footer
>> >.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/55B7E7A6.4020702%40gmx.de.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8En%2B8ydcRvuwMOd2fQbmiLjfkCz5VuyrcSnD5rKKb8%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to