Next LTS baseline

[Tim Jacomb]

Hi all,

It's time to select the next LTS baseline.

The best candidate right now appears to be 2.344.

There's some more UX fixes in the upcoming weekly too which could be an option

See recent changelogs: https://www.jenkins.io/changelog/

Thanks

Tim

[Alexander Brandes]

Heyo,

2.345 sounds promising, considering it contains current regressions and quite a few from older releases too.

What happened to the suggestion to delay the next LTS baseline selection by two to four weeks to have more time to iron out regressions?

~Alex

[Mark Waite]

On Saturday, April 23, 2022 at 1:52:31 PM UTC-6 you wrote:

Heyo,

2.345 sounds promising, considering it contains current regressions and quite a few from older releases too.

What happened to the suggestion to delay the next LTS baseline selection by two to four weeks to have more time to iron out regressions?

Tim had not agreed to the proposed delay in the Jenkins release schedule.  As the release officer, he has the final decision.

Here's my attempt to persuade Tim that we should take another week before selecting the LTS baseline and should then deliver the LTS release two weeks later than currently scheduled.

I am worried by the open regressions in 2.344 that don't have fixes merged or proposed for 2.345.  I don't think that we need to reduce those open UX regressions to zero, but there are several that I think we should resolve and verify in a weekly release before the baseline is selected.  I would prefer to give ourselves one more week to collect more fixes and more verification time of the existing fixes.  That would lead us to choose either 2.345 (today's release) or 2.346 as the LTS baseline.

Specific issues that worry me include:

• JENKINS-68303 - Schedule build icon no longer indicates the "scheduled to be built" state since 2.321 (multiple requests for this one)
• JENKINS-68296 - Broken sidebar icons from the Gitlab Branch Source plugin
  
• JENKINS-68042 - Help icon placement incorrect since 2.320 (fix is in review)

I'd really like fixes verified in a weekly for those before we select the LTS baseline.

I'm open to concerns and objections from others, but I think we should consider those issues before selecting the baseline.

 

~Alex

On Saturday, 23 April 2022 at 18:20:18 UTC+2 Tim Jacomb wrote:

Hi all,

It's time to select the next LTS baseline.

The best candidate right now appears to be 2.344.

I agree that 2.344 is the best candidate right now, but I would like an even better candidate with the fixes from today's weekly and key fixes from the list of open UX regressions.

Mark Waite

 

[Tim Jacomb]

Any thoughts on 2.346?

There were a small number of changes and it included a fix for credentials dialogs.

We can always backport additional fixes as required.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e372016c-f2bb-429b-8dca-2a38a8967471n%40googlegroups.com.

[Mark Waite]

On Friday, May 6, 2022 at 3:15:52 PM UTC-6 Tim Jacomb wrote:

Any thoughts on 2.346?

There were a small number of changes and it included a fix for credentials dialogs.

We can always backport additional fixes as required.

The issues that worried me were:

• JENKINS-68303 - Schedule build icon no longer indicates the "scheduled to be built" state since 2.321 - merged for 2.347 next Tuesday
• JENKINS-68296 - Broken sidebar icons from the Gitlab Branch Source plugin - under investigation
  
• JENKINS-68042 - Help icon placement incorrect since 2.320 (fix is in review) - merged for 2.347 next Tuesday

The issue that arrived recently that worries me include:

• JENKINS-68390 - Build number cut off on Safari

I'd prefer to wait for 2.347 rather than take 2.346, but I agree that the ratings for 2.344, 2.345, and 2.346 all look very good and the fixes that were included in those releases have not seemed to introduce any new regressions.

Mark Waite

[Daniel Beck]

On Sat, May 7, 2022 at 12:22 AM Mark Waite <mark.ea...@gmail.com> wrote:

The issues that worried me were:

• JENKINS-68303 - Schedule build icon no longer indicates the "scheduled to be built" state since 2.321 - merged for 2.347 next Tuesday

… 

• JENKINS-68042 - Help icon placement incorrect since 2.320 (fix is in review) - merged for 2.347 next Tuesday

These are already in an LTS line. While it would be nice to not have them in another, the LTS feedback doesn't indicate these were big issues, and we can always backport fixes into .1 or .2. It really doesn't look like we need to hold off further for these specifically.

[Mark Waite]

On Monday, May 9, 2022 at 4:15:21 AM UTC-6 Daniel Beck wrote:

On Sat, May 7, 2022 at 12:22 AM Mark Waite  wrote:

The issues that worried me were:

• JENKINS-68303 - Schedule build icon no longer indicates the "scheduled to be built" state since 2.321 - merged for 2.347 next Tuesday

… 

• JENKINS-68042 - Help icon placement incorrect since 2.320 (fix is in review) - merged for 2.347 next Tuesday

These are already in an LTS line. While it would be nice to not have them in another, the LTS feedback doesn't indicate these were big issues, and we can always backport fixes into .1 or .2. It really doesn't look like we need to hold off further for these specifically.

Good point that they were already in a previous LTS.  Good ratings for the most recent several weekly releases makes me think that 2.346 is a good choice as the LTS baseline.

Mark Waite

[Tim Jacomb]

Thanks all.

Let's go with 2.346

Cheers

Tim

--

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 jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5e24aef2-ff76-4b05-b49c-d02fe9ef4999n%40googlegroups.com.