Re: Next LTS baseline selection

[Tim Jacomb]

Hi all

2.375 is selected as the next baseline.

Thanks
Tim

On Mon, 31 Oct 2022 at 21:18, Tim Jacomb  wrote:

> https://issues.jenkins.io/browse/JENKINS-69966 is very much a real issue,
> but it has a fix on the plugin so I wouldn't worry too much about it.
>
> 2.375 looks to be a good baseline to me.
>
> On Fri, 28 Oct 2022 at 14:21, Alexander Brandes 
> wrote:
>
>> As an alternative to 2.375, I'd like to bring up 2.372 as a possible
>> candidate. 2.375 ships a (possible) issue tracked in JENKINS-69966
>> .
>> 2.372  is a much less recent
>> weekly release, with a better rating than 2.375 and less big changes, which
>> could result in possible regressions. It was released almost a month ago
>> with no community reported issues, according to the changelog.
>>
>> On Tuesday, 25 October 2022 at 17:48:11 UTC+2 m...@basilcrow.com wrote:
>>
>>> On Tue, Oct 25, 2022 at 7:42 AM 'wfoll...@cloudbees.com' via Jenkins
>>> Developers  wrote:
>>> >
>>> > To ease this kind of discussion, it could be interesting to introduce
>>> only very minor features or bug fixes before the LTS selection, so that we
>>> have more time to test them. But it's a different topic :p
>>>
>>> FTR there is something written about this at
>>>
>>> https://github.com/jenkinsci/jenkins/blob/e7df5eb5285ec965621a02d589f2543d09885723/docs/MAINTAINERS.adoc#step-2-is-it-a-good-time-to-merge
>>> although it refers more to security releases than creating a new
>>> stable branch. But yes I personally would not have merged the
>>> abovementioned three frontend changes so close to the branching date.
>>> If any issues are discovered in the next week, we can revert the
>>> relevant commits from the stable branch, or create the stable branch
>>> from an earlier point and backport the bug fixes to it like you
>>> mentioned.
>>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/3bda553b-1102-490d-8d54-fe0d9bf3be2an%40googlegroups.com
>> 
>> .
>>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicRBTV10yOP%3DX%2BwzQoGtCcLixmhqd16d7CQK8O2Fw4GFA%40mail.gmail.com.

Re: Next LTS baseline selection

[Tim Jacomb]

https://issues.jenkins.io/browse/JENKINS-69966 is very much a real issue,
but it has a fix on the plugin so I wouldn't worry too much about it.

2.375 looks to be a good baseline to me.

On Fri, 28 Oct 2022 at 14:21, Alexander Brandes 
wrote:

> As an alternative to 2.375, I'd like to bring up 2.372 as a possible
> candidate. 2.375 ships a (possible) issue tracked in JENKINS-69966
> .
> 2.372  is a much less recent
> weekly release, with a better rating than 2.375 and less big changes, which
> could result in possible regressions. It was released almost a month ago
> with no community reported issues, according to the changelog.
>
> On Tuesday, 25 October 2022 at 17:48:11 UTC+2 m...@basilcrow.com wrote:
>
>> On Tue, Oct 25, 2022 at 7:42 AM 'wfoll...@cloudbees.com' via Jenkins
>> Developers  wrote:
>> >
>> > To ease this kind of discussion, it could be interesting to introduce
>> only very minor features or bug fixes before the LTS selection, so that we
>> have more time to test them. But it's a different topic :p
>>
>> FTR there is something written about this at
>>
>> https://github.com/jenkinsci/jenkins/blob/e7df5eb5285ec965621a02d589f2543d09885723/docs/MAINTAINERS.adoc#step-2-is-it-a-good-time-to-merge
>> although it refers more to security releases than creating a new
>> stable branch. But yes I personally would not have merged the
>> abovementioned three frontend changes so close to the branching date.
>> If any issues are discovered in the next week, we can revert the
>> relevant commits from the stable branch, or create the stable branch
>> from an earlier point and backport the bug fixes to it like you
>> mentioned.
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3bda553b-1102-490d-8d54-fe0d9bf3be2an%40googlegroups.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidzMEMRBypemBsLwUqZmbEhy%2BAjDcB2SKj3ebQRiXTXrw%40mail.gmail.com.

Re: Next LTS baseline selection

[Alexander Brandes]

As an alternative to 2.375, I'd like to bring up 2.372 as a possible 
candidate. 2.375 ships a (possible) issue tracked in JENKINS-69966 
.
2.372  is a much less recent 
weekly release, with a better rating than 2.375 and less big changes, which 
could result in possible regressions. It was released almost a month ago 
with no community reported issues, according to the changelog.

On Tuesday, 25 October 2022 at 17:48:11 UTC+2 m...@basilcrow.com wrote:

> On Tue, Oct 25, 2022 at 7:42 AM 'wfoll...@cloudbees.com' via Jenkins
> Developers  wrote:
> >
> > To ease this kind of discussion, it could be interesting to introduce 
> only very minor features or bug fixes before the LTS selection, so that we 
> have more time to test them. But it's a different topic :p
>
> FTR there is something written about this at
>
> https://github.com/jenkinsci/jenkins/blob/e7df5eb5285ec965621a02d589f2543d09885723/docs/MAINTAINERS.adoc#step-2-is-it-a-good-time-to-merge
> although it refers more to security releases than creating a new
> stable branch. But yes I personally would not have merged the
> abovementioned three frontend changes so close to the branching date.
> If any issues are discovered in the next week, we can revert the
> relevant commits from the stable branch, or create the stable branch
> from an earlier point and backport the bug fixes to it like you
> mentioned.
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3bda553b-1102-490d-8d54-fe0d9bf3be2an%40googlegroups.com.

Re: Next LTS baseline selection

[Basil Crow]

On Tue, Oct 25, 2022 at 7:42 AM 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:
>
> To ease this kind of discussion, it could be interesting to introduce only 
> very minor features or bug fixes before the LTS selection, so that we have 
> more time to test them. But it's a different topic :p

FTR there is something written about this at
https://github.com/jenkinsci/jenkins/blob/e7df5eb5285ec965621a02d589f2543d09885723/docs/MAINTAINERS.adoc#step-2-is-it-a-good-time-to-merge
although it refers more to security releases than creating a new
stable branch. But yes I personally would not have merged the
abovementioned three frontend changes so close to the branching date.
If any issues are discovered in the next week, we can revert the
relevant commits from the stable branch, or create the stable branch
from an earlier point and backport the bug fixes to it like you
mentioned.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrTjtiv%2B7%3DDX4VSq5d3wvqcazTFjiWqmqKqp2z4NafB3A%40mail.gmail.com.

Re: Next LTS baseline selection

['wfoll...@cloudbees.com' via Jenkins Developers]

FTR 2.375 was released ~4h ago, the changelog page is not even updated (to 
receive the feedback).
With the list of regression/bug fix it seems to be a good candidate, but I 
think we should monitor carefully the user feedbacks and be ready to 
provide backports to a previous version.

To ease this kind of discussion, it could be interesting to introduce only 
very minor features or bug fixes before the LTS selection, so that we have 
more time to test them. But it's a different topic :p

On Monday, October 24, 2022 at 11:36:01 PM UTC+2 mc.ca...@gmail.com wrote:

> +1 for 2.375
>
> On Monday, 24 October 2022 at 23:12:43 UTC+2 m...@basilcrow.com wrote:
>
>> I feel strongly that the following fixes be included in the next LTS 
>> release:
>>
>> jenkinsci/jenkins#7208 - Fix for weather icon issue that many users
>> have complained about (included in the forthcoming 2.375)
>> jenkinsci/jenkins#7270 - Important fix for Java 17 users (included in
>> the forthcoming 2.375)
>> jenkinsci/jenkins#7273 - Fix for regression in queue maintenance
>> introduced in 2.361 (included in the forthcoming 2.375)
>> jenkinsci/jenkins#7275 - Update bundled plugins with security fixes
>> (included in the forthcoming 2.375)
>> jenkinsci/jenkins#7277 and jenkinsci/winstone#296 - Fix for WebSocket
>> regression introduced in the last LTS that many users have complained
>> about (included in the forthcoming 2.375)
>> jenkinsci/jenkins#7286 - Fix for regression in safe restart page
>> introduced in 2.374 (included in the forthcoming 2.375)
>>
>> Based on the above 2.375 could make a good candidate. Note that 2.375
>> also contains a number of significant frontend changes that have not
>> yet received widespread adoption:
>>
>> jenkinsci/jenkins#6912 - Improve breadcrumb bar accessibility
>> jenkinsci/jenkins#7049 - Update the design of notifications
>> jenkinsci/jenkins#7197 - Update design of Manage Users page
>>
>> Assuming that no issues with the abovementioned regression fixes and
>> frontend changes are discovered next week, my vote would be for 2.375.
>>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8af5bfe7-1176-42c8-b275-ec5ccce449adn%40googlegroups.com.

Re: Next LTS baseline selection

[Alexander Brandes]

+1 for 2.375

On Monday, 24 October 2022 at 23:12:43 UTC+2 m...@basilcrow.com wrote:

> I feel strongly that the following fixes be included in the next LTS 
> release:
>
> jenkinsci/jenkins#7208 - Fix for weather icon issue that many users
> have complained about (included in the forthcoming 2.375)
> jenkinsci/jenkins#7270 - Important fix for Java 17 users (included in
> the forthcoming 2.375)
> jenkinsci/jenkins#7273 - Fix for regression in queue maintenance
> introduced in 2.361 (included in the forthcoming 2.375)
> jenkinsci/jenkins#7275 - Update bundled plugins with security fixes
> (included in the forthcoming 2.375)
> jenkinsci/jenkins#7277 and jenkinsci/winstone#296 - Fix for WebSocket
> regression introduced in the last LTS that many users have complained
> about (included in the forthcoming 2.375)
> jenkinsci/jenkins#7286 - Fix for regression in safe restart page
> introduced in 2.374 (included in the forthcoming 2.375)
>
> Based on the above 2.375 could make a good candidate. Note that 2.375
> also contains a number of significant frontend changes that have not
> yet received widespread adoption:
>
> jenkinsci/jenkins#6912 - Improve breadcrumb bar accessibility
> jenkinsci/jenkins#7049 - Update the design of notifications
> jenkinsci/jenkins#7197 - Update design of Manage Users page
>
> Assuming that no issues with the abovementioned regression fixes and
> frontend changes are discovered next week, my vote would be for 2.375.
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d0f19cec-a978-4751-b221-866f15f7825fn%40googlegroups.com.

Re: Next LTS baseline selection

[Basil Crow]

I feel strongly that the following fixes be included in the next LTS release:

jenkinsci/jenkins#7208 - Fix for weather icon issue that many users
have complained about (included in the forthcoming 2.375)
jenkinsci/jenkins#7270 - Important fix for Java 17 users (included in
the forthcoming 2.375)
jenkinsci/jenkins#7273 - Fix for regression in queue maintenance
introduced in 2.361 (included in the forthcoming 2.375)
jenkinsci/jenkins#7275 - Update bundled plugins with security fixes
(included in the forthcoming 2.375)
jenkinsci/jenkins#7277 and jenkinsci/winstone#296 - Fix for WebSocket
regression introduced in the last LTS that many users have complained
about (included in the forthcoming 2.375)
jenkinsci/jenkins#7286 - Fix for regression in safe restart page
introduced in 2.374 (included in the forthcoming 2.375)

Based on the above 2.375 could make a good candidate. Note that 2.375
also contains a number of significant frontend changes that have not
yet received widespread adoption:

jenkinsci/jenkins#6912 - Improve breadcrumb bar accessibility
jenkinsci/jenkins#7049 - Update the design of notifications
jenkinsci/jenkins#7197 - Update design of Manage Users page

Assuming that no issues with the abovementioned regression fixes and
frontend changes are discovered next week, my vote would be for 2.375.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjr2ud_ZiN5fKdq44VP55vzWKHYhrVsp3eS9NnsD07L-ow%40mail.gmail.com.

Next LTS baseline selection

['Cathy Chan' via Jenkins Developers]

Hi all,

Looking at the Jenkins events calendar , we 
should have been well underway with the selection of the next LTS baseline.

Any proposals?

- Cathy.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a063f559-d2c0-4032-8eda-d7a8c2ca8315n%40googlegroups.com.

Re: New LTS baseline selection

[Tim Jacomb]

2.332 has been selected

On Tue, 25 Jan 2022 at 14:26, Mark Waite  wrote:

>
> On Tue, Jan 25, 2022 at 7:00 AM Tim Jacomb wrote:
>
>> Hi all,
>>
>> It's time to select the next LTS baseline.
>> The best candidate right now appears to be 2.332
>>
>> See recent changelogs: https://www.jenkins.io/changelog/
>>
>>
> I like the choice of 2.332 as the next baseline.  I'd really like a fix
> for Pipeline job status icon center is misplaced (JENKINS-67654
> ) but that can be done as
> a backport if it arrives in a weekly release reasonably soon.  It is not a
> blocker, but I think it will generate many bug reports from users.
>
> Mark Waite
>
>
>> Thanks
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiffxJ12qTNJAepD9FDZEqsWxTeaDz21NYN0ksVYrSax%3DQ%40mail.gmail.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGfjRbhAuZyQfTaz2bWiRx5ZyBq%2BWKwFsFL9nDDQpmBXw%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie2eMxWmOgjw%2BYC%3Dat3Z7cXw9iiVY8dZrvcZD%2BwZQf75A%40mail.gmail.com.

Re: New LTS baseline selection

[Mark Waite]

On Tue, Jan 25, 2022 at 7:00 AM Tim Jacomb wrote:

> Hi all,
>
> It's time to select the next LTS baseline.
> The best candidate right now appears to be 2.332
>
> See recent changelogs: https://www.jenkins.io/changelog/
>
>
I like the choice of 2.332 as the next baseline.  I'd really like a fix for
Pipeline job status icon center is misplaced (JENKINS-67654
) but that can be done as a
backport if it arrives in a weekly release reasonably soon.  It is not a
blocker, but I think it will generate many bug reports from users.

Mark Waite


> Thanks
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiffxJ12qTNJAepD9FDZEqsWxTeaDz21NYN0ksVYrSax%3DQ%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGfjRbhAuZyQfTaz2bWiRx5ZyBq%2BWKwFsFL9nDDQpmBXw%40mail.gmail.com.

New LTS baseline selection

[Tim Jacomb]

Hi all,

It's time to select the next LTS baseline.
The best candidate right now appears to be 2.332

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

Thanks
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiffxJ12qTNJAepD9FDZEqsWxTeaDz21NYN0ksVYrSax%3DQ%40mail.gmail.com.

Re: New LTS baseline selection

[Tim Jacomb]

Sure sounds fine

On Thu, 28 Oct 2021 at 08:55, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> If you like 2.318 for this, you should wait for 2.319, which will only
> contain security fixes.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BW%2BdDpTnW8Je06SqWMEzAjtjBpRZjjh_cwc6a1bp0d_g%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidF6GQs9Q-uCp3eDPDKZvKALgg74totM_C8_JGsy0XG2A%40mail.gmail.com.

Re: New LTS baseline selection

['Daniel Beck' via Jenkins Developers]

If you like 2.318 for this, you should wait for 2.319, which will only
contain security fixes.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BW%2BdDpTnW8Je06SqWMEzAjtjBpRZjjh_cwc6a1bp0d_g%40mail.gmail.com.

Re: New LTS baseline selection

[Tim Jacomb]

2.318 is looking good to me, I really like the new tooltips and the
`ExecutorListener` change could be a good one to get in as well

Thanks
Tim

On Thu, 21 Oct 2021 at 10:40, Oleg Nenashev  wrote:

