After some votes the winner is March 18th, 10AM UTC. I have added a meeting to the Jenkins calendar.
Join Zoom Meeting : https://zoom.us/j/875768974 Find your local call-in number: https://zoom.us/u/afxZRrxiW The meeting will be recorded, and we will make sure to do meeting notes and to update the Google Doc. Best regards, Oleg On Friday, March 13, 2020 at 9:18:05 AM UTC+1, Oleg Nenashev wrote: > > I plan to close the Doodle poll tomorrow. > If you want to participate, please vote. > https://doodle.com/poll/xrhpmsk9xpba2tfh > > Best regards, > Oleg > > > On Monday, March 9, 2020 at 11:21:25 AM UTC+1, Oleg Nenashev wrote: >> >> Dear all, >> >> We had serious regressions in the 2.204.x LTS baseline starting from >> 2.204.3 which was released on Feb 28 (changelog >> <https://jenkins.io/changelog-stable/>). After that we had 2 >> out-of-order releases over a week, with 3 major regressions reported by >> Jenkins LTS users. These regressions were largely related to the embedded >> Jetty web container updates in the LTS baseline. In 2.204.5 we also had to >> reintroduce a defect in the LTS release, and it is also far from business >> as usual. >> >> I have started a public retrospective document >> <https://docs.google.com/document/d/1NzR1XtkCfk6MDSD1jRq5H-iPSjqKvP-pfUO0b9lVZ9k/edit?usp=sharing> >> >> to restore the sequence of events and to discuss what we could do better in >> the next releases. Anyone is welcome to comment in the doc and to make >> suggestions there. If you are a Jenkins user affected by the issues, your >> feedback will be much appreciated as well. Thanks in advance for your time! >> >> I also suggest organizing a recorded video call next week to discuss the >> retrospective feedback. If you are interested to participate, please vote >> for the meeting times here: https://doodle.com/poll/xrhpmsk9xpba2tfh >> >> Just to emphasize, the purpose of the retrospective is to improve our >> processes and to ensure better quality of LTS and weekly releases. The >> regressions were caused by numerous causes and they passed though all our >> quality gates, there is no sense to put blame on any Jenkins team. There >> are many contributors involved in the core maintenance, and we do our best >> to provide stable releases, including weekends and burning the midnight >> oil. Please refrain from putting a blame and let's focus on making Jenkins >> releases more stable. >> >> P.S: We are always looking for more contributors >> <https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md> and >> reviewers/maintainers in the Jenkins core. If you are interested to >> help with maintaining the kernel of the project with millions of developers >> using it daily, please let us know! >> >> Best regards, >> Oleg Nenashev >> Jenkins Core Team >> > -- 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/2dc04243-df1c-4782-9e00-2dbe470faaad%40googlegroups.com.
