Finally 2.x LTS train is there. Its's so great to see new release of
jenkins nearly always on time. :-)
On Wednesday, 4 May 2016 21:47:13 UTC+5:30, Daniel Beck wrote:
>
>
> > On 04.05.2016, at 18:11, greg@qflow.com wrote:
> >
> > What is the suggested path for using Jenkins 2.x for a conse
> On 04.05.2016, at 18:11, greg.rom...@qflow.com wrote:
>
> What is the suggested path for using Jenkins 2.x for a conservative
> organization like ours? We would like to use version 2.1 but don't have the
> resources to be installing and potentially troubleshooting a new version
> every week
There will be a 2.x LTS in a couple of weeks... 1.651.3 needs to happen
first AIUI
On 4 May 2016 at 17:11, wrote:
> For Jenkins 1.x we have always gone with the Long-Term Support (LTS)
> release. We are not an organization who wants to be on "the latest and
> greatest". That being said, we are
For Jenkins 1.x we have always gone with the Long-Term Support (LTS)
release. We are not an organization who wants to be on "the latest and
greatest". That being said, we are very eager to start using Jenkins 2.x.
What is the suggested path for using Jenkins 2.x for a conservative
organizatio