> 2.317 looks good to me. No objections w.r.t 2.318 too, but we do not know
> a full scope yet.
> Personally I would be happy to get Winstone BOM into it (
> https://github.com/jenkinsci/winstone/pull/172), but I do not think it is
> a justification on its own.
> This patch is just a quality of life improvement for Jenkinsfile Runner
>
> Best regards,
> Oleg
>
> On Wednesday, October 20, 2021 at 9:24:46 PM UTC+2 Mark Waite wrote:
>
>> The changelist in 2.317 makes it very attractive to me, including:
>>
>>- JENKINS-66753 - Ongoing build disappears from build history
>>- JENKINS-61212 - Agent handshake fix for websockets on Java 11
>>
>> Anything older than 2.317 and later than 2.313 would require a backport
>> of JENKINS-66753.
>>
>> Mark Waite
>>
>> On Wed, Oct 20, 2021 at 12:31 PM Tim Jacomb  wrote:
>>
>>> Hi all,
>>>
>>> It's time to select the next LTS baseline.
>>> The best candidate right now appears to be 2.317 or the upcoming 2.318
>>>
>>> 2.317 fixed JENKINS-66753
>>>  which was reported as
>>> a major issue across a few versions.
>>>
>>> Thanks
>>> 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/CAH-3Bifbmg5g8FXeW_ArLDHqj0BRZkLJuwcUOVBeE9%3DgHCnsYA%40mail.gmail.com
>>> 
>>> .
>>>
>> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/f44dba88-0682-401e-b9f8-7275de079ba2n%40googlegroups.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidPCxZ0JfWRK5EhSq1cTqwwTEx-6nPOviordNY%3DGhu16g%40mail.gmail.com.

Re: New LTS baseline selection

[Oleg Nenashev]

2.317 looks good to me. No objections w.r.t 2.318 too, but we do not know a 
full scope yet.
Personally I would be happy to get Winstone BOM into it 
(https://github.com/jenkinsci/winstone/pull/172), but I do not think it is 
a justification on its own.
This patch is just a quality of life improvement for Jenkinsfile Runner

Best regards,
Oleg

On Wednesday, October 20, 2021 at 9:24:46 PM UTC+2 Mark Waite wrote:

> The changelist in 2.317 makes it very attractive to me, including:
>
>- JENKINS-66753 - Ongoing build disappears from build history
>- JENKINS-61212 - Agent handshake fix for websockets on Java 11
>
> Anything older than 2.317 and later than 2.313 would require a backport of 
> JENKINS-66753.
>
> Mark Waite
>
> On Wed, Oct 20, 2021 at 12:31 PM Tim Jacomb  wrote:
>
>> Hi all,
>>
>> It's time to select the next LTS baseline.
>> The best candidate right now appears to be 2.317 or the upcoming 2.318
>>
>> 2.317 fixed JENKINS-66753 
>>  which was reported as a 
>> major issue across a few versions.
>>
>> Thanks
>> 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/CAH-3Bifbmg5g8FXeW_ArLDHqj0BRZkLJuwcUOVBeE9%3DgHCnsYA%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f44dba88-0682-401e-b9f8-7275de079ba2n%40googlegroups.com.

Re: New LTS baseline selection

[Mark Waite]

The changelist in 2.317 makes it very attractive to me, including:

   - JENKINS-66753 - Ongoing build disappears from build history
   - JENKINS-61212 - Agent handshake fix for websockets on Java 11

Anything older than 2.317 and later than 2.313 would require a backport of
JENKINS-66753.

Mark Waite

On Wed, Oct 20, 2021 at 12:31 PM Tim Jacomb  wrote:

> Hi all,
>
> It's time to select the next LTS baseline.
> The best candidate right now appears to be 2.317 or the upcoming 2.318
>
> 2.317 fixed JENKINS-66753  
> which
> was reported as a major issue across a few versions.
>
> Thanks
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bifbmg5g8FXeW_ArLDHqj0BRZkLJuwcUOVBeE9%3DgHCnsYA%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFD%2BNwor1McJ9%3DPcPzM9djfz3VVRFkqCPsRsE6xTwmawg%40mail.gmail.com.

New LTS baseline selection

[Tim Jacomb]

Hi all,

It's time to select the next LTS baseline.
The best candidate right now appears to be 2.317 or the upcoming 2.318

2.317 fixed JENKINS-66753
 which
was reported as a major issue across a few versions.

Thanks
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bifbmg5g8FXeW_ArLDHqj0BRZkLJuwcUOVBeE9%3DgHCnsYA%40mail.gmail.com.

Re: Jenkins LTS baseline selection

[Tim Jacomb]

2.289 is selected

On Tue, 27 Apr 2021 at 16:25, Beatriz Munoz  wrote:

> Hi!
>
> So, is selected 2.289 or the discussion is still open?
>
> Thanks!
>
> El 24 abr 2021, a las 17:55, Tim Jacomb  escribió:
>
> Agreed
>
> On Sat, 24 Apr 2021 at 14:25, Oleg Nenashev 
> wrote:
>
>> AFAICT there have been no new regressions reported for 2.289 since the
>> release.
>> I think we can go ahead with choosing this baseline.
>>
>> BR, Oleg
>>
>> On Thursday, April 22, 2021 at 7:12:42 PM UTC+2 bmu...@cloudbees.com
>> wrote:
>>
>>> 2.289 looks good for me
>>>
>>> El 20 abr 2021, a las 12:43, Oleg Nenashev 
>>> escribió:
>>>
>>> 2.289 looks good for me. There are no major changes (e.g. we did not
>>> merge the Jetty 9.4.40 update), and it should be safe to take this versions
>>> as a baseline. If something happens, we still have 6 weeks
>>>
>>> On Tuesday, April 20, 2021 at 11:17:39 AM UTC+2 imon...@cloudbees.com
>>> wrote:
>>>
 2.289 LGTM

 Best,
 Ildefonso

 On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell 
 wrote:

> Hey Tim,
>
> I'm entirely for 2.289 as 2.289 does not make any major changes and as
> Daniel has pointed out, we can backport any fixes.
>
> Cheers,
> Raihaan
>
> On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus 
> wrote:
>
>> Thanks for raising this Tim.
>> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
>>
>> Can you please confirm the expected timeline, so we can better assess
>> things?
>> Re-reading https://www.jenkins.io/download/lts/ we're looking at a
>> .1 6 weeks from now, i.e. some time around 2021-06-02 right ?
>>
>> If so, I agree even choosing the upcoming 2.289 could be acceptable
>> with such a testing period.
>>
>> -- Baptiste
>>
>>
>>
>>
>> Given the expected usua
>>
>>
>>
>> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  a
>> écrit :
>>
>>> Hello everyone,
>>>
>>> Please voice your opinion on which version should be our next core
>>> baseline.
>>>
>>> For me it looks like either 2.288 or 2.289 are the options
>>>
>>> 2.289 (being released today) includes a change for an upcoming
>>> firefox version so it would be good to get it in, but it hasn't had any
>>> weekly soaking time so we could use 2.288 and then backport it in if we
>>> don't find any issues?
>>>
>>> What do you think?
>>>
>>> Thanks
>>> 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/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
>>> 
>>> .
>>>
>>
>> --
>> 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/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com
>> 
>> .
>>
>
> --
> 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/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
> 
> .
>


 --
 Ildefonso Montero Pérez
 Senior Software Engineer
 CloudBees, Inc



 E: imon...@cloudbees.com

>>>
>>> --
>>> 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/e95f04de-43f8-4b66-a68e-23379638d6f3n%40googlegroups.com
>>> 

Re: Jenkins LTS baseline selection

[Beatriz Munoz]

Hi!

So, is selected 2.289 or the discussion is still open?

Thanks!

> El 24 abr 2021, a las 17:55, Tim Jacomb  escribió:
> 
> Agreed
> 
> On Sat, 24 Apr 2021 at 14:25, Oleg Nenashev  > wrote:
> AFAICT there have been no new regressions reported for 2.289 since the 
> release.
> I think we can go ahead with choosing this baseline.
> 
> BR, Oleg
> 
> On Thursday, April 22, 2021 at 7:12:42 PM UTC+2 bmu...@cloudbees.com 
>  wrote:
> 2.289 looks good for me
> 
> 
>> El 20 abr 2021, a las 12:43, Oleg Nenashev > escribió:
>> 
> 
>> 2.289 looks good for me. There are no major changes (e.g. we did not merge 
>> the Jetty 9.4.40 update), and it should be safe to take this versions as a 
>> baseline. If something happens, we still have 6 weeks
>> 
>> On Tuesday, April 20, 2021 at 11:17:39 AM UTC+2 imon...@cloudbees.com 
>>  wrote:
>> 2.289 LGTM
>> 
>> Best,
>> Ildefonso
>> 
>> On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell > 
>> wrote:
>> Hey Tim,
>> 
>> I'm entirely for 2.289 as 2.289 does not make any major changes and as 
>> Daniel has pointed out, we can backport any fixes.
>> 
>> Cheers,
>> Raihaan
>> 
>> On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus > wrote:
>> Thanks for raising this Tim. 
>> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
>> 
>> Can you please confirm the expected timeline, so we can better assess things?
>> Re-reading https://www.jenkins.io/download/lts/ 
>>  we're looking at a .1 6 weeks from 
>> now, i.e. some time around 2021-06-02 right ?
>> 
>> If so, I agree even choosing the upcoming 2.289 could be acceptable with 
>> such a testing period. 
>> 
>> -- Baptiste
>> 
>> 
>> 
>> 
>> Given the expected usua
>> 
>> 
>> 
>> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb > a écrit :
>> Hello everyone,
>> 
>> Please voice your opinion on which version should be our next core baseline.
>> 
>> For me it looks like either 2.288 or 2.289 are the options
>> 
>> 2.289 (being released today) includes a change for an upcoming firefox 
>> version so it would be good to get it in, but it hasn't had any weekly 
>> soaking time so we could use 2.288 and then backport it in if we don't find 
>> any issues?
>> 
>> What do you think?
>> 
>> Thanks
>> 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/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
>>  
>> .
>> 
>> -- 
>> 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/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com
>>  
>> .
>> 
>> -- 
>> 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/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
>>  
>> .
>> 
>> 
>> -- 
>> Ildefonso Montero Pérez
>> Senior Software Engineer
>> CloudBees, Inc
>> 
>> 
>> 
>> E: imon...@cloudbees.com <>
>> 
>> -- 
>> 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/e95f04de-43f8-4b66-a68e-23379638d6f3n%40googlegroups.com
>>  
>> .
> 
> Beatriz Muñoz Manso
> Sr Software Engineer 
> CloudBees, Inc.
> 
> 
> 
> 
> -- 
> 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 

Re: Jenkins LTS baseline selection

[Tim Jacomb]

Agreed

On Sat, 24 Apr 2021 at 14:25, Oleg Nenashev  wrote:

> AFAICT there have been no new regressions reported for 2.289 since the
> release.
> I think we can go ahead with choosing this baseline.
>
> BR, Oleg
>
> On Thursday, April 22, 2021 at 7:12:42 PM UTC+2 bmu...@cloudbees.com
> wrote:
>
>> 2.289 looks good for me
>>
>> El 20 abr 2021, a las 12:43, Oleg Nenashev 
>> escribió:
>>
>> 2.289 looks good for me. There are no major changes (e.g. we did not
>> merge the Jetty 9.4.40 update), and it should be safe to take this versions
>> as a baseline. If something happens, we still have 6 weeks
>>
>> On Tuesday, April 20, 2021 at 11:17:39 AM UTC+2 imon...@cloudbees.com
>> wrote:
>>
>>> 2.289 LGTM
>>>
>>> Best,
>>> Ildefonso
>>>
>>> On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell 
>>> wrote:
>>>
 Hey Tim,

 I'm entirely for 2.289 as 2.289 does not make any major changes and as
 Daniel has pointed out, we can backport any fixes.

 Cheers,
 Raihaan

 On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus 
 wrote:

> Thanks for raising this Tim.
> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
>
> Can you please confirm the expected timeline, so we can better assess
> things?
> Re-reading https://www.jenkins.io/download/lts/ we're looking at a .1
> 6 weeks from now, i.e. some time around 2021-06-02 right ?
>
> If so, I agree even choosing the upcoming 2.289 could be acceptable
> with such a testing period.
>
> -- Baptiste
>
>
>
>
> Given the expected usua
>
>
>
> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  a
> écrit :
>
>> Hello everyone,
>>
>> Please voice your opinion on which version should be our next core
>> baseline.
>>
>> For me it looks like either 2.288 or 2.289 are the options
>>
>> 2.289 (being released today) includes a change for an upcoming
>> firefox version so it would be good to get it in, but it hasn't had any
>> weekly soaking time so we could use 2.288 and then backport it in if we
>> don't find any issues?
>>
>> What do you think?
>>
>> Thanks
>> 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/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
>> 
>> .
>>
>
> --
> 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/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com
> 
> .
>

 --
 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/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
 
 .

>>>
>>>
>>> --
>>> Ildefonso Montero Pérez
>>> Senior Software Engineer
>>> CloudBees, Inc
>>>
>>>
>>>
>>> E: imon...@cloudbees.com
>>>
>>
>> --
>> 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/e95f04de-43f8-4b66-a68e-23379638d6f3n%40googlegroups.com
>> 
>> .
>>
>>
>> Beatriz Muñoz Manso
>> Sr Software Engineer
>> CloudBees, Inc.
>>
>>
>> --
> 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 

Re: Jenkins LTS baseline selection

[Oleg Nenashev]

AFAICT there have been no new regressions reported for 2.289 since the 
release.
I think we can go ahead with choosing this baseline.

BR, Oleg

On Thursday, April 22, 2021 at 7:12:42 PM UTC+2 bmu...@cloudbees.com wrote:

> 2.289 looks good for me
>
> El 20 abr 2021, a las 12:43, Oleg Nenashev  escribió:
>
> 2.289 looks good for me. There are no major changes (e.g. we did not merge 
> the Jetty 9.4.40 update), and it should be safe to take this versions as a 
> baseline. If something happens, we still have 6 weeks
>
> On Tuesday, April 20, 2021 at 11:17:39 AM UTC+2 imon...@cloudbees.com 
> wrote:
>
>> 2.289 LGTM
>>
>> Best,
>> Ildefonso
>>
>> On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell  
>> wrote:
>>
>>> Hey Tim,
>>>
>>> I'm entirely for 2.289 as 2.289 does not make any major changes and as 
>>> Daniel has pointed out, we can backport any fixes.
>>>
>>> Cheers,
>>> Raihaan
>>>
>>> On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus  wrote:
>>>
 Thanks for raising this Tim. 
 As I've written on IRC, as long as we choose 2.288+, I'm happy :).

 Can you please confirm the expected timeline, so we can better assess 
 things?
 Re-reading https://www.jenkins.io/download/lts/ we're looking at a .1 
 6 weeks from now, i.e. some time around 2021-06-02 right ?

 If so, I agree even choosing the upcoming 2.289 could be acceptable 
 with such a testing period. 

 -- Baptiste




 Given the expected usua



 Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  a écrit :

> Hello everyone,
>
> Please voice your opinion on which version should be our next core 
> baseline.
>
> For me it looks like either 2.288 or 2.289 are the options
>
> 2.289 (being released today) includes a change for an upcoming firefox 
> version so it would be good to get it in, but it hasn't had any weekly 
> soaking time so we could use 2.288 and then backport it in if we don't 
> find 
> any issues?
>
> What do you think?
>
> Thanks
> 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/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
>  
> 
> .
>

 -- 
 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/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com
  
 
 .

>>>
>>> -- 
>>> 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/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Ildefonso Montero Pérez
>> Senior Software Engineer
>> CloudBees, Inc
>>
>>
>>
>> E: imon...@cloudbees.com
>>
>
> -- 
> 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/e95f04de-43f8-4b66-a68e-23379638d6f3n%40googlegroups.com
>  
> 
> .
>
>
> Beatriz Muñoz Manso
> Sr Software Engineer 
> CloudBees, Inc.
>
>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: Jenkins LTS baseline selection

[Beatriz Munoz]

2.289 looks good for me

> El 20 abr 2021, a las 12:43, Oleg Nenashev  escribió:
> 
> 2.289 looks good for me. There are no major changes (e.g. we did not merge 
> the Jetty 9.4.40 update), and it should be safe to take this versions as a 
> baseline. If something happens, we still have 6 weeks
> 
> On Tuesday, April 20, 2021 at 11:17:39 AM UTC+2 imon...@cloudbees.com wrote:
> 2.289 LGTM
> 
> Best,
> Ildefonso
> 
> On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell  > wrote:
> Hey Tim,
> 
> I'm entirely for 2.289 as 2.289 does not make any major changes and as Daniel 
> has pointed out, we can backport any fixes.
> 
> Cheers,
> Raihaan
> 
> On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus  > wrote:
> Thanks for raising this Tim. 
> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
> 
> Can you please confirm the expected timeline, so we can better assess things?
> Re-reading https://www.jenkins.io/download/lts/ 
>  we're looking at a .1 6 weeks from 
> now, i.e. some time around 2021-06-02 right ?
> 
> If so, I agree even choosing the upcoming 2.289 could be acceptable with such 
> a testing period. 
> 
> -- Baptiste
> 
> 
> 
> 
> Given the expected usua
> 
> 
> 
> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  > a écrit :
> Hello everyone,
> 
> Please voice your opinion on which version should be our next core baseline.
> 
> For me it looks like either 2.288 or 2.289 are the options
> 
> 2.289 (being released today) includes a change for an upcoming firefox 
> version so it would be good to get it in, but it hasn't had any weekly 
> soaking time so we could use 2.288 and then backport it in if we don't find 
> any issues?
> 
> What do you think?
> 
> Thanks
> 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/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
>  
> .
> 
> -- 
> 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/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com
>  
> .
> 
> -- 
> 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/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
>  
> .
> 
> 
> -- 
> Ildefonso Montero Pérez
> Senior Software Engineer
> CloudBees, Inc
> 
> 
> 
> E: imon...@cloudbees.com 
> 
> -- 
> 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-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/e95f04de-43f8-4b66-a68e-23379638d6f3n%40googlegroups.com
>  
> .

Beatriz Muñoz Manso
Sr Software Engineer 
CloudBees, Inc.



-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/C5C9BF5D-27B4-40FB-99CE-3316ED46D1A5%40cloudbees.com.

Re: Jenkins LTS baseline selection

[Oleg Nenashev]

2.289 looks good for me. There are no major changes (e.g. we did not merge 
the Jetty 9.4.40 update), and it should be safe to take this versions as a 
baseline. If something happens, we still have 6 weeks

On Tuesday, April 20, 2021 at 11:17:39 AM UTC+2 imon...@cloudbees.com wrote:

> 2.289 LGTM
>
> Best,
> Ildefonso
>
> On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell  
> wrote:
>
>> Hey Tim,
>>
>> I'm entirely for 2.289 as 2.289 does not make any major changes and as 
>> Daniel has pointed out, we can backport any fixes.
>>
>> Cheers,
>> Raihaan
>>
>> On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus  wrote:
>>
>>> Thanks for raising this Tim. 
>>> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
>>>
>>> Can you please confirm the expected timeline, so we can better assess 
>>> things?
>>> Re-reading https://www.jenkins.io/download/lts/ we're looking at a .1 6 
>>> weeks from now, i.e. some time around 2021-06-02 right ?
>>>
>>> If so, I agree even choosing the upcoming 2.289 could be acceptable with 
>>> such a testing period. 
>>>
>>> -- Baptiste
>>>
>>>
>>>
>>>
>>> Given the expected usua
>>>
>>>
>>>
>>> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  a écrit :
>>>
 Hello everyone,

 Please voice your opinion on which version should be our next core 
 baseline.

 For me it looks like either 2.288 or 2.289 are the options

 2.289 (being released today) includes a change for an upcoming firefox 
 version so it would be good to get it in, but it hasn't had any weekly 
 soaking time so we could use 2.288 and then backport it in if we don't 
 find 
 any issues?

 What do you think?

 Thanks
 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/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
  
 
 .

>>> -- 
>>> 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/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> 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/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
>
> Ildefonso Montero Pérez
> Senior Software Engineer
>
> CloudBees, Inc
>
>
>
> E: imon...@cloudbees.com
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e95f04de-43f8-4b66-a68e-23379638d6f3n%40googlegroups.com.

Re: Jenkins LTS baseline selection

[Ildefonso Montero]

2.289 LGTM

Best,
Ildefonso

On Tue, Apr 20, 2021 at 10:57 AM Raihaan Shouhell 
wrote:

> Hey Tim,
>
> I'm entirely for 2.289 as 2.289 does not make any major changes and as
> Daniel has pointed out, we can backport any fixes.
>
> Cheers,
> Raihaan
>
> On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus  wrote:
>
>> Thanks for raising this Tim.
>> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
>>
>> Can you please confirm the expected timeline, so we can better assess
>> things?
>> Re-reading https://www.jenkins.io/download/lts/ we're looking at a .1 6
>> weeks from now, i.e. some time around 2021-06-02 right ?
>>
>> If so, I agree even choosing the upcoming 2.289 could be acceptable with
>> such a testing period.
>>
>> -- Baptiste
>>
>>
>>
>>
>> Given the expected usua
>>
>>
>>
>> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  a écrit :
>>
>>> Hello everyone,
>>>
>>> Please voice your opinion on which version should be our next core
>>> baseline.
>>>
>>> For me it looks like either 2.288 or 2.289 are the options
>>>
>>> 2.289 (being released today) includes a change for an upcoming firefox
>>> version so it would be good to get it in, but it hasn't had any weekly
>>> soaking time so we could use 2.288 and then backport it in if we don't find
>>> any issues?
>>>
>>> What do you think?
>>>
>>> Thanks
>>> 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com
> 
> .
>


-- 

Ildefonso Montero Pérez
Senior Software Engineer

CloudBees, Inc



E: imont...@cloudbees.com

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BUGhi_VNXH1RXb3yBoX53KvSsDCXXbKniKYYr6kAY%3DiNWJ0fw%40mail.gmail.com.

Re: Jenkins LTS baseline selection

[Raihaan Shouhell]

Hey Tim,

I'm entirely for 2.289 as 2.289 does not make any major changes and as
Daniel has pointed out, we can backport any fixes.

Cheers,
Raihaan

On Tue, Apr 20, 2021 at 4:17 PM Baptiste Mathus  wrote:

> Thanks for raising this Tim.
> As I've written on IRC, as long as we choose 2.288+, I'm happy :).
>
> Can you please confirm the expected timeline, so we can better assess
> things?
> Re-reading https://www.jenkins.io/download/lts/ we're looking at a .1 6
> weeks from now, i.e. some time around 2021-06-02 right ?
>
> If so, I agree even choosing the upcoming 2.289 could be acceptable with
> such a testing period.
>
> -- Baptiste
>
>
>
>
> Given the expected usua
>
>
>
> Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  a écrit :
>
>> Hello everyone,
>>
>> Please voice your opinion on which version should be our next core
>> baseline.
>>
>> For me it looks like either 2.288 or 2.289 are the options
>>
>> 2.289 (being released today) includes a change for an upcoming firefox
>> version so it would be good to get it in, but it hasn't had any weekly
>> soaking time so we could use 2.288 and then backport it in if we don't find
>> any issues?
>>
>> What do you think?
>>
>> Thanks
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgxhKh_v1YRrniinWfJJBx1%3DOqtjEg14aUH3d_EU8VwM7g%40mail.gmail.com.

