get the release candidates, if you're available to assist with testing release
candidates for long term support.
Mark Waite
>
> From: Chris Withers
>To: jenkinsci-users@googlegroups.com
>Sent: Thursday, July 5, 2012 11:27 AM
>Subject: jenkins
Les Mikesell kirjoitti 6.7.2012 kello 1.01:
> On Thu, Jul 5, 2012 at 4:58 PM, Sami Tikka wrote:
>>
>> AFAIK there is nothing in the Jenkins build process that tests plugins.
>>
>> There are something like 700 plugins in github.com and maybe some more on
>> subversion. But, as Jenkins is open-
On Thu, Jul 5, 2012 at 3:01 PM, Les Mikesell wrote:
> On Thu, Jul 5, 2012 at 4:58 PM, Sami Tikka wrote:
>>
>> AFAIK there is nothing in the Jenkins build process that tests plugins.
>>
>> There are something like 700 plugins in github.com and maybe some more on
>> subversion. But, as Jenkins is
On Thu, Jul 5, 2012 at 4:58 PM, Sami Tikka wrote:
>
> AFAIK there is nothing in the Jenkins build process that tests plugins.
>
> There are something like 700 plugins in github.com and maybe some more on
> subversion. But, as Jenkins is open-source-software, there aren't too many
> people who ha
Chris Withers kirjoitti 5.7.2012 kello 20.27:
> I'm a know-nothing when it comes to Jenkins own development process, but does
> it perhaps need to slow down a little and focus on quality and stability?
> Does the Jenkins build process do anything to check what plugins will break
> with a parti
Hi All,
A little alarmed to read this:
"""
I have no inclination to continue beyond that version until a new
Jenkins LTS is cut. I am not going to be spending any more time or
energy supporting plugins beyond the latest Jenkins LTS. I'm sorry, but
I have a lot of things I want to do with my t
