Issues to be backported to LTS 1.409.2

[Vojtech Juranek]

Hi,
I identified following (blocker and critical) issue, which should be backported
to next LTS (i.e. 1.409.2):

* JENKINS-6700: (https://issues.jenkins-ci.org/browse/JENKINS-6700)
* JENKINS-8882 (https://issues.jenkins-ci.org/browse/JENKINS-8882)
* JENKINS-10346 (https://issues.jenkins-ci.org/browse/JENKINS-10346)
* JENKINS-10424 (https://issues.jenkins-ci.org/browse/JENKINS-10424)
* JENKINS-10511 (https://issues.jenkins-ci.org/browse/JENKINS-10511)
* JENKINS-10556 (https://issues.jenkins-ci.org/browse/JENKINS-10556)

Are you aware of any other blocker or critical bug, which was fixed since last
LTS and should be backported as well?
Thanks
Vojtech

[Christoph Kutzinski]

What about

https://issues.jenkins-ci.org/browse/JENKINS-8703
https://issues.jenkins-ci.org/browse/JENKINS-9189
?

[Vojtech Juranek]

ops, I somehow missed JENKINS-9189. JENKINS-8703 wasn't included as it's
clasified as major (not a blocker or critical), but no problem to include it.
Thanks!

Anything else what I missed?

[Christoph Kutzinski]

One additional question:

do you plan to update the versions of the bundled plugins, namely subversion?
There was e.g. a fix for JENKINS-10030 in https://github.com/jenkinsci/subversion-plugin/commit/9418134495a80964bb46d0ca7102e34641fa9a41

Which reminds me, that I wanted to check if JENKINS-10030 was already broken pre-1.409 so that we should maybe por it, too.

Christoph

-------- Original-Nachricht --------
> Datum: Tue, 16 Aug 2011 18:59:45 +0200
> Von: Christoph Kutzinski <ku...@gmx.de>
> An: jenkin...@googlegroups.com
> Betreff: Re: Issues to be backported to LTS 1.409.2

[Dean Yu]

Wow, that's an interesting question. In my opinion, taking new versions of
bundled plugins would potentially destabilize the LTS release. Ideally, we'd
create LTS branches of the bundled plugins for the versions that were
released with the core version the LTS release originally included, and
cherry pick bug fixes. That seems like a lot of work to manage though, so
I'm not set on this approach.

-- Dean

[Vojtech Juranek]

>Ideally,
> we'd create LTS branches of the bundled plugins for the versions that were
> released with the core version the LTS release originally included, and
> cherry pick bug fixes. That seems like a lot of work to manage though, so
> I'm not set on this approach.

I would prefere this approach. Switching to higher version of the plugin,
which contains given bug fix can lead (besides new features and new bugs:-) to
situation that higher plugin version requires higher version of Jenkins core
than LTS which would force us to create plugin LTS version anyway.

There are only 4 bundled plugins and I would create LTS version only in case
we want to backport some bug fixes into the plugin, which doesn't seem to me so
much work on top of that.

I'm not experienced with various background processes. Can I spoil something
if I release subversion-1.25.1 (e.g. some confusion in update center)?
And actually do we need it? I'm not completely sure if JENKINS-10030 is
present in 1.409.1

Vojtech