Re: Jenkins LTS baseline selection

[Baptiste Mathus]

Thanks for raising this Tim.
As I've written on IRC, as long as we choose 2.288+, I'm happy :).

Can you please confirm the expected timeline, so we can better assess
things?
Re-reading https://www.jenkins.io/download/lts/ we're looking at a .1 6
weeks from now, i.e. some time around 2021-06-02 right ?

If so, I agree even choosing the upcoming 2.289 could be acceptable with
such a testing period.

-- Baptiste




Given the expected usua



Le mar. 20 avr. 2021 à 08:53, Tim Jacomb  a écrit :

> Hello everyone,
>
> Please voice your opinion on which version should be our next core
> baseline.
>
> For me it looks like either 2.288 or 2.289 are the options
>
> 2.289 (being released today) includes a change for an upcoming firefox
> version so it would be good to get it in, but it hasn't had any weekly
> soaking time so we could use 2.288 and then backport it in if we don't find
> any issues?
>
> What do you think?
>
> Thanks
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7o6mGZttw4uo2r2RNqHnf7haaSFVmPcUEsphV7ynwkeA%40mail.gmail.com.

Re: Jenkins LTS baseline selection

[Daniel Beck]

In terms of notable user-facing changes, there is fairly little:

https://github.com/jenkinsci/jenkins/pull/5405 - Submit Event
https://github.com/jenkinsci/jenkins/pull/5411 - File parameter
overwriting, which would be backported anyway (I hope)
https://github.com/jenkinsci/jenkins/pull/5424 - Better slow trigger UI

Otherwise there's been Raihaan's label optimization (5412) and Basil's
Guava cleanup (5421), both of which should be safe enough, plus internal
cleanups and some translations.

As of 0fd55bd, I have a slight preference for 2.289 just because I dislike
the original slow trigger UI so much. We're six weeks out (four to RC)
which should be plenty for any serious problems in these changes to show
and allow us to backport fixes, back out problematic changes, or just go
with 2.288 instead.


On Tue, Apr 20, 2021 at 8:53 AM Tim Jacomb  wrote:

> Hello everyone,
>
> Please voice your opinion on which version should be our next core
> baseline.
>
> For me it looks like either 2.288 or 2.289 are the options
>
> 2.289 (being released today) includes a change for an upcoming firefox
> version so it would be good to get it in, but it hasn't had any weekly
> soaking time so we could use 2.288 and then backport it in if we don't find
> any issues?
>
> What do you think?
>
> Thanks
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com
> 
> .
>


-- 

Daniel Beck
Senior Software Engineer
CloudBees, Inc.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLGPMC3YQJQSW_BCYhZy7d6LmND2mevGmXkh4YAM_Labg%40mail.gmail.com.

Jenkins LTS baseline selection

[Tim Jacomb]

Hello everyone,

Please voice your opinion on which version should be our next core baseline.

For me it looks like either 2.288 or 2.289 are the options

2.289 (being released today) includes a change for an upcoming firefox
version so it would be good to get it in, but it hasn't had any weekly
soaking time so we could use 2.288 and then backport it in if we don't find
any issues?

What do you think?

Thanks
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidOjTQoUe7Y4q7m-9hp_UN6JX9t1xNyQTdhwNk3M1LqVg%40mail.gmail.com.

Re: Jenkins LTS Baseline Selection

[Tim Jacomb]

Hello

Given there have been no objections to 2.277 let's take that one.

The new bom  line has been
prepared and the 2 failures are now sorted,
Acceptance tests are not in the best shape, any help here would be greatly
appreciated.

~68 tests failed on the last run
https://ci.jenkins.io/blue/organizations/jenkins/Core%2Facceptance-test-harness/detail/master/296/tests/

25 failed on the latest LTS
https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/stable-2.263/10/tests

Fixes or proposing tests for removal are greatly appreciated, ath test
criteria

.
Thanks Ulli for removing a couple recently


Thanks
Tim

On Thu, 28 Jan 2021 at 10:59, Daniel Beck  wrote:

>
>
> > On 28. Jan 2021, at 10:49, fque...@cloudbees.com <
> fqueir...@cloudbees.com> wrote:
> >
> > +1 for 2.277
>
> Agree. There's no other reasonable choice at the moment.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/ABFE6C3A-D4CA-4FB5-9CCA-0C82FA21AC46%40beckweb.net
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif31Bi9irCZhFVAd6drdHhMpiW3bFqmXgUGHd9oqVMXeA%40mail.gmail.com.

Re: Jenkins LTS Baseline Selection

[Daniel Beck]

> On 28. Jan 2021, at 10:49, fque...@cloudbees.com  
> wrote:
> 
> +1 for 2.277

Agree. There's no other reasonable choice at the moment.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ABFE6C3A-D4CA-4FB5-9CCA-0C82FA21AC46%40beckweb.net.

Re: Jenkins LTS Baseline Selection

[fque...@cloudbees.com]

+1 for 2.277

2.277 includes fixes for major tables to divs issues (JENKINS-64429 and 
JENKINS-64291) that would need to be backported anyway.

On Thursday, January 28, 2021 at 10:12:22 AM UTC+1 Oleg Nenashev wrote:

> Tables to divs is the only real concern in the current state IMHO.
> In the current state it does not really matter which version to take, 
> especially since the diff between 2.276 and 2.277 is pretty smal.
> +1 for 2.277
>
>
> On Thursday, January 28, 2021 at 2:09:43 AM UTC+1 Mark Waite wrote:
>
>> Today is the day for the selection of the baseline version for the March 
>> LTS release.  The Jenkins calendar show the 2.263.4 release on February 10, 
>> 2021, with the next LTS 4 weeks later on March 10, 2021.
>>
>> User feedback on Jenkins 2.276 and 2.277 have improved compared to 
>> previous releases.  I recommend we choose Jenkins 2.277 as the LTS release 
>> baseline.
>>
>> This will be the first LTS release to include:
>>
>>- Tables to divs (as announced in the blog 
>>
>>)
>>- JQuery upgrade
>>- Acegi to Spring Security framework (as announced in Jesse's blog 
>>post )
>>- Xstream unfork (as announced in Jesse's blog post 
>>)
>>
>> Comments and discussion welcomed.
>>
>> Mark Waite
>>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f2070d2d-1439-41f9-a6f8-c7d4fadf4605n%40googlegroups.com.

Re: Jenkins LTS Baseline Selection

[Oleg Nenashev]

Tables to divs is the only real concern in the current state IMHO.
In the current state it does not really matter which version to take, 
especially since the diff between 2.276 and 2.277 is pretty smal.
+1 for 2.277


On Thursday, January 28, 2021 at 2:09:43 AM UTC+1 Mark Waite wrote:

> Today is the day for the selection of the baseline version for the March 
> LTS release.  The Jenkins calendar show the 2.263.4 release on February 10, 
> 2021, with the next LTS 4 weeks later on March 10, 2021.
>
> User feedback on Jenkins 2.276 and 2.277 have improved compared to 
> previous releases.  I recommend we choose Jenkins 2.277 as the LTS release 
> baseline.
>
> This will be the first LTS release to include:
>
>- Tables to divs (as announced in the blog 
>
>)
>- JQuery upgrade
>- Acegi to Spring Security framework (as announced in Jesse's blog post 
>)
>- Xstream unfork (as announced in Jesse's blog post 
>)
>
> Comments and discussion welcomed.
>
> Mark Waite
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2dd74e83-66b6-4a5e-95bc-90c1824241cbn%40googlegroups.com.

Jenkins LTS Baseline Selection

[Mark Waite]

Today is the day for the selection of the baseline version for the March 
LTS release.  The Jenkins calendar show the 2.263.4 release on February 10, 
2021, with the next LTS 4 weeks later on March 10, 2021.

User feedback on Jenkins 2.276 and 2.277 have improved compared to previous 
releases.  I recommend we choose Jenkins 2.277 as the LTS release baseline.

This will be the first LTS release to include:

   - Tables to divs (as announced in the blog 
   
   )
   - JQuery upgrade
   - Acegi to Spring Security framework (as announced in Jesse's blog post 
   )
   - Xstream unfork (as announced in Jesse's blog post 
   )

Comments and discussion welcomed.

Mark Waite

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3fde3369-48fc-41ef-b3c5-637c2e606b46n%40googlegroups.com.

Re: LTS baseline selection for the successor of 2.249

[Radek Antoniuk]

>
>
> Since the selection took place and I can see 2.263.1 in
> https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in
> https://github.com/jenkinsci/bom ?
>

 I think that you will eventually see 2.263.x in the bom rather than
 2.264.x.  I'm sure that a pull request would be welcomed to include 2.263.x
 in the bom.

>>>
>>> That was indeed a typo, I meant 2.263.x.
>>>
>>> Sure, I'm happy to open a PR but... my question was rather about if the
>>> LTS release process should automatically mean that a respective PR should
>>> be opened to the bom repository by the release manager who created the LTS
>>> release?
>>> In my case, I'm actually waiting for that since that blocks a dependency
>>> update (although I actually expected 2.264.x be next LTS, not sure why
>>> 2.263 was preferred).
>>>
>>>
>> Adding a new release to the plugin BOM is part of the new LTS release
>> checklist that is being developed by Tim Jacomb.  See
>> https://github.com/jenkins-infra/release/pull/122 for the initial pull
>> request and https://github.com/jenkins-infra/release/issues/123 for the
>> first use as preparation for Jenkins 2.263.2.
>>
>> Jenkins 2.263 was specifically chosen because it did not include the
>> significant changes that were introduced in 2.264.  Those significant
>> changes are described in
>> https://www.jenkins.io/blog/2020/11/10/major-changes-in-weekly-releases/
>> and in https://www.jenkins.io/blog/2020/11/10/spring-xstream/ .  We
>> wanted 3 months to work on the changes introduced in 2.264 before they were
>> delivered to LTS users as part of the March 2021 LTS release.
>>
>

> 2.263 is available (and has been for awhile) it’s called bom-latest in the
> folder structure
>
> And is available under the 2.263.x artifact ID
>

Indeed, I blindly assumed that bom-latest is for the upcoming new LTS, not
the one that was already released.
Thanks Mark & Tim for explanations.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPe2pWg9n76dJjgt-k31uBrPbXxCuXvG0S6mOHTAZrCtH-aJNQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Tim Jacomb]

2.263 is available (and has been for awhile) it’s called bom-latest in the
folder structure

And is available under the 2.263.x artifact ID

Thanks
Tim

On Mon, 28 Dec 2020 at 19:27, Mark Waite  wrote:

>
>
> On Mon, Dec 28, 2020 at 11:10 AM Radek Antoniuk 
> wrote:
>
>>
 Since the selection took place and I can see 2.263.1 in
 https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in
 https://github.com/jenkinsci/bom ?


>>> I think that you will eventually see 2.263.x in the bom rather than
>>> 2.264.x.  I'm sure that a pull request would be welcomed to include 2.263.x
>>> in the bom.
>>>
>>
>>
>> That was indeed a typo, I meant 2.263.x.
>>
>> Sure, I'm happy to open a PR but... my question was rather about if the
>> LTS release process should automatically mean that a respective PR should
>> be opened to the bom repository by the release manager who created the LTS
>> release?
>> In my case, I'm actually waiting for that since that blocks a dependency
>> update (although I actually expected 2.264.x be next LTS, not sure why
>> 2.263 was preferred).
>>
>>
> Adding a new release to the plugin BOM is part of the new LTS release
> checklist that is being developed by Tim Jacomb.  See
> https://github.com/jenkins-infra/release/pull/122 for the initial pull
> request and https://github.com/jenkins-infra/release/issues/123 for the
> first use as preparation for Jenkins 2.263.2.
>
> Jenkins 2.263 was specifically chosen because it did not include the
> significant changes that were introduced in 2.264.  Those significant
> changes are described in
> https://www.jenkins.io/blog/2020/11/10/major-changes-in-weekly-releases/
> and in https://www.jenkins.io/blog/2020/11/10/spring-xstream/ .  We
> wanted 3 months to work on the changes introduced in 2.264 before they were
> delivered to LTS users as part of the March 2021 LTS release.
>
> Mark Waite
>
>
>>
>>
>>
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPe2pWiZWEXzxb0LMKN%3D4QLf_FDegpxB5LE4%3D0RqPv3rA7DKWw%40mail.gmail.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG3qYr4Wgxkp%3DCF%2B1Q-h0mtAQM5Y1zfc3bxuHqYiU%3DyZg%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifyfpfBoe%2BcD82zZGbv%2BbE-dH-CNdCA9_z8%2B1C-HYW-Lg%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Mark Waite]

On Mon, Dec 28, 2020 at 11:10 AM Radek Antoniuk 
wrote:

>
>>> Since the selection took place and I can see 2.263.1 in
>>> https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in
>>> https://github.com/jenkinsci/bom ?
>>>
>>>
>> I think that you will eventually see 2.263.x in the bom rather than
>> 2.264.x.  I'm sure that a pull request would be welcomed to include 2.263.x
>> in the bom.
>>
>
>
> That was indeed a typo, I meant 2.263.x.
>
> Sure, I'm happy to open a PR but... my question was rather about if the
> LTS release process should automatically mean that a respective PR should
> be opened to the bom repository by the release manager who created the LTS
> release?
> In my case, I'm actually waiting for that since that blocks a dependency
> update (although I actually expected 2.264.x be next LTS, not sure why
> 2.263 was preferred).
>
>
Adding a new release to the plugin BOM is part of the new LTS release
checklist that is being developed by Tim Jacomb.  See
https://github.com/jenkins-infra/release/pull/122 for the initial pull
request and https://github.com/jenkins-infra/release/issues/123 for the
first use as preparation for Jenkins 2.263.2.

Jenkins 2.263 was specifically chosen because it did not include the
significant changes that were introduced in 2.264.  Those significant
changes are described in
https://www.jenkins.io/blog/2020/11/10/major-changes-in-weekly-releases/
and in https://www.jenkins.io/blog/2020/11/10/spring-xstream/ .  We wanted
3 months to work on the changes introduced in 2.264 before they were
delivered to LTS users as part of the March 2021 LTS release.

Mark Waite


>
>
>
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPe2pWiZWEXzxb0LMKN%3D4QLf_FDegpxB5LE4%3D0RqPv3rA7DKWw%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG3qYr4Wgxkp%3DCF%2B1Q-h0mtAQM5Y1zfc3bxuHqYiU%3DyZg%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Radek Antoniuk]

>
>
>> Since the selection took place and I can see 2.263.1 in
>> https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in
>> https://github.com/jenkinsci/bom ?
>>
>>
> I think that you will eventually see 2.263.x in the bom rather than
> 2.264.x.  I'm sure that a pull request would be welcomed to include 2.263.x
> in the bom.
>


That was indeed a typo, I meant 2.263.x.

Sure, I'm happy to open a PR but... my question was rather about if the LTS
release process should automatically mean that a respective PR should be
opened to the bom repository by the release manager who created the LTS
release?
In my case, I'm actually waiting for that since that blocks a dependency
update (although I actually expected 2.264.x be next LTS, not sure why
2.263 was preferred).

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPe2pWiZWEXzxb0LMKN%3D4QLf_FDegpxB5LE4%3D0RqPv3rA7DKWw%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Mark Waite]

On Mon, Dec 28, 2020 at 9:54 AM Radek Antoniuk 
wrote:

> Since the selection took place and I can see 2.263.1 in
> https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in
> https://github.com/jenkinsci/bom ?
>
>
I think that you will eventually see 2.263.x in the bom rather than
2.264.x.  I'm sure that a pull request would be welcomed to include 2.263.x
in the bom.


>
> On Monday, 9 November 2020 at 14:06:02 UTC+1 Mark Waite wrote:
>
>> Yes, 2.263 is the selected baseline for the next Jenkins LTS.
>>
>> On Mon, Nov 9, 2020 at 2:19 AM Antonio Muñiz 
>> wrote:
>>
>>> > Thanks to Oliver for the decision!
>>>
>>> So, is 2.263 the selected one finally?
>>>
>>> On Sat, 24 Oct 2020 at 12:16, Oleg Nenashev  wrote:
>>>
 Thanks to Oliver for the decision! I will go ahead and start switching
 the preview components like JFR and Custom War Packager to use 2.263 by
 default. It should give us some additional testing. Thanks to Jesse Glick
 for starting the Plugin BOM baseline early:
 https://github.com/jenkinsci/bom/releases/tag/bom-16 .

 W.r.t. Windows bits... Yes, the Windows packaging hiccup is
 unfortunate. Unfortunately it would apply to any package we try to ship,
 regardless of the version. We could consider switching Windows packaging to
 alternative setup (e.g. VM instead of a container), but IMHO it would be a
 disservice to users adopting Windows containers provided by the Jenkins
 project. They experience the same issue as us.

 Best regards,
 Oleg


 On Fri, Oct 23, 2020, 14:45 Baptiste Mathus  wrote:

