Some bits: - We have some regression reports probably related to XML 1.1 ( JENKINS-49588 <https://issues.jenkins-ci.org/browse/JENKINS-49588>, fix has not been integrated yet + some other issues) - We have an issue with Violations plugin breaking config UIs on new versions (JENKINS-49630 <https://issues.jenkins-ci.org/browse/JENKINS-49630>). I have not fully triaged it yet, but it may be caused by a core regression somehow - We have minor regressions in UI, (JENKINS-49634 <https://issues.jenkins-ci.org/browse/JENKINS-49634>, JENKINS-49387 <https://issues.jenkins-ci.org/browse/JENKINS-49387>, JENKINS-49520, <https://issues.jenkins-ci.org/browse/JENKINS-49520>), can be easily backported - Same for this localization (JENKINS-49498 <https://issues.jenkins-ci.org/browse/JENKINS-49498>) - not new regressions, but may need backporting - We are still getting new regression reports for JEP-200 <https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200> (added in 2.102), but I'd guess we want it in LTS anyway
Currently I am not fully comfortable about 2.107. - JEP-200 upgrade guidelines will explicitly require users to do a backup before upgrading. There is a risk that the instance does not startup due to a non-fixed plugin - But you know, not everybody reads upgrade guidelines and changelogs - If we release JEP-200 and XML 1.1 at the same time, there a risk of causing serious configuration fallout for users who did not do backup. JEP-200 can cause a fallout on its own, but with XML 1.1 it may get even worse Since XML 1.1 fix <https://github.com/jenkinsci/jenkins/pull/3305>has not been approved yet, my proposal would be to exclude XML 1.1 from the release. So I vote for 2.104. BR, Oleg On Friday, February 23, 2018 at 5:27:28 AM UTC+1, Mark Waite wrote: > > I've been running 2.107 since last week and have found no surprises in my > tests. > > I'm running a Docker instance with permanent agents connected from CentOS > 6, CentOS 7, Debian 8, Debian 9, Ubuntu 14, Ubuntu 16, Windows 7, and > Windows 10. > > My configuration is mostly focused on detecting problems in the git plugin > and the git client plugin. The setup includes multi-branch pipeline jobs > that monitor the git plugin and git client plugin, other multi-branch jobs > that monitor my jenkins-bugs repository and a private version of the same > repository, and many jobs which check for specific bugs. > > Mark Waite > > On Thu, Feb 22, 2018 at 1:31 PM Daniel Beck <[email protected] > <javascript:>> wrote: > >> >> > On 15. Feb 2018, at 09:26, Oliver Gondža <[email protected] >> <javascript:>> wrote: >> > >> > As greed on Governance meeting, the next LTS line will be based on >> latest weekly release. That means, there are no backports to be added for >> .1 provided we do not discover something urgent that would cause us to >> expedite some or reconsider our choice of baseline - which we do not >> anticipate. >> > >> > Therefore, I would like to encourage all the folks that kindly help us >> test the RCs to use 2.107 weekly(!). Note formally we are still in a >> backportig period and testing is planned to start in two weeks, though with >> the bits already out, there is no reason not to start right away. >> >> It's been a week. Any news from testing, or anything we've since learned >> about the current weeklies? I've seen some grumbling about the XML 1.1 >> change that went into 2.105, but mostly people downgrading and resolved by >> `sed -i`. Anything else we should know while we can still reconsider the >> baseline choice (or nominate backports)? >> >> Daniel >> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/9479AADB-C26C-4C1D-B287-EA2A7DB1C583%40beckweb.net >> . >> 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/f472bf23-b7e7-4077-94eb-66cf81bf9f22%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
