<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dang</author><text>This release was discussed at &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=11362058&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=11362058&lt;/a&gt;.</text><parent_chain></parent_chain></comment><story><title>Jenkins 2.0 is here</title><url>https://jenkins.io/blog/2016/04/26/jenkins-20-is-here/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>mikestew</author><text>I was looking at this over the weekend to see if the risk&amp;#x2F;benefit ratio was appropriate for our team. Meh, we already use the pipelines plug-in, and the insecure-by-default configuration has already been locked down, so for our team the answer is, &amp;quot;no, it&amp;#x27;s not worth risking mikestew having to spend a day putting things back the way they were if the upgrade goes horribly wrong&amp;quot;. I&amp;#x27;m supposed to be writing code, not dicking around with broken installs.&lt;p&gt;That&amp;#x27;s not to poo-poo the hard work that obviously went into this release. Big, shiny new stuff there, and the next Jenkins box I setup will be running 2.0. But for my particular situation at this point in time, it&amp;#x27;ll be 1.6 for a while.</text><parent_chain></parent_chain></comment><story><title>Jenkins 2.0 is here</title><url>https://jenkins.io/blog/2016/04/26/jenkins-20-is-here/</url></story>