> I agree. 2.263 seems like the least bad option.
>
> Le ven. 23 oct. 2020 à 11:00, Oliver Gondža  a
> écrit :
>
>> For now, we have no better candidate than 2.263. I suggest to accept
>> it,
>> with possibility to reevaluate in two weeks when the line is supposed
>> to
>> be initiated. We will keep it if nothing pressing pops up.
>>
>> On 23/10/2020 02.05, Mark Waite wrote:
>> > That's correct.  The windows installer can't be built (yet) due to
>> an
>> > issue with password expiration and the Windows Docker container.
>> >
>> > Windows users can install prior weekly releases and use the
>> "Upgrade
>> > now" button inside Jenkins to install 2.263 on their Windows
>> computer.
>> >
>> > On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com
>> >  > > > wrote:
>> >
>> > It looks Windows release is not available -
>> > https://github.com/jenkins-infra/jenkins.io/issues/3892
>> >
>> > On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick
>> wrote:
>> >
>> > For what it is worth, 2.263 seems reasonable.
>> > https://www.jenkins.io/changelog/ shows no user complaints
>> so far.
>> >
>> > --
>> > 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/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com
>> > <
>> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com?utm_medium=email_source=footer
>> >.
>> >
>> > --
>> > 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/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com
>> > <
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com?utm_medium=email_source=footer
>> >.
>>
>>
>> --
>> oliver
>>
>> --
>> 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/e59ae697-1d6d-055d-6cb7-0fe75f014897%40gmail.com
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> 

Re: LTS baseline selection for the successor of 2.249

[Radek Antoniuk]

Since the selection took place and I can see 2.263.1 in 
https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x 
in https://github.com/jenkinsci/bom ?


On Monday, 9 November 2020 at 14:06:02 UTC+1 Mark Waite wrote:

> Yes, 2.263 is the selected baseline for the next Jenkins LTS.
>
> On Mon, Nov 9, 2020 at 2:19 AM Antonio Muñiz  wrote:
>
>> > Thanks to Oliver for the decision!
>>
>> So, is 2.263 the selected one finally?
>>
>> On Sat, 24 Oct 2020 at 12:16, Oleg Nenashev  wrote:
>>
>>> Thanks to Oliver for the decision! I will go ahead and start switching 
>>> the preview components like JFR and Custom War Packager to use 2.263 by 
>>> default. It should give us some additional testing. Thanks to Jesse Glick 
>>> for starting the Plugin BOM baseline early: 
>>> https://github.com/jenkinsci/bom/releases/tag/bom-16 .
>>>
>>> W.r.t. Windows bits... Yes, the Windows packaging hiccup is unfortunate. 
>>> Unfortunately it would apply to any package we try to ship, regardless of 
>>> the version. We could consider switching Windows packaging to alternative 
>>> setup (e.g. VM instead of a container), but IMHO it would be a disservice 
>>> to users adopting Windows containers provided by the Jenkins project. They 
>>> experience the same issue as us.
>>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>> On Fri, Oct 23, 2020, 14:45 Baptiste Mathus  wrote:
>>>
 I agree. 2.263 seems like the least bad option.

 Le ven. 23 oct. 2020 à 11:00, Oliver Gondža  a 
 écrit :

> For now, we have no better candidate than 2.263. I suggest to accept 
> it, 
> with possibility to reevaluate in two weeks when the line is supposed 
> to 
> be initiated. We will keep it if nothing pressing pops up.
>
> On 23/10/2020 02.05, Mark Waite wrote:
> > That's correct.  The windows installer can't be built (yet) due to 
> an 
> > issue with password expiration and the Windows Docker container.
> > 
> > Windows users can install prior weekly releases and use the "Upgrade 
> > now" button inside Jenkins to install 2.263 on their Windows 
> computer.
> > 
> > On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com 
> >   > > wrote:
> > 
> > It looks Windows release is not available -
> > https://github.com/jenkins-infra/jenkins.io/issues/3892
> > 
> > On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick 
> wrote:
> > 
> > For what it is worth, 2.263 seems reasonable.
> > https://www.jenkins.io/changelog/ shows no user complaints 
> so far.
> > 
> > -- 
> > 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/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com?utm_medium=email_source=footer
> >.
> > 
> > -- 
> > 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/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com
>  
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com?utm_medium=email_source=footer
> >.
>
>
> -- 
> oliver
>
> -- 
> 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/e59ae697-1d6d-055d-6cb7-0fe75f014897%40gmail.com
> .
>
 -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "Jenkins Developers" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/jenkinsci-dev/AWOPeU4k0DI/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 jenkinsci-de...@googlegroups.com.
 To view this discussion on the web visit 
 

Re: LTS baseline selection for the successor of 2.249

[Mark Waite]

Yes, 2.263 is the selected baseline for the next Jenkins LTS.

On Mon, Nov 9, 2020 at 2:19 AM Antonio Muñiz  wrote:

> > Thanks to Oliver for the decision!
>
> So, is 2.263 the selected one finally?
>
> On Sat, 24 Oct 2020 at 12:16, Oleg Nenashev 
> wrote:
>
>> Thanks to Oliver for the decision! I will go ahead and start switching
>> the preview components like JFR and Custom War Packager to use 2.263 by
>> default. It should give us some additional testing. Thanks to Jesse Glick
>> for starting the Plugin BOM baseline early:
>> https://github.com/jenkinsci/bom/releases/tag/bom-16 .
>>
>> W.r.t. Windows bits... Yes, the Windows packaging hiccup is unfortunate.
>> Unfortunately it would apply to any package we try to ship, regardless of
>> the version. We could consider switching Windows packaging to alternative
>> setup (e.g. VM instead of a container), but IMHO it would be a disservice
>> to users adopting Windows containers provided by the Jenkins project. They
>> experience the same issue as us.
>>
>> Best regards,
>> Oleg
>>
>>
>> On Fri, Oct 23, 2020, 14:45 Baptiste Mathus  wrote:
>>
>>> I agree. 2.263 seems like the least bad option.
>>>
>>> Le ven. 23 oct. 2020 à 11:00, Oliver Gondža  a
>>> écrit :
>>>
 For now, we have no better candidate than 2.263. I suggest to accept
 it,
 with possibility to reevaluate in two weeks when the line is supposed
 to
 be initiated. We will keep it if nothing pressing pops up.

 On 23/10/2020 02.05, Mark Waite wrote:
 > That's correct.  The windows installer can't be built (yet) due to an
 > issue with password expiration and the Windows Docker container.
 >
 > Windows users can install prior weekly releases and use the "Upgrade
 > now" button inside Jenkins to install 2.263 on their Windows computer.
 >
 > On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com
 >  >>> > > wrote:
 >
 > It looks Windows release is not available -
 > https://github.com/jenkins-infra/jenkins.io/issues/3892
 >
 > On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick
 wrote:
 >
 > For what it is worth, 2.263 seems reasonable.
 > https://www.jenkins.io/changelog/ shows no user complaints
 so far.
 >
 > --
 > 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-dev+unsubscr...@googlegroups.com
 > .
 > To view this discussion on the web visit
 >
 https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com
 > <
 https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com?utm_medium=email_source=footer
 >.
 >
 > --
 > 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-dev+unsubscr...@googlegroups.com
 > .
 > To view this discussion on the web visit
 >
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com
 > <
 https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com?utm_medium=email_source=footer
 >.


 --
 oliver

 --
 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-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/e59ae697-1d6d-055d-6cb7-0fe75f014897%40gmail.com
 .

>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-dev/AWOPeU4k0DI/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7N8EjiQjg6zpPYYqbmG6wn3sTV2BGsBFWMHy9j-KCvHQ%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from 

Re: LTS baseline selection for the successor of 2.249

[Antonio Muñiz]

> Thanks to Oliver for the decision!

So, is 2.263 the selected one finally?

On Sat, 24 Oct 2020 at 12:16, Oleg Nenashev  wrote:

> Thanks to Oliver for the decision! I will go ahead and start switching the
> preview components like JFR and Custom War Packager to use 2.263 by
> default. It should give us some additional testing. Thanks to Jesse Glick
> for starting the Plugin BOM baseline early:
> https://github.com/jenkinsci/bom/releases/tag/bom-16 .
>
> W.r.t. Windows bits... Yes, the Windows packaging hiccup is unfortunate.
> Unfortunately it would apply to any package we try to ship, regardless of
> the version. We could consider switching Windows packaging to alternative
> setup (e.g. VM instead of a container), but IMHO it would be a disservice
> to users adopting Windows containers provided by the Jenkins project. They
> experience the same issue as us.
>
> Best regards,
> Oleg
>
>
> On Fri, Oct 23, 2020, 14:45 Baptiste Mathus  wrote:
>
>> I agree. 2.263 seems like the least bad option.
>>
>> Le ven. 23 oct. 2020 à 11:00, Oliver Gondža  a écrit :
>>
>>> For now, we have no better candidate than 2.263. I suggest to accept it,
>>> with possibility to reevaluate in two weeks when the line is supposed to
>>> be initiated. We will keep it if nothing pressing pops up.
>>>
>>> On 23/10/2020 02.05, Mark Waite wrote:
>>> > That's correct.  The windows installer can't be built (yet) due to an
>>> > issue with password expiration and the Windows Docker container.
>>> >
>>> > Windows users can install prior weekly releases and use the "Upgrade
>>> > now" button inside Jenkins to install 2.263 on their Windows computer.
>>> >
>>> > On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com
>>> >  >> > > wrote:
>>> >
>>> > It looks Windows release is not available -
>>> > https://github.com/jenkins-infra/jenkins.io/issues/3892
>>> >
>>> > On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick
>>> wrote:
>>> >
>>> > For what it is worth, 2.263 seems reasonable.
>>> > https://www.jenkins.io/changelog/ shows no user complaints so
>>> far.
>>> >
>>> > --
>>> > 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-dev+unsubscr...@googlegroups.com
>>> > .
>>> > To view this discussion on the web visit
>>> >
>>> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com
>>> > <
>>> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com?utm_medium=email_source=footer
>>> >.
>>> >
>>> > --
>>> > 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-dev+unsubscr...@googlegroups.com
>>> > .
>>> > To view this discussion on the web visit
>>> >
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com
>>> > <
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com?utm_medium=email_source=footer
>>> >.
>>>
>>>
>>> --
>>> oliver
>>>
>>> --
>>> 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/e59ae697-1d6d-055d-6cb7-0fe75f014897%40gmail.com
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/AWOPeU4k0DI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7N8EjiQjg6zpPYYqbmG6wn3sTV2BGsBFWMHy9j-KCvHQ%40mail.gmail.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> 

Re: LTS baseline selection for the successor of 2.249

[Oleg Nenashev]

Thanks to Oliver for the decision! I will go ahead and start switching the
preview components like JFR and Custom War Packager to use 2.263 by
default. It should give us some additional testing. Thanks to Jesse Glick
for starting the Plugin BOM baseline early:
https://github.com/jenkinsci/bom/releases/tag/bom-16 .

W.r.t. Windows bits... Yes, the Windows packaging hiccup is unfortunate.
Unfortunately it would apply to any package we try to ship, regardless of
the version. We could consider switching Windows packaging to alternative
setup (e.g. VM instead of a container), but IMHO it would be a disservice
to users adopting Windows containers provided by the Jenkins project. They
experience the same issue as us.

Best regards,
Oleg


On Fri, Oct 23, 2020, 14:45 Baptiste Mathus  wrote:

> I agree. 2.263 seems like the least bad option.
>
> Le ven. 23 oct. 2020 à 11:00, Oliver Gondža  a écrit :
>
>> For now, we have no better candidate than 2.263. I suggest to accept it,
>> with possibility to reevaluate in two weeks when the line is supposed to
>> be initiated. We will keep it if nothing pressing pops up.
>>
>> On 23/10/2020 02.05, Mark Waite wrote:
>> > That's correct.  The windows installer can't be built (yet) due to an
>> > issue with password expiration and the Windows Docker container.
>> >
>> > Windows users can install prior weekly releases and use the "Upgrade
>> > now" button inside Jenkins to install 2.263 on their Windows computer.
>> >
>> > On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com
>> >  > > > wrote:
>> >
>> > It looks Windows release is not available -
>> > https://github.com/jenkins-infra/jenkins.io/issues/3892
>> >
>> > On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick wrote:
>> >
>> > For what it is worth, 2.263 seems reasonable.
>> > https://www.jenkins.io/changelog/ shows no user complaints so
>> far.
>> >
>> > --
>> > 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-dev+unsubscr...@googlegroups.com
>> > .
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com
>> > <
>> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com?utm_medium=email_source=footer
>> >.
>> >
>> > --
>> > 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-dev+unsubscr...@googlegroups.com
>> > .
>> > To view this discussion on the web visit
>> >
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com
>> > <
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com?utm_medium=email_source=footer
>> >.
>>
>>
>> --
>> oliver
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/e59ae697-1d6d-055d-6cb7-0fe75f014897%40gmail.com
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/AWOPeU4k0DI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7N8EjiQjg6zpPYYqbmG6wn3sTV2BGsBFWMHy9j-KCvHQ%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDSiV4cP_GjnNeELs0AkJamnmv3K2ogt0k4JJS2W-Z%2Bpg%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Baptiste Mathus]

I agree. 2.263 seems like the least bad option.

Le ven. 23 oct. 2020 à 11:00, Oliver Gondža  a écrit :

> For now, we have no better candidate than 2.263. I suggest to accept it,
> with possibility to reevaluate in two weeks when the line is supposed to
> be initiated. We will keep it if nothing pressing pops up.
>
> On 23/10/2020 02.05, Mark Waite wrote:
> > That's correct.  The windows installer can't be built (yet) due to an
> > issue with password expiration and the Windows Docker container.
> >
> > Windows users can install prior weekly releases and use the "Upgrade
> > now" button inside Jenkins to install 2.263 on their Windows computer.
> >
> > On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com
> >   > > wrote:
> >
> > It looks Windows release is not available -
> > https://github.com/jenkins-infra/jenkins.io/issues/3892
> >
> > On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick wrote:
> >
> > For what it is worth, 2.263 seems reasonable.
> > https://www.jenkins.io/changelog/ shows no user complaints so
> far.
> >
> > --
> > 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-dev+unsubscr...@googlegroups.com
> > .
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com?utm_medium=email_source=footer
> >.
> >
> > --
> > 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-dev+unsubscr...@googlegroups.com
> > .
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com?utm_medium=email_source=footer
> >.
>
>
> --
> oliver
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e59ae697-1d6d-055d-6cb7-0fe75f014897%40gmail.com
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7N8EjiQjg6zpPYYqbmG6wn3sTV2BGsBFWMHy9j-KCvHQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Oliver Gondža]

For now, we have no better candidate than 2.263. I suggest to accept it, 
with possibility to reevaluate in two weeks when the line is supposed to 
be initiated. We will keep it if nothing pressing pops up.


On 23/10/2020 02.05, Mark Waite wrote:
That's correct.  The windows installer can't be built (yet) due to an 
issue with password expiration and the Windows Docker container.


Windows users can install prior weekly releases and use the "Upgrade 
now" button inside Jenkins to install 2.263 on their Windows computer.


On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com 
 > wrote:


It looks Windows release is not available -
https://github.com/jenkins-infra/jenkins.io/issues/3892

On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick wrote:

For what it is worth, 2.263 seems reasonable.
https://www.jenkins.io/changelog/ shows no user complaints so far.

-- 
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-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com

.

--
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-dev+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com 
.



--
oliver

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e59ae697-1d6d-055d-6cb7-0fe75f014897%40gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Mark Waite]

That's correct.  The windows installer can't be built (yet) due to an issue
with password expiration and the Windows Docker container.

Windows users can install prior weekly releases and use the "Upgrade now"
button inside Jenkins to install 2.263 on their Windows computer.

On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com 
wrote:

> It looks Windows release is not available -
> https://github.com/jenkins-infra/jenkins.io/issues/3892
>
> On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick wrote:
>
>> For what it is worth, 2.263 seems reasonable.
>> https://www.jenkins.io/changelog/ shows no user complaints so far.
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[vsilv...@gmail.com]

It looks Windows release is not available 
- https://github.com/jenkins-infra/jenkins.io/issues/3892

On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick wrote:

> For what it is worth, 2.263 seems reasonable.
> https://www.jenkins.io/changelog/ shows no user complaints so far.
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/30b38bff-19bc-4897-8d1a-d416b6664ef5n%40googlegroups.com.

Re: LTS baseline selection for the successor of 2.249

[Oleg Nenashev]

Yes, Jira is also fine for 2.263

On Thu, Oct 22, 2020, 23:48 Jesse Glick  wrote:

> For what it is worth, 2.263 seems reasonable.
> https://www.jenkins.io/changelog/ shows no user complaints so far.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/AWOPeU4k0DI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3zXCeJUmwQZCMniORA3Y5VZxPdf6hOYXViyY86w7PgLw%40mail.gmail.com
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCTjghdBv-g45unYLfQijxzRV86sVvMViaxnH%3DVv5xzCA%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Jesse Glick]

For what it is worth, 2.263 seems reasonable.
https://www.jenkins.io/changelog/ shows no user complaints so far.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3zXCeJUmwQZCMniORA3Y5VZxPdf6hOYXViyY86w7PgLw%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Oleg Nenashev]

+1 to what Mark says. We discussed options on the table at the meeting, but
that's it. Oliver was not present at the meeting, and there was not much
feedback in the mailing list by the time of the meeting.



On Thu, Oct 22, 2020, 22:49 Mark Waite  wrote:

> Governance meeting
> <https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#>
> discussion did not bless 2.263.  The discussion is ongoing.
>
> New weekly release 2.263
> <https://www.youtube.com/watch?v=zBOwRubg7FE=youtu.be=75> was
> noted in the governance meeting and noted that the LTS baseline selection
> has not concluded.  Feedback encouraged on the discussion thread.
>
> On Thu, Oct 22, 2020 at 12:44 PM Jesse Glick  wrote:
>
>> Did the governance meeting bless 2.263, or is the debate still open?
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3bk7SObPFA_Lxo_-3gamV2rC6Zu%2BD6QhRXiWPfaRYo8w%40mail.gmail.com
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/AWOPeU4k0DI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFaQr%3DYk9eDp-qCh_c6_qpKMnJ413n67afDQ6xjDqBCRQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFaQr%3DYk9eDp-qCh_c6_qpKMnJ413n67afDQ6xjDqBCRQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAGi%3Dh1TRpjMtyxeM3hNydD4m7nkiHvMTWU_aSkZuJyaw%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Mark Waite]

Governance meeting
<https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#>
discussion did not bless 2.263.  The discussion is ongoing.

New weekly release 2.263
<https://www.youtube.com/watch?v=zBOwRubg7FE=youtu.be=75> was
noted in the governance meeting and noted that the LTS baseline selection
has not concluded.  Feedback encouraged on the discussion thread.

On Thu, Oct 22, 2020 at 12:44 PM Jesse Glick  wrote:

> Did the governance meeting bless 2.263, or is the debate still open?
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3bk7SObPFA_Lxo_-3gamV2rC6Zu%2BD6QhRXiWPfaRYo8w%40mail.gmail.com
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFaQr%3DYk9eDp-qCh_c6_qpKMnJ413n67afDQ6xjDqBCRQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Marky Jackson]

To my knowledge it was blessed

> On Oct 22, 2020, at 11:43 AM, Jesse Glick  wrote:
> 
> Did the governance meeting bless 2.263, or is the debate still open?
> 
> -- 
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3bk7SObPFA_Lxo_-3gamV2rC6Zu%2BD6QhRXiWPfaRYo8w%40mail.gmail.com.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/22AB3065-09F2-40EE-8ABC-66F2E915D523%40gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Jesse Glick]

Did the governance meeting bless 2.263, or is the debate still open?

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3bk7SObPFA_Lxo_-3gamV2rC6Zu%2BD6QhRXiWPfaRYo8w%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Tim Jacomb]

We’ve been running it in production since yesterday

On Thu, 22 Oct 2020 at 12:52, Oleg Nenashev  wrote:

> My instances have been running on 2.263 since Tuesday. I have also
> switched my test Jenkinsfile Runner testing setup to 2.263, and it looks
> good.
>
> The biggest issue I see in production is the Trilead API plugin regression
> in the latest versions. Not relevant to the core LTS baseline though we may
> want to update the bundled version before the release.
>
>
>
> On Thu, Oct 22, 2020, 13:46 Mark Waite  wrote:
>
>> I've successfully switched my test environment to Jenkins 2.263. I'll
>> continue running in that environment.  It is looking good so far.
>>
>> On Thu, Oct 22, 2020 at 4:59 AM Tim Jacomb  wrote:
>>
>>> 2.263 is looking like the best option, so far no reports of issues in it.
>>>
>>> 2.263 was reverting / fixing the last of the major regressions in the
>>> previous versions.
>>>
>>> Thanks
>>> Tim
>>>
>>> On Tue, 20 Oct 2020 at 21:48, Oleg Nenashev 
>>> wrote:
>>>
 I hope the today's 2.263 stabilizes the weekly release line:
 https://www.jenkins.io/changelog/#v2.263. We have integrated the issue
 63958  regression
 fix, and the rest of the changes were very conservative. Unless there is
 something really bad with this release, I would suggest selecting it. With
 4 weeks until the release candidate, we should be able to mitigate other
 regressions if somethings pops up.

 I will try to facilitate the community feedback through social media.

 Best regards,
 Oleg



 On Tuesday, October 20, 2020 at 3:52:22 PM UTC+2 ogondza wrote:

> Let's voice the baseline candidate suggestions and concerns.
>
> We seem to be in the situation where all recent weeklies are fixing
> recent regressions making none of them an appealing candidate to me. I
> do not feel like choosing the latest weekly in a hope all will be well
> from now on. But at the same time 2.258 (2020-09-22), the latest
> release
> its changelog is filling me with confidence, feels too old by now.
>
> Thoughts?
>
> https://jenkins.io/changelog/
> --
> oliver
>
 --
 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-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/19940acc-d16b-4fca-a985-96c7ce9a6fd1n%40googlegroups.com
 
 .

>>> --
>>> 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieDRMn4bSCVsZ7ugkXpNP6oe7SH8MpmW-Fy%3D806MvNTWQ%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>>
> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/AWOPeU4k0DI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFt%3DoeQQK-Bxm7dBVtg35Tk00ry%3DDviNSQF0TN-Wok8hQ%40mail.gmail.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDi4aky3dZ6szMw%2BJ_jLy84E7f68Gkg-NF-v_4qAN1LOA%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: LTS baseline selection for the successor of 2.249

[Oleg Nenashev]

My instances have been running on 2.263 since Tuesday. I have also switched
my test Jenkinsfile Runner testing setup to 2.263, and it looks good.

The biggest issue I see in production is the Trilead API plugin regression
in the latest versions. Not relevant to the core LTS baseline though we may
want to update the bundled version before the release.



On Thu, Oct 22, 2020, 13:46 Mark Waite  wrote:

> I've successfully switched my test environment to Jenkins 2.263. I'll
> continue running in that environment.  It is looking good so far.
>
> On Thu, Oct 22, 2020 at 4:59 AM Tim Jacomb  wrote:
>
>> 2.263 is looking like the best option, so far no reports of issues in it.
>>
>> 2.263 was reverting / fixing the last of the major regressions in the
>> previous versions.
>>
>> Thanks
>> Tim
>>
>> On Tue, 20 Oct 2020 at 21:48, Oleg Nenashev 
>> wrote:
>>
>>> I hope the today's 2.263 stabilizes the weekly release line:
>>> https://www.jenkins.io/changelog/#v2.263. We have integrated the issue
>>> 63958  regression
>>> fix, and the rest of the changes were very conservative. Unless there is
>>> something really bad with this release, I would suggest selecting it. With
>>> 4 weeks until the release candidate, we should be able to mitigate other
>>> regressions if somethings pops up.
>>>
>>> I will try to facilitate the community feedback through social media.
>>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>>
>>> On Tuesday, October 20, 2020 at 3:52:22 PM UTC+2 ogondza wrote:
>>>
 Let's voice the baseline candidate suggestions and concerns.

 We seem to be in the situation where all recent weeklies are fixing
 recent regressions making none of them an appealing candidate to me. I
 do not feel like choosing the latest weekly in a hope all will be well
 from now on. But at the same time 2.258 (2020-09-22), the latest
 release
 its changelog is filling me with confidence, feels too old by now.

 Thoughts?

 https://jenkins.io/changelog/
 --
 oliver

>>> --
>>> 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/19940acc-d16b-4fca-a985-96c7ce9a6fd1n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieDRMn4bSCVsZ7ugkXpNP6oe7SH8MpmW-Fy%3D806MvNTWQ%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/AWOPeU4k0DI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFt%3DoeQQK-Bxm7dBVtg35Tk00ry%3DDviNSQF0TN-Wok8hQ%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDi4aky3dZ6szMw%2BJ_jLy84E7f68Gkg-NF-v_4qAN1LOA%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Mark Waite]

I've successfully switched my test environment to Jenkins 2.263. I'll
continue running in that environment.  It is looking good so far.

On Thu, Oct 22, 2020 at 4:59 AM Tim Jacomb  wrote:

> 2.263 is looking like the best option, so far no reports of issues in it.
>
> 2.263 was reverting / fixing the last of the major regressions in the
> previous versions.
>
> Thanks
> Tim
>
> On Tue, 20 Oct 2020 at 21:48, Oleg Nenashev 
> wrote:
>
>> I hope the today's 2.263 stabilizes the weekly release line:
>> https://www.jenkins.io/changelog/#v2.263. We have integrated the issue
>> 63958  regression
>> fix, and the rest of the changes were very conservative. Unless there is
>> something really bad with this release, I would suggest selecting it. With
>> 4 weeks until the release candidate, we should be able to mitigate other
>> regressions if somethings pops up.
>>
>> I will try to facilitate the community feedback through social media.
>>
>> Best regards,
>> Oleg
>>
>>
>>
>> On Tuesday, October 20, 2020 at 3:52:22 PM UTC+2 ogondza wrote:
>>
>>> Let's voice the baseline candidate suggestions and concerns.
>>>
>>> We seem to be in the situation where all recent weeklies are fixing
>>> recent regressions making none of them an appealing candidate to me. I
>>> do not feel like choosing the latest weekly in a hope all will be well
>>> from now on. But at the same time 2.258 (2020-09-22), the latest release
>>> its changelog is filling me with confidence, feels too old by now.
>>>
>>> Thoughts?
>>>
>>> https://jenkins.io/changelog/
>>> --
>>> oliver
>>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/19940acc-d16b-4fca-a985-96c7ce9a6fd1n%40googlegroups.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieDRMn4bSCVsZ7ugkXpNP6oe7SH8MpmW-Fy%3D806MvNTWQ%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFt%3DoeQQK-Bxm7dBVtg35Tk00ry%3DDviNSQF0TN-Wok8hQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Tim Jacomb]

2.263 is looking like the best option, so far no reports of issues in it.

2.263 was reverting / fixing the last of the major regressions in the
previous versions.

Thanks
Tim

On Tue, 20 Oct 2020 at 21:48, Oleg Nenashev  wrote:

> I hope the today's 2.263 stabilizes the weekly release line:
> https://www.jenkins.io/changelog/#v2.263. We have integrated the issue
> 63958  regression
> fix, and the rest of the changes were very conservative. Unless there is
> something really bad with this release, I would suggest selecting it. With
> 4 weeks until the release candidate, we should be able to mitigate other
> regressions if somethings pops up.
>
> I will try to facilitate the community feedback through social media.
>
> Best regards,
> Oleg
>
>
>
> On Tuesday, October 20, 2020 at 3:52:22 PM UTC+2 ogondza wrote:
>
>> Let's voice the baseline candidate suggestions and concerns.
>>
>> We seem to be in the situation where all recent weeklies are fixing
>> recent regressions making none of them an appealing candidate to me. I
>> do not feel like choosing the latest weekly in a hope all will be well
>> from now on. But at the same time 2.258 (2020-09-22), the latest release
>> its changelog is filling me with confidence, feels too old by now.
>>
>> Thoughts?
>>
>> https://jenkins.io/changelog/
>> --
>> oliver
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/19940acc-d16b-4fca-a985-96c7ce9a6fd1n%40googlegroups.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieDRMn4bSCVsZ7ugkXpNP6oe7SH8MpmW-Fy%3D806MvNTWQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Oleg Nenashev]

I hope the today's 2.263 stabilizes the weekly release line: 
https://www.jenkins.io/changelog/#v2.263. We have integrated the issue 63958 
 regression fix, and 
the rest of the changes were very conservative. Unless there is something 
really bad with this release, I would suggest selecting it. With 4 weeks 
until the release candidate, we should be able to mitigate other 
regressions if somethings pops up.

I will try to facilitate the community feedback through social media.

Best regards,
Oleg



On Tuesday, October 20, 2020 at 3:52:22 PM UTC+2 ogondza wrote:

> Let's voice the baseline candidate suggestions and concerns.
>
> We seem to be in the situation where all recent weeklies are fixing 
> recent regressions making none of them an appealing candidate to me. I 
> do not feel like choosing the latest weekly in a hope all will be well 
> from now on. But at the same time 2.258 (2020-09-22), the latest release 
> its changelog is filling me with confidence, feels too old by now.
>
> Thoughts?
>
> https://jenkins.io/changelog/
> -- 
> oliver
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/19940acc-d16b-4fca-a985-96c7ce9a6fd1n%40googlegroups.com.

LTS baseline selection for the successor of 2.249

[Oliver Gondža]

Let's voice the baseline candidate suggestions and concerns.

We seem to be in the situation where all recent weeklies are fixing 
recent regressions making none of them an appealing candidate to me. I 
do not feel like choosing the latest weekly in a hope all will be well 
from now on. But at the same time 2.258 (2020-09-22), the latest release 
its changelog is filling me with confidence, feels too old by now.


Thoughts?

https://jenkins.io/changelog/
--
oliver

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ade43a0c-24f6-e065-fb51-4d1fae279cdb%40gmail.com.

Re: LTS baseline selection for the successor of 2.235

[Oleg Nenashev]

Thanks Oliver! I have added the target dates for 2.249.1 to the event 
calendar.

On Saturday, August 1, 2020 at 10:30:41 AM UTC+2, ogondza wrote:
>
> Avoiding 2.250 so it is not confused with 2.150 is an interesting 
> suggestion, though it does not outweigh stability so 2.249 is preferable 
> over 2.251.
>
> I do not think backporting the only fix from 2.250 to 2.249 is going to 
> confuse anyone: users need to track *when* the fix was introduced in 
> weekly and LTS separately and I doubt they care much *how* specifically 
> it have happened.
>
> *So, I am declaring 2.249 a winner.*
>
> As always, thanks a lot for all the inputs! Even when your suggestions was 
> not followed, please keep them coming to ensure the hight quality of the 
> results produced.
>
> Thanks!
> --
> oliver
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/65ae85e2-0e80-4b7a-a09d-7a9f3bf7a4e2o%40googlegroups.com.

Re: LTS baseline selection for the successor of 2.235

[ogondza]

Avoiding 2.250 so it is not confused with 2.150 is an interesting 
suggestion, though it does not outweigh stability so 2.249 is preferable 
over 2.251.

I do not think backporting the only fix from 2.250 to 2.249 is going to 
confuse anyone: users need to track *when* the fix was introduced in weekly 
and LTS separately and I doubt they care much *how* specifically it have 
happened.

*So, I am declaring 2.249 a winner.*

As always, thanks a lot for all the inputs! Even when your suggestions was 
not followed, please keep them coming to ensure the hight quality of the 
results produced.

Thanks!
--
oliver

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/00077a7b-71fb-495c-b9ae-4928b1c66aaco%40googlegroups.com.

Re: LTS baseline selection for the successor of 2.235

[Daniel Beck]

On Fri, Jul 31, 2020 at 7:11 PM Mark Waite 
wrote:

> We could also choose 2.251 and have the most of the same improvement in
> clarity for user communication, but it would bring the other changes from
> 2.251 into the LTS baseline.
>

Unless we merge something potentially causing regressions (and we
shouldn't, see core maintainer guidelines) that release should be a safe
choice too. Don't know whether Oliver would be OK with that approach given
we deliberately moved the baseline decision earlier.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BH7mPE7jX8KgXOu2%3D8QBVJcsJCHFFbyF%2BJMkbsHKK9Bg%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.235

[Mark Waite]

On Fri, Jul 31, 2020 at 10:11 AM Jesse Glick  wrote:

> Seems more confusing to me to take 2.249 given that you will
> immediately need to backport the one non-cosmetic change in 2.250
> (#4879) but it does not really matter much one way or the other.
>
>
I think we may have different people that we're trying to avoid confusing.
I would expect developers to be confused that we chose 2.249 and backported
a change that was in 2.250 (along with other changes).  I think we should
accept that they may be confused by that choice.  I believe the goal in
choosing 2.249 is to reduce confusion for users as they are reporting an
issue.  They are less likely to make a mistake listing the version number
as 2.249 than if it were 2.250.

We could also choose 2.251 and have the most of the same improvement in
clarity for user communication, but it would bring the other changes from
2.251 into the LTS baseline.

Mark Waite


> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0nn4jphWRXinRtTOZfPg6HO7o7sYoR2vhSxhBCAkebag%40mail.gmail.com
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE47z9sbn4he43z7z_wMv-2ROOvEG5Sz1-Q7R2%3DKn2AzQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.235

[Jesse Glick]

Seems more confusing to me to take 2.249 given that you will
immediately need to backport the one non-cosmetic change in 2.250
(#4879) but it does not really matter much one way or the other.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0nn4jphWRXinRtTOZfPg6HO7o7sYoR2vhSxhBCAkebag%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.235

[Mark Waite]

I agree with Daniel that we should prefer 2.249 or consider 2.251 so that
we avoid confusion in bug reports.  I also like that Ulli noted it
increases the Hamming distance.  It has been a while since I thought about
Hamming codes.

On Thu, Jul 30, 2020 at 2:22 PM Daniel Beck  wrote:

>
>
> > On 29. Jul 2020, at 13:59, Oleg Nenashev  wrote:
> >
> > 2.250 is a fancy number, so why not?
>
> As I previously explained, too similar to 2.150 which was also an LTS
> baseline. Since there's no other notable difference to 2.249, I would
> prefer less confusing bug reports over having a nice looking number.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/374FBAD1-9229-4EC1-B333-1B1BF1B299B5%40beckweb.net
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEw3QRSpm-5UncC%2Bc4M%2BJSpeZ9MBisxvL0W1THqbY36LQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.235

[Daniel Beck]

> On 29. Jul 2020, at 13:59, Oleg Nenashev  wrote:
> 
> 2.250 is a fancy number, so why not?

As I previously explained, too similar to 2.150 which was also an LTS baseline. 
Since there's no other notable difference to 2.249, I would prefer less 
confusing bug reports over having a nice looking number.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/374FBAD1-9229-4EC1-B333-1B1BF1B299B5%40beckweb.net.

Re: LTS baseline selection for the successor of 2.235

[Matt Sicker]

If you're going by neat numbers, 2.255 would be the coolest. ;)

On Wed, Jul 29, 2020 at 8:03 AM Tim Jacomb  wrote:

> I vote for 2.250, with some backporting needed.
>
> Thanks
> Tim
>
> On Wed, 29 Jul 2020 at 12:59, Oleg Nenashev 
> wrote:
>
>> Hi all,
>>
>> I would vote for 2.250. 2.250 has no functional difference from 2.249,
>> there is just one internal fix. 2.250 is a fancy number, so why not?
>>
>> 2.249/2.250 still have issues after the .NET Framework 2.0 support
>> removal. Both issues need some fixes and upgrade guidelines. I believe that
>> I will be able to prepare and integrate the fixes by the next LTS RC in 4
>> weeks. If we want to take older version without regressions, it would be
>> 2.247 which lacks many other important patches. I'd rather go ahead with
>> the version and get it fixed.
>>
>>- Windows Agent Installer Module:
>>https://issues.jenkins-ci.org/browse/JENKINS-63198
>>- WMI Windows Agents installer:
>>https://issues.jenkins-ci.org/browse/JENKINS-63223
>>
>> +1 to Daniel's comment about UI changes. As discussed at the last UX SIG
>> meeting we have an option to backport fixes for UI before the RC date if
>> there is a consensus.
>>
>> Best regards,
>> Oleg
>>
>> On Wednesday, July 29, 2020 at 1:54:42 PM UTC+2, Daniel Beck wrote:
>>>
>>> Is this about https://github.com/jenkinsci/jenkins/pull/4867 ? We can
>>> always backport that change if needed.
>>>
>>> Or, with some merge discipline we could tentatively choose 2.251 and
>>> fall back to 2.250/2.249 (which are basically identical) if something we
>>> don't want makes it in.
>>>
>>> 2.250 is a nicer number but might cause confusion with 2.150 which was
>>> also an LTS baseline, so would tentatively prefer 2.249 for greater Hamming
>>> distance.
>>>
>>>
>>> On Wed, Jul 29, 2020 at 1:20 PM Ullrich Hafner 
>>> wrote:
>>>
 That means that we have the intermediate black table headers in it :-(

 Am 29.07.2020 um 13:14 schrieb Antonio Muñiz :

 This is the full list of bugs reported after the previous LTS release
 date
 
 .
 I had a quick look and I don't see anything clearly blocking the LTS
 release (JENKINS-63082  smells bad, but it was
 already in the previous LTS, so not a regression).

 2.249 looks good to me.

 On Wed, 29 Jul 2020 at 12:00, Oliver Gondža  wrote:

> Let's voice the baseline candidates and concerns so we have the
> candidate agreed on by the end of the week.
>
> To get the discussion started, how about 2.249?
>
> https://jenkins.io/changelog/
> --
> oliver
>
> --
> 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 jenkin...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3292bcc0-2fb5-08ab-51b6-fb88f53c0eb4%40gmail.com
> .
>


 --
 Antonio Muñiz
 Human, Engineer
 CloudBees, Inc.

 --
 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 jenkin...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzTmwdY875R4bV8h_tbRM4%2Bm3-XRiiqoHBccn8DUjJrQXQ%40mail.gmail.com
 
 .


 --
 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 jenkin...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/0B575C1E-06AD-4D04-BDA2-0424269AAB8F%40gmail.com
 
 .

>>>
>>>
>>> --
>>>
>>> Daniel Beck
>>> Senior Software Engineer
>>> CloudBees, Inc.
>>>
>>>
>>>
>>>
>>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/aadb0f8f-7847-4ad6-a5a0-e396f03bbabeo%40googlegroups.com
>> 

Re: LTS baseline selection for the successor of 2.235

[Tim Jacomb]

I vote for 2.250, with some backporting needed.

Thanks
Tim

On Wed, 29 Jul 2020 at 12:59, Oleg Nenashev  wrote:

> Hi all,
>
> I would vote for 2.250. 2.250 has no functional difference from 2.249,
> there is just one internal fix. 2.250 is a fancy number, so why not?
>
> 2.249/2.250 still have issues after the .NET Framework 2.0 support
> removal. Both issues need some fixes and upgrade guidelines. I believe that
> I will be able to prepare and integrate the fixes by the next LTS RC in 4
> weeks. If we want to take older version without regressions, it would be
> 2.247 which lacks many other important patches. I'd rather go ahead with
> the version and get it fixed.
>
>- Windows Agent Installer Module:
>https://issues.jenkins-ci.org/browse/JENKINS-63198
>- WMI Windows Agents installer:
>https://issues.jenkins-ci.org/browse/JENKINS-63223
>
> +1 to Daniel's comment about UI changes. As discussed at the last UX SIG
> meeting we have an option to backport fixes for UI before the RC date if
> there is a consensus.
>
> Best regards,
> Oleg
>
> On Wednesday, July 29, 2020 at 1:54:42 PM UTC+2, Daniel Beck wrote:
>>
>> Is this about https://github.com/jenkinsci/jenkins/pull/4867 ? We can
>> always backport that change if needed.
>>
>> Or, with some merge discipline we could tentatively choose 2.251 and fall
>> back to 2.250/2.249 (which are basically identical) if something we don't
>> want makes it in.
>>
>> 2.250 is a nicer number but might cause confusion with 2.150 which was
>> also an LTS baseline, so would tentatively prefer 2.249 for greater Hamming
>> distance.
>>
>>
>> On Wed, Jul 29, 2020 at 1:20 PM Ullrich Hafner 
>> wrote:
>>
>>> That means that we have the intermediate black table headers in it :-(
>>>
>>> Am 29.07.2020 um 13:14 schrieb Antonio Muñiz :
>>>
>>> This is the full list of bugs reported after the previous LTS release
>>> date
>>> 
>>> .
>>> I had a quick look and I don't see anything clearly blocking the LTS
>>> release (JENKINS-63082  smells bad, but it was
>>> already in the previous LTS, so not a regression).
>>>
>>> 2.249 looks good to me.
>>>
>>> On Wed, 29 Jul 2020 at 12:00, Oliver Gondža  wrote:
>>>
 Let's voice the baseline candidates and concerns so we have the
 candidate agreed on by the end of the week.

 To get the discussion started, how about 2.249?

 https://jenkins.io/changelog/
 --
 oliver

 --
 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 jenkin...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/3292bcc0-2fb5-08ab-51b6-fb88f53c0eb4%40gmail.com
 .

>>>
>>>
>>> --
>>> Antonio Muñiz
>>> Human, Engineer
>>> CloudBees, Inc.
>>>
>>> --
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzTmwdY875R4bV8h_tbRM4%2Bm3-XRiiqoHBccn8DUjJrQXQ%40mail.gmail.com
>>> 
>>> .
>>>
>>>
>>> --
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/0B575C1E-06AD-4D04-BDA2-0424269AAB8F%40gmail.com
>>> 
>>> .
>>>
>>
>>
>> --
>>
>> Daniel Beck
>> Senior Software Engineer
>> CloudBees, Inc.
>>
>>
>>
>>
>> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/aadb0f8f-7847-4ad6-a5a0-e396f03bbabeo%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this 

Re: LTS baseline selection for the successor of 2.235

[Oleg Nenashev]

Hi all,

I would vote for 2.250. 2.250 has no functional difference from 2.249, 
there is just one internal fix. 2.250 is a fancy number, so why not?

2.249/2.250 still have issues after the .NET Framework 2.0 support removal. 
Both issues need some fixes and upgrade guidelines. I believe that I will 
be able to prepare and integrate the fixes by the next LTS RC in 4 weeks. 
If we want to take older version without regressions, it would be 2.247 
which lacks many other important patches. I'd rather go ahead with the 
version and get it fixed.

   - Windows Agent Installer Module: 
   https://issues.jenkins-ci.org/browse/JENKINS-63198
   - WMI Windows Agents installer: 
   https://issues.jenkins-ci.org/browse/JENKINS-63223

+1 to Daniel's comment about UI changes. As discussed at the last UX SIG 
meeting we have an option to backport fixes for UI before the RC date if 
there is a consensus.

Best regards,
Oleg

On Wednesday, July 29, 2020 at 1:54:42 PM UTC+2, Daniel Beck wrote:
>
> Is this about https://github.com/jenkinsci/jenkins/pull/4867 ? We can 
> always backport that change if needed.
>
> Or, with some merge discipline we could tentatively choose 2.251 and fall 
> back to 2.250/2.249 (which are basically identical) if something we don't 
> want makes it in.
>
> 2.250 is a nicer number but might cause confusion with 2.150 which was 
> also an LTS baseline, so would tentatively prefer 2.249 for greater Hamming 
> distance.
>
>
> On Wed, Jul 29, 2020 at 1:20 PM Ullrich Hafner  > wrote:
>
>> That means that we have the intermediate black table headers in it :-( 
>>
>> Am 29.07.2020 um 13:14 schrieb Antonio Muñiz > >:
>>
>> This is the full list of bugs reported after the previous LTS release 
>> date 
>> 
>> .
>> I had a quick look and I don't see anything clearly blocking the LTS 
>> release (JENKINS-63082  smells bad, but it was 
>> already in the previous LTS, so not a regression).
>>
>> 2.249 looks good to me.
>>
>> On Wed, 29 Jul 2020 at 12:00, Oliver Gondža > > wrote:
>>
>>> Let's voice the baseline candidates and concerns so we have the 
>>> candidate agreed on by the end of the week.
>>>
>>> To get the discussion started, how about 2.249?
>>>
>>> https://jenkins.io/changelog/
>>> -- 
>>> oliver
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/3292bcc0-2fb5-08ab-51b6-fb88f53c0eb4%40gmail.com
>>> .
>>>
>>
>>
>> -- 
>> Antonio Muñiz
>> Human, Engineer
>> CloudBees, Inc.
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzTmwdY875R4bV8h_tbRM4%2Bm3-XRiiqoHBccn8DUjJrQXQ%40mail.gmail.com
>>  
>> 
>> .
>>
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/0B575C1E-06AD-4D04-BDA2-0424269AAB8F%40gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
>
> Daniel Beck
> Senior Software Engineer
> CloudBees, Inc.
>
>   
>
>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/aadb0f8f-7847-4ad6-a5a0-e396f03bbabeo%40googlegroups.com.

Re: LTS baseline selection for the successor of 2.235

[Daniel Beck]

Is this about https://github.com/jenkinsci/jenkins/pull/4867 ? We can
always backport that change if needed.

Or, with some merge discipline we could tentatively choose 2.251 and fall
back to 2.250/2.249 (which are basically identical) if something we don't
want makes it in.

2.250 is a nicer number but might cause confusion with 2.150 which was also
an LTS baseline, so would tentatively prefer 2.249 for greater Hamming
distance.


On Wed, Jul 29, 2020 at 1:20 PM Ullrich Hafner 
wrote:

> That means that we have the intermediate black table headers in it :-(
>
> Am 29.07.2020 um 13:14 schrieb Antonio Muñiz :
>
> This is the full list of bugs reported after the previous LTS release date
> 
> .
> I had a quick look and I don't see anything clearly blocking the LTS
> release (JENKINS-63082  smells bad, but it was
> already in the previous LTS, so not a regression).
>
> 2.249 looks good to me.
>
> On Wed, 29 Jul 2020 at 12:00, Oliver Gondža  wrote:
>
>> Let's voice the baseline candidates and concerns so we have the
>> candidate agreed on by the end of the week.
>>
>> To get the discussion started, how about 2.249?
>>
>> https://jenkins.io/changelog/
>> --
>> oliver
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/3292bcc0-2fb5-08ab-51b6-fb88f53c0eb4%40gmail.com
>> .
>>
>
>
> --
> Antonio Muñiz
> Human, Engineer
> CloudBees, Inc.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzTmwdY875R4bV8h_tbRM4%2Bm3-XRiiqoHBccn8DUjJrQXQ%40mail.gmail.com
> 
> .
>
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/0B575C1E-06AD-4D04-BDA2-0424269AAB8F%40gmail.com
> 
> .
>


-- 

Daniel Beck
Senior Software Engineer
CloudBees, Inc.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJp2FoO1rkGgzBk62mJfntCAg1UH_p6-j_mfEPebUEyOA%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.235

[Ullrich Hafner]

That means that we have the intermediate black table headers in it :-( 

> Am 29.07.2020 um 13:14 schrieb Antonio Muñiz :
> 
> This is the full list of bugs reported after the previous LTS release date 
> .
> I had a quick look and I don't see anything clearly blocking the LTS release 
> (JENKINS-63082  smells bad, but it was already in the 
> previous LTS, so not a regression).
> 
> 2.249 looks good to me.
> 
> On Wed, 29 Jul 2020 at 12:00, Oliver Gondža  > wrote:
> Let's voice the baseline candidates and concerns so we have the 
> candidate agreed on by the end of the week.
> 
> To get the discussion started, how about 2.249?
> 
> https://jenkins.io/changelog/ 
> -- 
> oliver
> 
> -- 
> 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-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/3292bcc0-2fb5-08ab-51b6-fb88f53c0eb4%40gmail.com
>  
> .
> 
> 
> -- 
> Antonio Muñiz
> Human, Engineer
> CloudBees, Inc.
> 
> -- 
> 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-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzTmwdY875R4bV8h_tbRM4%2Bm3-XRiiqoHBccn8DUjJrQXQ%40mail.gmail.com
>  
> .

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0B575C1E-06AD-4D04-BDA2-0424269AAB8F%40gmail.com.

Re: LTS baseline selection for the successor of 2.235

[Antonio Muñiz]

This is the full list of bugs reported after the previous LTS release date

.
I had a quick look and I don't see anything clearly blocking the LTS
release (JENKINS-63082 smells bad, but it was already in the previous LTS,
so not a regression).

2.249 looks good to me.

On Wed, 29 Jul 2020 at 12:00, Oliver Gondža  wrote:

> Let's voice the baseline candidates and concerns so we have the
> candidate agreed on by the end of the week.
>
> To get the discussion started, how about 2.249?
>
> https://jenkins.io/changelog/
> --
> oliver
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3292bcc0-2fb5-08ab-51b6-fb88f53c0eb4%40gmail.com
> .
>


-- 
Antonio Muñiz
Human, Engineer
CloudBees, Inc.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzTmwdY875R4bV8h_tbRM4%2Bm3-XRiiqoHBccn8DUjJrQXQ%40mail.gmail.com.

LTS baseline selection for the successor of 2.235

[Oliver Gondža]

Let's voice the baseline candidates and concerns so we have the 
candidate agreed on by the end of the week.


To get the discussion started, how about 2.249?

https://jenkins.io/changelog/
--
oliver

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3292bcc0-2fb5-08ab-51b6-fb88f53c0eb4%40gmail.com.

Re: LTS baseline selection for the successor of 2.222

[Oleg Nenashev]

Thanks Oliver and all contributors!

On Wednesday, May 6, 2020 at 10:47:51 PM UTC+2, ogondza wrote:
>
> After the discussion on the Governance Meeting, we agreed to go for 
> 2.235 as a next LTS baseline. 2.235.1 is expected to be out six weeks 
> from now. 
>
> On 29/04/2020 18.36, Mark Waite wrote: 
> > +1 from me for 2.235, particularly with the additional UI improvements 
> > in recent releases. 
> > 
> > Also assuming that there will be *lots of help testing the release 
> > candidate* once it is delivered . ☺ ☺ ☺ 
> > 
> > On Wed, Apr 29, 2020 at 9:59 AM Oleg Nenashev   
> > > wrote: 
> > 
> > +1 for 2.235, assuming that we are conservative about merges this 
> week. 
> > 
> > On Wednesday, April 29, 2020 at 5:47:41 PM UTC+2, Tim Jacomb wrote: 
> > 
> > 2.235 would also be my preference, I've got 2 (hopefully) last 
> > system read PRs, I would love to get in before the LTS 
> > 
> > On Wed, 29 Apr 2020 at 14:54, Daniel Beck  
> wrote: 
> > 
> > 
> > 
> >  > On 29. Apr 2020, at 12:44, Oliver Gondža 
> >  wrote: 
> >  > 
> >  > In accordance we recently approved process changes, we 
> > are doing next baseline section two weeks earlier in the 
> cycle. 
> > 
> > Assuming nobody merges something crazy into core this week, 
> > I'm for 2.235. 
> > 
> > We've moved the baseline decision earlier to give us the 
> > freedom to choose a very recent release without a lot of 
> > risk and overlapping work schedules, since we'll have 4 
> > weeks to identify and fix problems and back port those 
> > fixes. So I propose we try this and see how it goes. 
> > 
> > (FWIW we probably want to figure out what to do about 
> > JENKINS-61937 before the new LTS lands…) 
> > 
> > -- 
> > 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 jenkin...@googlegroups.com. 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/jenkinsci-dev/900CA800-A7CB-486B-B49A-93DF05F30CB8%40beckweb.net.
>  
>
> > 
> > -- 
> > 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 jenkin...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/jenkinsci-dev/c34d0118-503e-42e3-b6e3-e57384621cf0%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/c34d0118-503e-42e3-b6e3-e57384621cf0%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
> > 
> > -- 
> > 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 jenkin...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHCpxgwu3qjVa1RVhn_x44jYhBniu3dOzOPsZZ3SUQJ0A%40mail.gmail.com
>  
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHCpxgwu3qjVa1RVhn_x44jYhBniu3dOzOPsZZ3SUQJ0A%40mail.gmail.com?utm_medium=email_source=footer>.
>  
>
>
>
> -- 
> oliver 
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6f3ff58d-43dc-450e-abf8-27ffcacaa2c1%40googlegroups.com.

Re: LTS baseline selection for the successor of 2.222

[Oliver Gondža]

After the discussion on the Governance Meeting, we agreed to go for 
2.235 as a next LTS baseline. 2.235.1 is expected to be out six weeks 
from now.


On 29/04/2020 18.36, Mark Waite wrote:
+1 from me for 2.235, particularly with the additional UI improvements 
in recent releases.


Also assuming that there will be *lots of help testing the release 
candidate* once it is delivered . ☺ ☺ ☺


On Wed, Apr 29, 2020 at 9:59 AM Oleg Nenashev > wrote:


+1 for 2.235, assuming that we are conservative about merges this week.

On Wednesday, April 29, 2020 at 5:47:41 PM UTC+2, Tim Jacomb wrote:

2.235 would also be my preference, I've got 2 (hopefully) last
system read PRs, I would love to get in before the LTS

On Wed, 29 Apr 2020 at 14:54, Daniel Beck  wrote:



 > On 29. Apr 2020, at 12:44, Oliver Gondža
 wrote:
 >
 > In accordance we recently approved process changes, we
are doing next baseline section two weeks earlier in the cycle.

Assuming nobody merges something crazy into core this week,
I'm for 2.235.

We've moved the baseline decision earlier to give us the
freedom to choose a very recent release without a lot of
risk and overlapping work schedules, since we'll have 4
weeks to identify and fix problems and back port those
fixes. So I propose we try this and see how it goes.

(FWIW we probably want to figure out what to do about
JENKINS-61937 before the new LTS lands…)

-- 
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 jenkin...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/900CA800-A7CB-486B-B49A-93DF05F30CB8%40beckweb.net.

-- 
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-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/c34d0118-503e-42e3-b6e3-e57384621cf0%40googlegroups.com

.

--
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-dev+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHCpxgwu3qjVa1RVhn_x44jYhBniu3dOzOPsZZ3SUQJ0A%40mail.gmail.com 
.



--
oliver

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7f972e87-d22b-f5b0-36e9-3c364e56ab49%40gmail.com.

Re: LTS baseline selection for the successor of 2.222

[Mark Waite]

+1 from me for 2.235, particularly with the additional UI improvements in
recent releases.

Also assuming that there will be *lots of help testing the release
candidate* once it is delivered . ☺ ☺ ☺

On Wed, Apr 29, 2020 at 9:59 AM Oleg Nenashev 
wrote:

> +1 for 2.235, assuming that we are conservative about merges this week.
>
> On Wednesday, April 29, 2020 at 5:47:41 PM UTC+2, Tim Jacomb wrote:
>>
>> 2.235 would also be my preference, I've got 2 (hopefully) last system
>> read PRs, I would love to get in before the LTS
>>
>> On Wed, 29 Apr 2020 at 14:54, Daniel Beck  wrote:
>>
>>>
>>>
>>> > On 29. Apr 2020, at 12:44, Oliver Gondža  wrote:
>>> >
>>> > In accordance we recently approved process changes, we are doing next
>>> baseline section two weeks earlier in the cycle.
>>>
>>> Assuming nobody merges something crazy into core this week, I'm for
>>> 2.235.
>>>
>>> We've moved the baseline decision earlier to give us the freedom to
>>> choose a very recent release without a lot of risk and overlapping work
>>> schedules, since we'll have 4 weeks to identify and fix problems and back
>>> port those fixes. So I propose we try this and see how it goes.
>>>
>>> (FWIW we probably want to figure out what to do about JENKINS-61937
>>> before the new LTS lands…)
>>>
>>> --
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/900CA800-A7CB-486B-B49A-93DF05F30CB8%40beckweb.net
>>> .
>>>
>> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/c34d0118-503e-42e3-b6e3-e57384621cf0%40googlegroups.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHCpxgwu3qjVa1RVhn_x44jYhBniu3dOzOPsZZ3SUQJ0A%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.222

[Oleg Nenashev]

+1 for 2.235, assuming that we are conservative about merges this week.

On Wednesday, April 29, 2020 at 5:47:41 PM UTC+2, Tim Jacomb wrote:
>
> 2.235 would also be my preference, I've got 2 (hopefully) last system read 
> PRs, I would love to get in before the LTS
>
> On Wed, 29 Apr 2020 at 14:54, Daniel Beck > 
> wrote:
>
>>
>>
>> > On 29. Apr 2020, at 12:44, Oliver Gondža > > wrote:
>> > 
>> > In accordance we recently approved process changes, we are doing next 
>> baseline section two weeks earlier in the cycle. 
>>
>> Assuming nobody merges something crazy into core this week, I'm for 2.235.
>>
>> We've moved the baseline decision earlier to give us the freedom to 
>> choose a very recent release without a lot of risk and overlapping work 
>> schedules, since we'll have 4 weeks to identify and fix problems and back 
>> port those fixes. So I propose we try this and see how it goes.
>>
>> (FWIW we probably want to figure out what to do about JENKINS-61937 
>> before the new LTS lands…)
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/900CA800-A7CB-486B-B49A-93DF05F30CB8%40beckweb.net
>> .
>>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c34d0118-503e-42e3-b6e3-e57384621cf0%40googlegroups.com.

Re: LTS baseline selection for the successor of 2.222

[Tim Jacomb]

2.235 would also be my preference, I've got 2 (hopefully) last system read
PRs, I would love to get in before the LTS

On Wed, 29 Apr 2020 at 14:54, Daniel Beck  wrote:

>
>
> > On 29. Apr 2020, at 12:44, Oliver Gondža  wrote:
> >
> > In accordance we recently approved process changes, we are doing next
> baseline section two weeks earlier in the cycle.
>
> Assuming nobody merges something crazy into core this week, I'm for 2.235.
>
> We've moved the baseline decision earlier to give us the freedom to choose
> a very recent release without a lot of risk and overlapping work schedules,
> since we'll have 4 weeks to identify and fix problems and back port those
> fixes. So I propose we try this and see how it goes.
>
> (FWIW we probably want to figure out what to do about JENKINS-61937 before
> the new LTS lands…)
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/900CA800-A7CB-486B-B49A-93DF05F30CB8%40beckweb.net
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicEUb9i%2BD_x3FVsN914UumR8mGeKMFd_3%3D0zrAb%2BgrJaQ%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.222

[Daniel Beck]

> On 29. Apr 2020, at 12:44, Oliver Gondža  wrote:
> 
> In accordance we recently approved process changes, we are doing next 
> baseline section two weeks earlier in the cycle. 

Assuming nobody merges something crazy into core this week, I'm for 2.235.

We've moved the baseline decision earlier to give us the freedom to choose a 
very recent release without a lot of risk and overlapping work schedules, since 
we'll have 4 weeks to identify and fix problems and back port those fixes. So I 
propose we try this and see how it goes.

(FWIW we probably want to figure out what to do about JENKINS-61937 before the 
new LTS lands…)

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/900CA800-A7CB-486B-B49A-93DF05F30CB8%40beckweb.net.

Re: LTS baseline selection for the successor of 2.222

[Baptiste Mathus]

I would also vote for 2.234 for the UI improvements that I think the UX SiG
would love to see used more widely and get more feedback about.

Thanks!

On Wed, Apr 29, 2020 at 2:00 PM Tim Jacomb  wrote:

> My preference would be 2.234,
>
> It has the most system read features in it which  would be great to
> announce as part of the next LTS
>
> Also 2.233 has the button re-work which really should make it in imo (and
> 2.234 with the help icon changes)
>
> Thanks
> Tim
>
> On Wed, 29 Apr 2020 at 11:44, Oliver Gondža  wrote:
>
>> In accordance we recently approved process changes, we are doing next
>> baseline section two weeks earlier in the cycle. Let's voice the
>> baseline candidates and concerns so we have the candidate by next
>> Governance meeting at 2020-05-06.
>>
>> My preferable choices would be 2.232 as the next release have introduced
>> 2 known regressions. They are resolved in 2.234 so that would work as a
>> second option, too.
>>
>> https://jenkins.io/changelog/
>> --
>> oliver
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/ef5d8ebf-1812-a451-1c75-d9b7344b430d%40gmail.com
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiciX%2BFfXwFKGLSunK5G%2Bk1tq5VEZsZgGRZiBMFJeK2L-w%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp26_NmDSqSFzid4cqRMaii%2B%2B0RWmAsLSEWmzaHeuVCtew%40mail.gmail.com.

Re: LTS baseline selection for the successor of 2.222

[Tim Jacomb]

My preference would be 2.234,

It has the most system read features in it which  would be great to
announce as part of the next LTS

Also 2.233 has the button re-work which really should make it in imo (and
2.234 with the help icon changes)

Thanks
Tim

On Wed, 29 Apr 2020 at 11:44, Oliver Gondža  wrote:

> In accordance we recently approved process changes, we are doing next
> baseline section two weeks earlier in the cycle. Let's voice the
> baseline candidates and concerns so we have the candidate by next
> Governance meeting at 2020-05-06.
>
> My preferable choices would be 2.232 as the next release have introduced
> 2 known regressions. They are resolved in 2.234 so that would work as a
> second option, too.
>
> https://jenkins.io/changelog/
> --
> oliver
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/ef5d8ebf-1812-a451-1c75-d9b7344b430d%40gmail.com
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiciX%2BFfXwFKGLSunK5G%2Bk1tq5VEZsZgGRZiBMFJeK2L-w%40mail.gmail.com.

LTS baseline selection for the successor of 2.222

[Oliver Gondža]

In accordance we recently approved process changes, we are doing next 
baseline section two weeks earlier in the cycle. Let's voice the 
baseline candidates and concerns so we have the candidate by next 
Governance meeting at 2020-05-06.


My preferable choices would be 2.232 as the next release have introduced 
2 known regressions. They are resolved in 2.234 so that would work as a 
second option, too.


https://jenkins.io/changelog/
--
oliver

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ef5d8ebf-1812-a451-1c75-d9b7344b430d%40gmail.com.

Re: Move the LTS baseline selection to take place 2 weeks earlier in the cycle

[James Nord]

 from me

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d8d52d33-409e-4a1f-9029-492104261465%40googlegroups.com.

Re: Move the LTS baseline selection to take place 2 weeks earlier in the cycle

[Mark Waite]

+1 from me.

On Monday, March 30, 2020 at 4:43:49 AM UTC-6, ogondza wrote:
>
> As agreed on 2.204.* LTS line retrospective[1], I am proposing to adjust 
> LTS schedule so that next LTS baseline will be selected in week 10 when 
> .3 RC is published. It used to be in week 12 when .3 is released. There 
> ware 2 reasons for this: 
>
> - Lately, we slowly shifted towards choosing too new baselines 
> effectively shortening the core soak time. Making the call 2 weeks 
> sooner (no matter how new the core) will create the time buffer for more 
> issues to be discovered and fixed before the LTS is published. 
>
> - Core developers/reviewers tend to be busy testing during RC testing 
> periods and preparing weeklies that are likely to be chosen an LTS 
> baseline (LTS week 10-12). Making the call 2 weeks sooner will prevent 
> the two to overlap. 
>
> Please let us know your thoughts and concerns by the end of the week. 
>
> [1] 
>
> https://docs.google.com/document/d/1NzR1XtkCfk6MDSD1jRq5H-iPSjqKvP-pfUO0b9lVZ9k/edit?disco=JRfN_wA
>  
> [2] https://github.com/jenkins-infra/jenkins.io/pull/3017 
>
> Thanks! 
> -- 
> oliver 
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ee634139-79d0-4131-b37d-f8bf6adec17c%40googlegroups.com.

Re: Move the LTS baseline selection to take place 2 weeks earlier in the cycle

[Antonio Muñiz]

+1 Sounds good to me.

On Mon, 30 Mar 2020 at 12:56, Oleg Nenashev  wrote:

> I am +1. We could definitely try it for the next baseline and to see
> whether it helps
>
> On Monday, March 30, 2020 at 12:43:49 PM UTC+2, ogondza wrote:
>>
>> As agreed on 2.204.* LTS line retrospective[1], I am proposing to adjust
>> LTS schedule so that next LTS baseline will be selected in week 10 when
>> .3 RC is published. It used to be in week 12 when .3 is released. There
>> ware 2 reasons for this:
>>
>> - Lately, we slowly shifted towards choosing too new baselines
>> effectively shortening the core soak time. Making the call 2 weeks
>> sooner (no matter how new the core) will create the time buffer for more
>> issues to be discovered and fixed before the LTS is published.
>>
>> - Core developers/reviewers tend to be busy testing during RC testing
>> periods and preparing weeklies that are likely to be chosen an LTS
>> baseline (LTS week 10-12). Making the call 2 weeks sooner will prevent
>> the two to overlap.
>>
>> Please let us know your thoughts and concerns by the end of the week.
>>
>> [1]
>>
>> https://docs.google.com/document/d/1NzR1XtkCfk6MDSD1jRq5H-iPSjqKvP-pfUO0b9lVZ9k/edit?disco=JRfN_wA
>> [2] https://github.com/jenkins-infra/jenkins.io/pull/3017
>>
>> Thanks!
>> --
>> oliver
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/149fa0f2-8d2e-4de4-812a-163faf7ad2c3%40googlegroups.com
> 
> .
>


-- 
Antonio Muñiz
Human, Engineer
CloudBees, Inc.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzTATxa_E-RH3_f%2BgR%3DvNbh9dsd8Mg7_6Ad%2BnJdOoWPmyQ%40mail.gmail.com.

Re: Move the LTS baseline selection to take place 2 weeks earlier in the cycle

[Oleg Nenashev]

I am +1. We could definitely try it for the next baseline and to see 
whether it helps

On Monday, March 30, 2020 at 12:43:49 PM UTC+2, ogondza wrote:
>
> As agreed on 2.204.* LTS line retrospective[1], I am proposing to adjust 
> LTS schedule so that next LTS baseline will be selected in week 10 when 
> .3 RC is published. It used to be in week 12 when .3 is released. There 
> ware 2 reasons for this: 
>
> - Lately, we slowly shifted towards choosing too new baselines 
> effectively shortening the core soak time. Making the call 2 weeks 
> sooner (no matter how new the core) will create the time buffer for more 
> issues to be discovered and fixed before the LTS is published. 
>
> - Core developers/reviewers tend to be busy testing during RC testing 
> periods and preparing weeklies that are likely to be chosen an LTS 
> baseline (LTS week 10-12). Making the call 2 weeks sooner will prevent 
> the two to overlap. 
>
> Please let us know your thoughts and concerns by the end of the week. 
>
> [1] 
>
> https://docs.google.com/document/d/1NzR1XtkCfk6MDSD1jRq5H-iPSjqKvP-pfUO0b9lVZ9k/edit?disco=JRfN_wA
>  
> [2] https://github.com/jenkins-infra/jenkins.io/pull/3017 
>
> Thanks! 
> -- 
> oliver 
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/149fa0f2-8d2e-4de4-812a-163faf7ad2c3%40googlegroups.com.

Move the LTS baseline selection to take place 2 weeks earlier in the cycle

[Oliver Gondža]

As agreed on 2.204.* LTS line retrospective[1], I am proposing to adjust 
LTS schedule so that next LTS baseline will be selected in week 10 when 
.3 RC is published. It used to be in week 12 when .3 is released. There 
ware 2 reasons for this:


- Lately, we slowly shifted towards choosing too new baselines 
effectively shortening the core soak time. Making the call 2 weeks 
sooner (no matter how new the core) will create the time buffer for more 
issues to be discovered and fixed before the LTS is published.


- Core developers/reviewers tend to be busy testing during RC testing 
periods and preparing weeklies that are likely to be chosen an LTS 
baseline (LTS week 10-12). Making the call 2 weeks sooner will prevent 
the two to overlap.


Please let us know your thoughts and concerns by the end of the week.

[1] 
https://docs.google.com/document/d/1NzR1XtkCfk6MDSD1jRq5H-iPSjqKvP-pfUO0b9lVZ9k/edit?disco=JRfN_wA

[2] https://github.com/jenkins-infra/jenkins.io/pull/3017

Thanks!
--
oliver

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b428a179-b218-7913-6142-a6d086e09169%40gmail.com.

Re: LTS baseline selection

[Oleg Nenashev]

IIUC 2.222 is a winner. If yes/no, could we please officially announce it 
so that parties can start preparing to the RC testing?

search also looks a little funky in my Neo2 theme: https://imgur.com/9UC4jQZ 
> 
> Looks like a minor fix IMHO.
>

Yes, themes might be affected as it was discussed in the PRs. The impact 
should be fairly minor tho.
I also added an entry in the upgrade guideline for that: 
https://github.com/jenkinsci/jenkins/pull/4463

BR, Oleg

On Wednesday, February 26, 2020 at 11:01:25 PM UTC+1, Tobias Gruetzmacher 
wrote:
>
> Hi, 
>
> search also looks a little funky in my Neo2 theme: 
> https://imgur.com/9UC4jQZ 
>
> Looks like a minor fix IMHO. 
>
> On Tue, Feb 25, 2020 at 02:23:28PM +, Tim Jacomb wrote: 
> > That looks like a fairly minor css tweak to fix that, is it just the 
> > search input? I wouldn’t exclude it from LTS for that issue 
> > 
> > On Tue, 25 Feb 2020 at 13:52, Ullrich Hafner  > wrote: 
> > 
> >   While I like the new look, a mix of the new UI and the existing 
> >   material theme looks kind of weird now, even with disabled UI flag. 
> >   There are a lot of changes that are not part of the flag: 
> > 
>
>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a232e692-92b7-40b5-ab26-1049edbe9857%40googlegroups.com.

Re: LTS baseline selection

[Tobias Gruetzmacher]

Hi,

search also looks a little funky in my Neo2 theme: https://imgur.com/9UC4jQZ

Looks like a minor fix IMHO.

On Tue, Feb 25, 2020 at 02:23:28PM +, Tim Jacomb wrote:
> That looks like a fairly minor css tweak to fix that, is it just the
> search input? I wouldn’t exclude it from LTS for that issue
> 
> On Tue, 25 Feb 2020 at 13:52, Ullrich Hafner  wrote:
> 
>   While I like the new look, a mix of the new UI and the existing
>   material theme looks kind of weird now, even with disabled UI flag.
>   There are a lot of changes that are not part of the flag:
> 


-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20200226213748.GA262798%4023.gs.

Re: LTS baseline selection

['Gavin Mogan' via Jenkins Developers]

For the lazy - https://jenkins.io/jep/219
> JEP-223: "Manage" permission for managing non-security aspects of a
Jenkins instance

I also havn't tried 223, but like the slight changes to the new UI, though
it is slightly jarring on very first glance.

On Wed, Feb 26, 2020 at 7:53 AM Tim Jacomb  wrote:

> Yes we have the new header UI enabled, the feedback I got from users was
> they liked it, no negative feedback received.
> JEP-223: No we have no use for it as our instance is fully managed in code
>
> Thanks
> Tim
>
> On Wed, 26 Feb 2020 at 15:04, Baptiste Mathus 
> wrote:
>
>> Curious @Tim:
>> did you also:
>>
>>- enable the new header UI?
>>- enable JEP-223?
>>
>> Thanks!
>>
>>
>> On Wed, Feb 26, 2020 at 11:02 AM Tim Jacomb  wrote:
>>
>>> We've been running 2.222 in production since first thing Monday,
>>>
>>> No issues so far,
>>>
>>> We enabled the global background build discarder, it ran for about 9
>>> hours on the first run and cleared up ~200GB of space,
>>> We're very happy with the disk cleanup feature in 2.221 (thanks DB)
>>>
>>> Thanks
>>> Tim
>>>
>>> On Tue, 25 Feb 2020 at 22:59, Daniel Beck  wrote:
>>>


 > On 25. Feb 2020, at 16:44, Oleg Nenashev 
 wrote:
 >
 > There is also  https://issues.jenkins-ci.org/browse/JENKINS-60409
 which needs to be investigated for the new LTS candidate. Looks like the
 default Jetty behavior changed, and it may impact some users when they
 upgrade to the new baseline

 Irrelevant for this thread, as that issue affects every weekly release
 newer than the current LTS baseline. Might need upgrade docs or an
 expedited fix + back port but that applies to every potential LTS baseline
 choice.

 --
 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-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/7E8CB82D-2A1F-4A02-B42A-2AE0920CD822%40beckweb.net
 .

>>> --
>>> 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieKEt0Jv3RZb19yWmBZNTbyr%2Bmf%2BAmjP1SxeO3XdEvGfA%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp0kF6zx%2BpmR9LCN7XS8iTfi6aS86TGDR3j%3DZMXfRSHzTg%40mail.gmail.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic5ROtC5em5oNQTJYrT4w6BhkZbf2RueUHE-7CyE%2BPLHQ%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duu%3Dq3HxUXAdM9iWyB-Q5ji9VH-Xdc5ZvUKpK%3DEvJSmMNg%40mail.gmail.com.

Re: LTS baseline selection

[Tim Jacomb]

Yes we have the new header UI enabled, the feedback I got from users was
they liked it, no negative feedback received.
JEP-223: No we have no use for it as our instance is fully managed in code

Thanks
Tim

On Wed, 26 Feb 2020 at 15:04, Baptiste Mathus  wrote:

> Curious @Tim:
> did you also:
>
>- enable the new header UI?
>- enable JEP-223?
>
> Thanks!
>
>
> On Wed, Feb 26, 2020 at 11:02 AM Tim Jacomb  wrote:
>
>> We've been running 2.222 in production since first thing Monday,
>>
>> No issues so far,
>>
>> We enabled the global background build discarder, it ran for about 9
>> hours on the first run and cleared up ~200GB of space,
>> We're very happy with the disk cleanup feature in 2.221 (thanks DB)
>>
>> Thanks
>> Tim
>>
>> On Tue, 25 Feb 2020 at 22:59, Daniel Beck  wrote:
>>
>>>
>>>
>>> > On 25. Feb 2020, at 16:44, Oleg Nenashev 
>>> wrote:
>>> >
>>> > There is also  https://issues.jenkins-ci.org/browse/JENKINS-60409
>>> which needs to be investigated for the new LTS candidate. Looks like the
>>> default Jetty behavior changed, and it may impact some users when they
>>> upgrade to the new baseline
>>>
>>> Irrelevant for this thread, as that issue affects every weekly release
>>> newer than the current LTS baseline. Might need upgrade docs or an
>>> expedited fix + back port but that applies to every potential LTS baseline
>>> choice.
>>>
>>> --
>>> 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/7E8CB82D-2A1F-4A02-B42A-2AE0920CD822%40beckweb.net
>>> .
>>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieKEt0Jv3RZb19yWmBZNTbyr%2Bmf%2BAmjP1SxeO3XdEvGfA%40mail.gmail.com
>> 
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp0kF6zx%2BpmR9LCN7XS8iTfi6aS86TGDR3j%3DZMXfRSHzTg%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic5ROtC5em5oNQTJYrT4w6BhkZbf2RueUHE-7CyE%2BPLHQ%40mail.gmail.com.

Re: LTS baseline selection

[Baptiste Mathus]

Curious @Tim:
did you also:

   - enable the new header UI?
   - enable JEP-223?

Thanks!


On Wed, Feb 26, 2020 at 11:02 AM Tim Jacomb  wrote:

> We've been running 2.222 in production since first thing Monday,
>
> No issues so far,
>
> We enabled the global background build discarder, it ran for about 9 hours
> on the first run and cleared up ~200GB of space,
> We're very happy with the disk cleanup feature in 2.221 (thanks DB)
>
> Thanks
> Tim
>
> On Tue, 25 Feb 2020 at 22:59, Daniel Beck  wrote:
>
>>
>>
>> > On 25. Feb 2020, at 16:44, Oleg Nenashev 
>> wrote:
>> >
>> > There is also  https://issues.jenkins-ci.org/browse/JENKINS-60409
>> which needs to be investigated for the new LTS candidate. Looks like the
>> default Jetty behavior changed, and it may impact some users when they
>> upgrade to the new baseline
>>
>> Irrelevant for this thread, as that issue affects every weekly release
>> newer than the current LTS baseline. Might need upgrade docs or an
>> expedited fix + back port but that applies to every potential LTS baseline
>> choice.
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/7E8CB82D-2A1F-4A02-B42A-2AE0920CD822%40beckweb.net
>> .
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieKEt0Jv3RZb19yWmBZNTbyr%2Bmf%2BAmjP1SxeO3XdEvGfA%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp0kF6zx%2BpmR9LCN7XS8iTfi6aS86TGDR3j%3DZMXfRSHzTg%40mail.gmail.com.

Re: LTS baseline selection

[Oliver Gondža]

The have almost unanimous support for 2.222. Since users can opt-out 
from the potentially breaking changes, I do not see a reason why not to 
use it.


On 25/02/2020 13.04, Oleg Nenashev wrote:
Regarding 2.222... I believe there is a lot for interest to get 2.222 in 
the LTS so that plugins could start adapting to the new Systemread and 
Manage permissions earlier. There is a lot of experimental features and 
new APIs included there, and I believe it would be valuable for the 
Jenkins community if this release was selected as an LTS baseline. At 
the same time, I admit that the release has not been battle tested for long.


Some notes:

  * 2.222 was released this Sunday, and the release metrics are yet to
be seen.
  o The community rating is 19 positives and 2 "I had to rollback"
  o There is no issues reported to this release in Jira or in social
media
  o There is one negative feedback in the UX SIG Gitter
 about the header size in
the default UI. The header went from 68px to 96px (thanks
Wadeck) and caused some feedback about mispositioned controls
and impact on muscle memory by Rocky Breslow. I consider it as
an important feedback, but AFAICT we can optimize the header
size and backport the change if needed
  * 2.221 has a flawless community rating (31 positive), there is no
regressions reported
  o JENKINS-61121
 will need
to be backported if we chose this release
  * Issues in both releases
  o There is a JENKINS-61197
 regression
which impacts custom workspaces in the root directory (or
Windows drive label). I am working on a fix, it should be
backportable

My personal preference would be to go with 2.222 unless there are major 
issues discovered there by the RC date. In order to make it happen, we 
should at least process the UX report with the header. I deployed 2.222 
on my local setup, and it looks good with the default setting and with 
Manage and SystemRead permissions enabled. Experimental Web UI works as 
well, but I reverted to the classic one.


BR, Oleg


On Tuesday, February 25, 2020 at 11:39:35 AM UTC+1, Baptiste Mathus wrote:



On Tue, Feb 25, 2020 at 12:33 AM Jesse Glick > wrote:

On Mon, Feb 24, 2020 at 4:37 PM Oliver Gondža > wrote:
 > the baseline candidates

Reference: https://jenkins.io/changelog/

 > in advance to speed up the discussion in governance meeting.

Are baselines still selected during governance meetings? I thought
that had switched to the list.


I /think/ the discussion happens here a lot, but the final /stamp/
after the trend/discussion/decision here is still done during gov
meeting (still makes sense IMO).



-- 
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 jenkin...@googlegroups.com .
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1C4wg1EiT18OuyG3Mi3WeZspgwtUuqpME2L_7P-O%2B_CQ%40mail.gmail.com

.

--
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-dev+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a98cbee5-e2b9-4164-be01-7f7c5c2ddbfe%40googlegroups.com 
.



--
oliver

--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3b262486-7cdf-d6ef-cc04-12b68df74230%40gmail.com.

Re: LTS baseline selection

[Tim Jacomb]

We've been running 2.222 in production since first thing Monday,

No issues so far,

We enabled the global background build discarder, it ran for about 9 hours
on the first run and cleared up ~200GB of space,
We're very happy with the disk cleanup feature in 2.221 (thanks DB)

Thanks
Tim

On Tue, 25 Feb 2020 at 22:59, Daniel Beck  wrote:

>
>
> > On 25. Feb 2020, at 16:44, Oleg Nenashev  wrote:
> >
> > There is also  https://issues.jenkins-ci.org/browse/JENKINS-60409 which
> needs to be investigated for the new LTS candidate. Looks like the default
> Jetty behavior changed, and it may impact some users when they upgrade to
> the new baseline
>
> Irrelevant for this thread, as that issue affects every weekly release
> newer than the current LTS baseline. Might need upgrade docs or an
> expedited fix + back port but that applies to every potential LTS baseline
> choice.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/7E8CB82D-2A1F-4A02-B42A-2AE0920CD822%40beckweb.net
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieKEt0Jv3RZb19yWmBZNTbyr%2Bmf%2BAmjP1SxeO3XdEvGfA%40mail.gmail.com.

Re: LTS baseline selection

[Daniel Beck]

> On 25. Feb 2020, at 16:44, Oleg Nenashev  wrote:
> 
> There is also  https://issues.jenkins-ci.org/browse/JENKINS-60409 which needs 
> to be investigated for the new LTS candidate. Looks like the default Jetty 
> behavior changed, and it may impact some users when they upgrade to the new 
> baseline

Irrelevant for this thread, as that issue affects every weekly release newer 
than the current LTS baseline. Might need upgrade docs or an expedited fix + 
back port but that applies to every potential LTS baseline choice.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7E8CB82D-2A1F-4A02-B42A-2AE0920CD822%40beckweb.net.

Re: LTS baseline selection

[Oleg Nenashev]

There is also  https://issues.jenkins-ci.org/browse/JENKINS-60409 which
needs to be investigated for the new LTS candidate. Looks like the default
Jetty behavior changed, and it may impact some users when they upgrade to
the new baseline


On Tue, Feb 25, 2020 at 3:23 PM Tim Jacomb  wrote:

> That looks like a fairly minor css tweak to fix that, is it just the
> search input? I wouldn’t exclude it from LTS for that issue
>
> On Tue, 25 Feb 2020 at 13:52, Ullrich Hafner 
> wrote:
>
>> While I like the new look, a mix of the new UI and the existing material
>> theme looks kind of weird now, even with disabled UI flag. There are a lot
>> of changes that are not part of the flag:
>>
>> Jenkins 2.222 (new UI disabled):
>>
>>
>>
>> Jenkins LTS:
>>
>>
>>
>>
>> Am 25.02.2020 um 14:39 schrieb Oleg Nenashev :
>>
>> Hi Ulli,
>>
>> The new frontend styling is behind the feature flag. By default there is
>> only a change in the Jenkins header which should not impact the plugin
>> developers except few ones who extend breadcrumbs or customize login/search
>> controls. I believe that only few plugin maintainers would be affected
>> there. Theme developers are a different story, and indeed there is likely
>> to be an impact on them. AFAIK Felix did some experiments with Material
>> Design Themes tho, and they worked pretty well out-of-the-box
>>
>> BR, Oleg
>>
>>
>>
>> On Tuesday, February 25, 2020 at 2:29:42 PM UTC+1, Ullrich Hafner wrote:
>>>
>>>
>>>-
>>>2.222 was released this Sunday, and the release metrics are yet to
>>>be seen.
>>>   - The community rating is 19 positives and 2 "I had to rollback"
>>>   - There is no issues reported to this release in Jira or in
>>>   social media
>>>   - There is one negative feedback in the UX SIG Gitter
>>>    about the header size in the
>>>   default UI. The header went from 68px to 96px (thanks Wadeck) and 
>>> caused
>>>   some feedback about mispositioned controls and impact on muscle memory
>>>   by Rocky Breslow. I consider it as an important feedback, but AFAICT 
>>> we can
>>>   optimize the header size and backport the change if needed
>>>
>>>
>>> I think we should give theme authors (and maybe plugin developers) more
>>> time to update their plugins to the new styling. Otherwise the new UI
>>> improvements might look like a step backward rather than a step forward.
>>> Then we also have the chance to provide some more UI enhancements in other
>>> areas so that the overall appearance looks consistent.
>>>
>>>
>>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/2b66fcbd-3b15-4fea-8d39-9beeb11f5a8f%40googlegroups.com
>> 
>> .
>>
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/64C2E3C8-CA2D-4C36-BFAF-9889BA1EA634%40gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/VRxRCP_IKhQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieW76tV_2%3DqvwAJy7BpnaFzCZ6Mucoi7KGCY-JLefqABQ%40mail.gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDL24k1B_tCJ9wN6e%2Bx3EW_DeNdMVXA9mFCZuExB3KmCA%40mail.gmail.com.

Re: LTS baseline selection

[Tim Jacomb]

That looks like a fairly minor css tweak to fix that, is it just the search
input? I wouldn’t exclude it from LTS for that issue

On Tue, 25 Feb 2020 at 13:52, Ullrich Hafner 
wrote:

> While I like the new look, a mix of the new UI and the existing material
> theme looks kind of weird now, even with disabled UI flag. There are a lot
> of changes that are not part of the flag:
>
> Jenkins 2.222 (new UI disabled):
>
>
>
> Jenkins LTS:
>
>
>
>
> Am 25.02.2020 um 14:39 schrieb Oleg Nenashev :
>
> Hi Ulli,
>
> The new frontend styling is behind the feature flag. By default there is
> only a change in the Jenkins header which should not impact the plugin
> developers except few ones who extend breadcrumbs or customize login/search
> controls. I believe that only few plugin maintainers would be affected
> there. Theme developers are a different story, and indeed there is likely
> to be an impact on them. AFAIK Felix did some experiments with Material
> Design Themes tho, and they worked pretty well out-of-the-box
>
> BR, Oleg
>
>
>
> On Tuesday, February 25, 2020 at 2:29:42 PM UTC+1, Ullrich Hafner wrote:
>>
>>
>>-
>>2.222 was released this Sunday, and the release metrics are yet to be
>>seen.
>>   - The community rating is 19 positives and 2 "I had to rollback"
>>   - There is no issues reported to this release in Jira or in social
>>   media
>>   - There is one negative feedback in the UX SIG Gitter
>>    about the header size in the
>>   default UI. The header went from 68px to 96px (thanks Wadeck) and 
>> caused
>>   some feedback about mispositioned controls and impact on muscle memory
>>   by Rocky Breslow. I consider it as an important feedback, but AFAICT 
>> we can
>>   optimize the header size and backport the change if needed
>>
>>
>> I think we should give theme authors (and maybe plugin developers) more
>> time to update their plugins to the new styling. Otherwise the new UI
>> improvements might look like a step backward rather than a step forward.
>> Then we also have the chance to provide some more UI enhancements in other
>> areas so that the overall appearance looks consistent.
>>
>>
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/2b66fcbd-3b15-4fea-8d39-9beeb11f5a8f%40googlegroups.com
> 
> .
>
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/64C2E3C8-CA2D-4C36-BFAF-9889BA1EA634%40gmail.com
> 
> .
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieW76tV_2%3DqvwAJy7BpnaFzCZ6Mucoi7KGCY-JLefqABQ%40mail.gmail.com.

Re: LTS baseline selection

[Ullrich Hafner]

While I like the new look, a mix of the new UI and the existing material theme 
looks kind of weird now, even with disabled UI flag. There are a lot of changes 
that are not part of the flag:

Jenkins 2.222 (new UI disabled):



Jenkins LTS:




> Am 25.02.2020 um 14:39 schrieb Oleg Nenashev :
> 
> Hi Ulli,
> 
> The new frontend styling is behind the feature flag. By default there is only 
> a change in the Jenkins header which should not impact the plugin developers 
> except few ones who extend breadcrumbs or customize login/search controls. I 
> believe that only few plugin maintainers would be affected there. Theme 
> developers are a different story, and indeed there is likely to be an impact 
> on them. AFAIK Felix did some experiments with Material Design Themes tho, 
> and they worked pretty well out-of-the-box
> 
> BR, Oleg
> 
> 
> 
> On Tuesday, February 25, 2020 at 2:29:42 PM UTC+1, Ullrich Hafner wrote:
>> 
>> 2.222 was released this Sunday, and the release metrics are yet to be seen. 
>> The community rating is 19 positives and 2 "I had to rollback"
>> There is no issues reported to this release in Jira or in social media
>> There is one negative feedback in the UX SIG Gitter 
>>  about the header size in the default 
>> UI. The header went from 68px to 96px (thanks Wadeck) and caused some 
>> feedback about mispositioned controls and impact on muscle memory by Rocky 
>> Breslow. I consider it as an important feedback, but AFAICT we can optimize 
>> the header size and backport the change if needed
> 
> I think we should give theme authors (and maybe plugin developers) more time 
> to update their plugins to the new styling. Otherwise the new UI improvements 
> might look like a step backward rather than a step forward. Then we also have 
> the chance to provide some more UI enhancements in other areas so that the 
> overall appearance looks consistent.  
> 
> 
> 
> -- 
> 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-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/2b66fcbd-3b15-4fea-8d39-9beeb11f5a8f%40googlegroups.com
>  
> .

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/64C2E3C8-CA2D-4C36-BFAF-9889BA1EA634%40gmail.com.

Re: LTS baseline selection

[Oleg Nenashev]

Hi Ulli,

The new frontend styling is behind the feature flag. By default there is 
only a change in the Jenkins header which should not impact the plugin 
developers except few ones who extend breadcrumbs or customize login/search 
controls. I believe that only few plugin maintainers would be affected 
there. Theme developers are a different story, and indeed there is likely 
to be an impact on them. AFAIK Felix did some experiments with Material 
Design Themes tho, and they worked pretty well out-of-the-box

BR, Oleg



On Tuesday, February 25, 2020 at 2:29:42 PM UTC+1, Ullrich Hafner wrote:
>
>
>- 
>2.222 was released this Sunday, and the release metrics are yet to be 
>seen. 
>   - The community rating is 19 positives and 2 "I had to rollback"
>   - There is no issues reported to this release in Jira or in social 
>   media
>   - There is one negative feedback in the UX SIG Gitter 
>    about the header size in the 
>   default UI. The header went from 68px to 96px (thanks Wadeck) and 
> caused 
>   some feedback about mispositioned controls and impact on muscle memory 
>   by Rocky Breslow. I consider it as an important feedback, but AFAICT we 
> can 
>   optimize the header size and backport the change if needed
>
>
> I think we should give theme authors (and maybe plugin developers) more 
> time to update their plugins to the new styling. Otherwise the new UI 
> improvements might look like a step backward rather than a step forward. 
> Then we also have the chance to provide some more UI enhancements in other 
> areas so that the overall appearance looks consistent.  
>
>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2b66fcbd-3b15-4fea-8d39-9beeb11f5a8f%40googlegroups.com.

Re: LTS baseline selection

[Ullrich Hafner]

> 
> 2.222 was released this Sunday, and the release metrics are yet to be seen. 
> The community rating is 19 positives and 2 "I had to rollback"
> There is no issues reported to this release in Jira or in social media
> There is one negative feedback in the UX SIG Gitter 
>  about the header size in the default UI. 
> The header went from 68px to 96px (thanks Wadeck) and caused some feedback 
> about mispositioned controls and impact on muscle memory by Rocky Breslow. I 
> consider it as an important feedback, but AFAICT we can optimize the header 
> size and backport the change if needed

I think we should give theme authors (and maybe plugin developers) more time to 
update their plugins to the new styling. Otherwise the new UI improvements 
might look like a step backward rather than a step forward. Then we also have 
the chance to provide some more UI enhancements in other areas so that the 
overall appearance looks consistent.  


-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/D339AB58-0DF1-4848-9C0D-AEDAE695107F%40gmail.com.

Re: LTS baseline selection

[Oleg Nenashev]

Regarding 2.222... I believe there is a lot for interest to get 2.222 in 
the LTS so that plugins could start adapting to the new Systemread and 
Manage permissions earlier. There is a lot of experimental features and new 
APIs included there, and I believe it would be valuable for the Jenkins 
community if this release was selected as an LTS baseline. At the same 
time, I admit that the release has not been battle tested for long.

Some notes:

   - 2.222 was released this Sunday, and the release metrics are yet to be 
   seen. 
  - The community rating is 19 positives and 2 "I had to rollback"
  - There is no issues reported to this release in Jira or in social 
  media
  - There is one negative feedback in the UX SIG Gitter 
   about the header size in the 
  default UI. The header went from 68px to 96px (thanks Wadeck) and caused 
  some feedback about mispositioned controls and impact on muscle memory 
  by Rocky Breslow. I consider it as an important feedback, but AFAICT we 
can 
  optimize the header size and backport the change if needed
   - 2.221 has a flawless community rating (31 positive), there is no 
   regressions reported
  - JENKINS-61121  will 
  need to be backported if we chose this release
  - Issues in both releases
  - There is a JENKINS-61197 
   regression which 
  impacts custom workspaces in the root directory (or Windows drive label). 
I 
  am working on a fix, it should be backportable
   
My personal preference would be to go with 2.222 unless there are major 
issues discovered there by the RC date. In order to make it happen, we 
should at least process the UX report with the header. I deployed 2.222 on 
my local setup, and it looks good with the default setting and with Manage 
and SystemRead permissions enabled. Experimental Web UI works as well, but 
I reverted to the classic one. 

BR, Oleg


On Tuesday, February 25, 2020 at 11:39:35 AM UTC+1, Baptiste Mathus wrote:
>
>
>
> On Tue, Feb 25, 2020 at 12:33 AM Jesse Glick  > wrote:
>
>> On Mon, Feb 24, 2020 at 4:37 PM Oliver Gondža > > wrote:
>> > the baseline candidates
>>
>> Reference: https://jenkins.io/changelog/
>>
>> > in advance to speed up the discussion in governance meeting.
>>
>> Are baselines still selected during governance meetings? I thought
>> that had switched to the list.
>>
>
> I *think* the discussion happens here a lot, but the final /stamp/ after 
> the trend/discussion/decision here is still done during gov meeting (still 
> makes sense IMO).
>
>
>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1C4wg1EiT18OuyG3Mi3WeZspgwtUuqpME2L_7P-O%2B_CQ%40mail.gmail.com
>> .
>>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a98cbee5-e2b9-4164-be01-7f7c5c2ddbfe%40googlegroups.com.