Re: Proposal: "Friend Of Jenkins" Revamp

[Oleg Nenashev]

Hi Zbynek! I was also thinking about a badges-alike approach in the future.
The Linux Foundation supports open badges on its platform, and we could
somehow get access to it. E.g. I have a badge for speaking at cdCon
there... IIUC it is based on https://info.credly.com/ .

We could definitely explore it more if someone is interested. Badges for
financial donations are probably not the biggest use-case though.

Best regards,
Oleg Nenashev

On Wed, May 12, 2021 at 1:29 AM Zbynek Konecny  wrote:

> Hi,
>
> > recognizing donations through Jenkins social media
>
> sounds like a better approach than having a plugin. If there is a need to
> go beyond social media endorsements and invest time in a technical
> solution, I think instead of having some 2.0 version of the plugin one
> should look into the Open Badges standard and maybe issue different badges
> for financial support / coding / reviews / translations (see
> https://en.wikipedia.org/wiki/Mozilla_Open_Badges ). AFAIK such badges
> can be exported to LinkedIn and may get some attention there.
>
> Best regards,
> Zbynek
>
>
> On Tue, May 11, 2021 at 12:31 PM Oleg Nenashev 
> wrote:
>
>> > Honestly I'm not even sure it's worth spending the time to upgrade the
>> plugin. It just adds a low res icon and a link. I vote for discontinuing
>> the non distributed plugin.
>>
>> There are some merits in the icon/link: pointing end users of Jenkins to
>> https://www.jenkins.io/participate/ . It **might** help to get more
>> visitors of this page and, hopefully, new contributors.
>> We could also discontinue the plugin and just include the functionality
>> into the Jenkins core. Should not be a big deal as long as it's opt-in in
>> appearance.
>>
>> BR, Oleg
>>
>> On Tuesday, May 11, 2021 at 3:19:21 AM UTC+2 ga...@gavinmogan.com wrote:
>>
>>> Honestly I'm not even sure it's worth spending the time to upgrade the
>>> plugin. It just adds a low res icon and a link. I vote for discontinuing
>>> the non distributed plugin.
>>>
>>> On Mon., May 10, 2021, 11:34 a.m. Mark Waite, 
>>> wrote:
>>>
 +1 from me on the proposal as well

 On Monday, May 10, 2021 at 5:20:02 AM UTC-6 timja...@gmail.com wrote:

> +1 to proposal
>
> On Mon, 10 May 2021 at 11:08, Oleg Nenashev 
> wrote:
>
>> Would appreciate any feedback in this thread from the community
>>
>> On Wednesday, May 5, 2021 at 9:58:50 AM UTC+2 Oleg Nenashev wrote:
>>
>>> Dear all,
>>>
>>> We’ve recently had a few discussions with the board and Daniel Beck
>>> about the “Friend of Jenkins” plugin. This is a plugin referenced from
>>> https://www.jenkins.io/donate: *“In showing our appreciation, we’ll
>>> send out a special "friend of Jenkins" plugin to those who have donated 
>>> at
>>> least 25 USD / 25 EUR. This plugin adds a little icon in the footer
>>> section, telling that you are a friend of Jenkins. You can install this 
>>> to
>>> your Jenkins to show off that you’ve helped us”*. De facto, we have
>>> not been doing so in the recent years. There are a few problems 
>>> associated
>>> with the plugin.
>>>
>>> *First of all*, you can become a “Friend of Jenkins” only by
>>> donating money. IMO it goes against open source values, we should 
>>> equally
>>> appreciate all kinds of contributions and avoid promoting money 
>>> donations
>>> specifically. *Secondly*, the plugin is private source at the
>>> moment. It is weird to send a private source plugin to anyone, 
>>> especially
>>> as appreciation. *Thirdly*, the plugin is dated. It has not been
>>> updated for a while, and it does not use modern build/test pipelines. 
>>> For
>>> example the code still targets Jenkins 1.396 as the build target. Even 
>>> if
>>> the code is tiny, it is not good to send such a questionable build to
>>> Jenkins users and suggest its installation. *Last but not least*,
>>> sending private builds in email is flawed on its own due to the risk of
>>> various social engineering attacks.
>>>
>>> I suggest that we completely tear down the “Friend of Jenkins”
>>> program:
>>>
>>>- We remove sections about “Friend of Jenkins” from the
>>>Donations page
>>>- Instead of sending the plugin, the Jenkins Governance Board
>>>will focus on sending appreciation letters and recognizing donations
>>>through Jenkins social media. It should help us to build 
>>> relationships with
>>>donors and hopefully get them involved in the community.
>>>
>>>
>>> Later actions (no specific timeline):
>>>
>>>- We (as community) open source the plugin as the standard
>>>Jenkins plugin on https://github.com/jenkinsci, update it to the
>>>modern development pipelines.
>>>- We update the plugin to reference
>>>https://www.jenkins.io/participate/ instead of donations.  We

Re: Proposal: "Friend Of Jenkins" Revamp

[Zbynek Konecny]

Hi,

> recognizing donations through Jenkins social media

sounds like a better approach than having a plugin. If there is a need to
go beyond social media endorsements and invest time in a technical
solution, I think instead of having some 2.0 version of the plugin one
should look into the Open Badges standard and maybe issue different badges
for financial support / coding / reviews / translations (see
https://en.wikipedia.org/wiki/Mozilla_Open_Badges ). AFAIK such badges can
be exported to LinkedIn and may get some attention there.

Best regards,
Zbynek


On Tue, May 11, 2021 at 12:31 PM Oleg Nenashev 
wrote:

> > Honestly I'm not even sure it's worth spending the time to upgrade the
> plugin. It just adds a low res icon and a link. I vote for discontinuing
> the non distributed plugin.
>
> There are some merits in the icon/link: pointing end users of Jenkins to
> https://www.jenkins.io/participate/ . It **might** help to get more
> visitors of this page and, hopefully, new contributors.
> We could also discontinue the plugin and just include the functionality
> into the Jenkins core. Should not be a big deal as long as it's opt-in in
> appearance.
>
> BR, Oleg
>
> On Tuesday, May 11, 2021 at 3:19:21 AM UTC+2 ga...@gavinmogan.com wrote:
>
>> Honestly I'm not even sure it's worth spending the time to upgrade the
>> plugin. It just adds a low res icon and a link. I vote for discontinuing
>> the non distributed plugin.
>>
>> On Mon., May 10, 2021, 11:34 a.m. Mark Waite, 
>> wrote:
>>
>>> +1 from me on the proposal as well
>>>
>>> On Monday, May 10, 2021 at 5:20:02 AM UTC-6 timja...@gmail.com wrote:
>>>
 +1 to proposal

 On Mon, 10 May 2021 at 11:08, Oleg Nenashev 
 wrote:

> Would appreciate any feedback in this thread from the community
>
> On Wednesday, May 5, 2021 at 9:58:50 AM UTC+2 Oleg Nenashev wrote:
>
>> Dear all,
>>
>> We’ve recently had a few discussions with the board and Daniel Beck
>> about the “Friend of Jenkins” plugin. This is a plugin referenced from
>> https://www.jenkins.io/donate: *“In showing our appreciation, we’ll
>> send out a special "friend of Jenkins" plugin to those who have donated 
>> at
>> least 25 USD / 25 EUR. This plugin adds a little icon in the footer
>> section, telling that you are a friend of Jenkins. You can install this 
>> to
>> your Jenkins to show off that you’ve helped us”*. De facto, we have
>> not been doing so in the recent years. There are a few problems 
>> associated
>> with the plugin.
>>
>> *First of all*, you can become a “Friend of Jenkins” only by
>> donating money. IMO it goes against open source values, we should equally
>> appreciate all kinds of contributions and avoid promoting money donations
>> specifically. *Secondly*, the plugin is private source at the
>> moment. It is weird to send a private source plugin to anyone, especially
>> as appreciation. *Thirdly*, the plugin is dated. It has not been
>> updated for a while, and it does not use modern build/test pipelines. For
>> example the code still targets Jenkins 1.396 as the build target. Even if
>> the code is tiny, it is not good to send such a questionable build to
>> Jenkins users and suggest its installation. *Last but not least*,
>> sending private builds in email is flawed on its own due to the risk of
>> various social engineering attacks.
>>
>> I suggest that we completely tear down the “Friend of Jenkins”
>> program:
>>
>>- We remove sections about “Friend of Jenkins” from the Donations
>>page
>>- Instead of sending the plugin, the Jenkins Governance Board
>>will focus on sending appreciation letters and recognizing donations
>>through Jenkins social media. It should help us to build 
>> relationships with
>>donors and hopefully get them involved in the community.
>>
>>
>> Later actions (no specific timeline):
>>
>>- We (as community) open source the plugin as the standard
>>Jenkins plugin on https://github.com/jenkinsci, update it to the
>>modern development pipelines.
>>- We update the plugin to reference
>>https://www.jenkins.io/participate/ instead of donations.  We
>>might add “Donate” as a type of participation to the list
>>- We release the plugin as 2.0, without changing the artifact ID.
>>Any user of the older private source version, if any, will be able to
>>update via the update center. Any Jenkins user will be also able to 
>> install
>>it via the plugin manager, no preconditions.
>>- We reference the plugin from the install wizard suggestions
>>(not installed by default), and other places.
>>
>> There were also some discussions about building signed versions of
>> the plugin and somehow allowing to verify the “Friend of Jenkins” status.

Re: CDF Technical Oversight Committee - Jenkins project representative nominations

[Oleg Nenashev]

Hi all,

Just in case anyone is interested, here is a draft of my public statement 
as a CDF TOC 
candidate: 
https://docs.google.com/document/d/11yuwAYyq0bCXzLTyoUhood2Y7cIIQzcvR8hvOTazg_A/edit?usp=sharing
 
. I will appreciate any feedback!

Initial version for review (see the Google Doc for latest):

*I am humbled and grateful to be nominated for the CDF TOC by the Jenkins 
community! I have been an active contributor to the project since 2012. I 
am a Jenkins core maintainer, governance board member, and an acting events 
officer. I’ve contributed to many community programs, including open 
governance, public roadmap, Jenkins Enhancement Proposals, and Jenkins 
graduation in CDF. I regularly participate in the CDF TOC meetings as 
Jenkins representative. I am a CDF community ambassador, and help to 
organize events and outreach programs like GSoC. I also contribute to the 
Free and Open Source Silicon Foundation where I work on open hardware CI 
and evangelism. I am a principal engineer in the Community Team at 
CloudBees. This role allows me to dedicate time to drive many initiatives 
in the Jenkins project and the foundations.*
*If elected to the CDF TOC, my main priority will be to coordinate 
technical programs within the CDF. I plan to help CDF projects improve 
their community and governance processes so that they could improve and 
graduate in the CDF. Another priority will be interoperability between 
projects so that the CDF end users can easily combine them for their 
software delivery needs. I will work with the CDF special interest groups 
to define a public technical roadmap for the CDF initiatives, including but 
not limited to interoperability and security. I will also facilitate 
collaboration between the CDF, member companies, end users, and other open 
software and hardware foundations, i.e Linux Foundation, Cloud Native 
Computing Foundation (CNCF), Open Source Security Foundation (OpenSSF), 
RISC-V Foundation, CHIPS Alliance, etc.*

Best regards,
Oleg Nenashev


On Thursday, May 6, 2021 at 6:43:05 AM UTC+2 Oleg Nenashev wrote:

> Dear all,
>
> Thanks to everyone who have provided feedback in this thread and in the 
> governance board channels. We have discussed the nomination at the 
> governance meeting yesterday. There was only one candidate nominated: Oleg 
> Nenashev (yes, me), and we decided no not extend the candidate search 
> beyond the announced nominations deadline. Oleg Nenashev is nominated to 
> the CDF TOC Representative role from the Jenkins project.
>
> Approvers at the governance meeting: Ulli Hafner, Gavin Mogan, Ewelina 
> Wilkosz, Daniel Beck, Baptiste Mathus, Mark Waite
>
> Best regards,
> Oleg Nenashev
>
> On Monday, May 3, 2021 at 10:31:13 PM UTC+2 Oleg Nenashev wrote:
>
>> > Having more motivative contributors is crucial for the community. 
>> Sharing your routine or stories to us might be a good way to let those who 
>> is interested in the community contribution even leading. If there’s any 
>> chances I’d like to take some responsibility.
>>
>> Thanks, it is much appreciated. Just FYI, there is a pending proposal to 
>> the board about making our governance activities more open and shareable 
>> with others. Likely it will be an additional GitHub Repo with Issues for 
>> initiatives/backlog + more frequent roadmap updates. It should help other 
>> contributors to pick up tasks including the CDF related ones. We need to 
>> reduce the bus factor and let others to be involved.
>>
>> > Like you said, getting support from the employer is quite important.
>>
>> Yes, I confirmed with my manager that I will be able to dedicate some 
>> working time to the CDF TOC representation. CloudBees is a very active 
>> participant in the Jenkins community and the CDF as all of us know, and it 
>> is a good opportunity for all parties. 
>>
>> Best regards,
>> Oleg
>>
>> On Monday, May 3, 2021 at 3:41:09 AM UTC+2 Xiaojie Zhao wrote:
>>
>>> Having more motivative contributors is crucial for the community. 
>>> Sharing your routine or stories to us might be a good way to let those who 
>>> is interested in the community contribution even leading. If there’s any 
>>> chances I’d like to take some responsibility.
>>>
>>> Like you said, getting support from the employer is quite important. I’d 
>>> like to say a big thanks for all the companies that support open-source.
>>>
>>> Best regards,
>>> Best
>>>
>>>
>>>
>>>
>>> On 05/3/2021 06:46，Oleg Nenashev wrote： 
>>>
>>> Dear all,
>>>
>>> Thanks a lot for the nomination and feedback! I am really humbled and 
>>> grateful for that, and I appreciate the trust from the community members. I 
>>> am ready to run for the CDF Jenkins representative nomination and for the 
>>> TOC seat. I have been participating in the CDF TOC meetings since May 2020, 
>>> and I have been handling other project representative responsibilities like 
>>> providing project updates and communicating news back to the Jenkins 
>>> community. I would be happy to 

Re: Applying JavaScript and CSS on f:select

[Ullrich Hafner]

Where do you want to use the element? In one of your views? Or in a job 
configuration page?

It is not required to use a f:select. Can’t you directly use the select or what 
is missing in that case (data binding?)?

> Am 10.05.2021 um 11:37 schrieb Daniel Akua :
> 
> Hi all,
> In my plugin I have a  element with the multiple attribute 
> (multi-select) that is changing according to another field.
> My problem is that I want to apply JavaScript and CSS to it to make it look 
> better than the standard multi-select element.
> 
> it currently looks like this:
> 
> 
> and I want it to look something like this:
> 
> 
> I have the required JS and CSS files and it is working on a normal  
> element but not on .
> 
> How do I apply JavaScript and CSS on ?
> Is there some guide on how to do it?
> 
> Tips or links will be appreciated.
> 
> -- 
> 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/5c068520-dace-47bf-beff-5fbdc7392038n%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/F84B061D-9485-40B0-B554-5656B405B615%40gmail.com.

Re: Backporting has started and the RC is scheduled for 19th May

[jn...@cloudbees.com]

https://issues.jenkins.io/browse/JENKINS-65605 for tracking purposes.

KK has been pinged to see if someone can get access, (even if just to 
approve a transfer request).

/James

On Tuesday, May 11, 2021 at 11:05:58 AM UTC+1 timja...@gmail.com wrote:

> The bridge method injector project looks abandoned? We may need to fork it 
> to release a fix 
>
> On Tue, 11 May 2021 at 11:00, jn...@cloudbees.com  
> wrote:
>
>> There are 2 regressions that I know of currently in 2.288,  one is a 
>> blocker and the other possibly so.
>>
>> 1. the `WithBridgeMethods` annotation no longer works and so we would 
>> break compatibility with plugins using bridge methods from core  PR to fix 
>> the injector is 
>> https://github.com/infradna/bridge-method-injector/pull/25 and this will 
>> need a release and a Jenkins PR and then backporting. (will create a Jira 
>> soon)
>>
>> 2. the HTML form submission has broken quite a few tests (could be 
>> HTMLUnit bug, or other but there are a number of plugins now with failing 
>> tests when bumping to this core) 
>> -> https://issues.jenkins.io/browse/JENKINS-65585  , 
>> https://github.com/jenkinsci/jenkins/pull/5405#issuecomment-836265920 
>> and https://github.com/jenkinsci/jenkins/pull/5479
>>
>>
>> /James
>>
>> On Monday, May 10, 2021 at 3:55:22 PM UTC+1 Oleg Nenashev wrote:
>>
>>> Then let's postpone it until .2 at least
>>>
>>> On Mon, May 10, 2021 at 4:44 PM Basil Crow  wrote:
>>>
 On Mon, May 10, 2021 at 2:35 AM Oleg Nenashev  
 wrote:
 >
 > I wonder whether we should also create a Remoting 4.8 backport this 
 time: https://github.com/jenkinsci/remoting/releases/tag/remoting-4.8
 > There are 2 bugfixes which seem important though we could also just 
 embed 4.8 into the LTS line. THere is one performance RFE and one minor 
 feature added, so just backporting the version looks safe enough

 #449 is off-by-default and anyway only applies to the Swarm client
 rather than the Jenkins controller. The other changes, while not
 regression fixes, seem safe to me. I don't feel strongly either way.

 -- 
 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/TPQum9wHFVg/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 
 https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqR22pncxWPsmBq3biGDZZWtHBoN2Bm%2B1qfbv%3DXY1WhEQ%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/c1032e1c-b60b-4780-8d9e-a4fd116f9c36n%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/548b7ee5-8e71-4144-86e0-6265035e85adn%40googlegroups.com.

Re: Proposal: "Friend Of Jenkins" Revamp

[Oleg Nenashev]

> Honestly I'm not even sure it's worth spending the time to upgrade the 
plugin. It just adds a low res icon and a link. I vote for discontinuing 
the non distributed plugin. 

There are some merits in the icon/link: pointing end users of Jenkins to 
https://www.jenkins.io/participate/ . It **might** help to get more 
visitors of this page and, hopefully, new contributors. 
We could also discontinue the plugin and just include the functionality 
into the Jenkins core. Should not be a big deal as long as it's opt-in in 
appearance.

BR, Oleg

On Tuesday, May 11, 2021 at 3:19:21 AM UTC+2 ga...@gavinmogan.com wrote:

> Honestly I'm not even sure it's worth spending the time to upgrade the 
> plugin. It just adds a low res icon and a link. I vote for discontinuing 
> the non distributed plugin.
>
> On Mon., May 10, 2021, 11:34 a.m. Mark Waite,  
> wrote:
>
>> +1 from me on the proposal as well
>>
>> On Monday, May 10, 2021 at 5:20:02 AM UTC-6 timja...@gmail.com wrote:
>>
>>> +1 to proposal
>>>
>>> On Mon, 10 May 2021 at 11:08, Oleg Nenashev  wrote:
>>>
 Would appreciate any feedback in this thread from the community

 On Wednesday, May 5, 2021 at 9:58:50 AM UTC+2 Oleg Nenashev wrote:

> Dear all,
>
> We’ve recently had a few discussions with the board and Daniel Beck 
> about the “Friend of Jenkins” plugin. This is a plugin referenced from 
> https://www.jenkins.io/donate: *“In showing our appreciation, we’ll 
> send out a special "friend of Jenkins" plugin to those who have donated 
> at 
> least 25 USD / 25 EUR. This plugin adds a little icon in the footer 
> section, telling that you are a friend of Jenkins. You can install this 
> to 
> your Jenkins to show off that you’ve helped us”*. De facto, we have 
> not been doing so in the recent years. There are a few problems 
> associated 
> with the plugin.
>
> *First of all*, you can become a “Friend of Jenkins” only by donating 
> money. IMO it goes against open source values, we should equally 
> appreciate 
> all kinds of contributions and avoid promoting money donations 
> specifically. *Secondly*, the plugin is private source at the moment. 
> It is weird to send a private source plugin to anyone, especially as 
> appreciation. *Thirdly*, the plugin is dated. It has not been updated 
> for a while, and it does not use modern build/test pipelines. For example 
> the code still targets Jenkins 1.396 as the build target. Even if the 
> code 
> is tiny, it is not good to send such a questionable build to Jenkins 
> users 
> and suggest its installation. *Last but not least*, sending private 
> builds in email is flawed on its own due to the risk of various social 
> engineering attacks.
>
> I suggest that we completely tear down the “Friend of Jenkins” program:
>
>- We remove sections about “Friend of Jenkins” from the Donations 
>page
>- Instead of sending the plugin, the Jenkins Governance Board will 
>focus on sending appreciation letters and recognizing donations 
> through 
>Jenkins social media. It should help us to build relationships with 
> donors 
>and hopefully get them involved in the community.
>
>
> Later actions (no specific timeline):
>
>- We (as community) open source the plugin as the standard Jenkins 
>plugin on https://github.com/jenkinsci, update it to the modern 
>development pipelines.
>- We update the plugin to reference 
>https://www.jenkins.io/participate/ instead of donations.  We 
>might add “Donate” as a type of participation to the list 
>- We release the plugin as 2.0, without changing the artifact ID. 
>Any user of the older private source version, if any, will be able to 
>update via the update center. Any Jenkins user will be also able to 
> install 
>it via the plugin manager, no preconditions.
>- We reference the plugin from the install wizard suggestions (not 
>installed by default), and other places.
>
> There were also some discussions about building signed versions of the 
> plugin and somehow allowing to verify the “Friend of Jenkins” status. 
> Although I proposed it, now I do not think it is really needed. We can 
> discuss it for future iterations.
>
> Would appreciate any feedback, and I suggest discussing that at the 
> next Governance meeting.
>
> Best regards,
> Oleg Nenashev
> Jenkins Governance Board
>
> -- 
 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 
 

Re: Backporting has started and the RC is scheduled for 19th May

[Tim Jacomb]

The bridge method injector project looks abandoned? We may need to fork it
to release a fix

On Tue, 11 May 2021 at 11:00, jn...@cloudbees.com 
wrote:

> There are 2 regressions that I know of currently in 2.288,  one is a
> blocker and the other possibly so.
>
> 1. the `WithBridgeMethods` annotation no longer works and so we would
> break compatibility with plugins using bridge methods from core  PR to fix
> the injector is https://github.com/infradna/bridge-method-injector/pull/25
> and this will need a release and a Jenkins PR and then backporting. (will
> create a Jira soon)
>
> 2. the HTML form submission has broken quite a few tests (could be
> HTMLUnit bug, or other but there are a number of plugins now with failing
> tests when bumping to this core)
> -> https://issues.jenkins.io/browse/JENKINS-65585  ,
> https://github.com/jenkinsci/jenkins/pull/5405#issuecomment-836265920 and
> https://github.com/jenkinsci/jenkins/pull/5479
>
>
> /James
>
> On Monday, May 10, 2021 at 3:55:22 PM UTC+1 Oleg Nenashev wrote:
>
>> Then let's postpone it until .2 at least
>>
>> On Mon, May 10, 2021 at 4:44 PM Basil Crow  wrote:
>>
>>> On Mon, May 10, 2021 at 2:35 AM Oleg Nenashev 
>>> wrote:
>>> >
>>> > I wonder whether we should also create a Remoting 4.8 backport this
>>> time: https://github.com/jenkinsci/remoting/releases/tag/remoting-4.8
>>> > There are 2 bugfixes which seem important though we could also just
>>> embed 4.8 into the LTS line. THere is one performance RFE and one minor
>>> feature added, so just backporting the version looks safe enough
>>>
>>> #449 is off-by-default and anyway only applies to the Swarm client
>>> rather than the Jenkins controller. The other changes, while not
>>> regression fixes, seem safe to me. I don't feel strongly either way.
>>>
>>> --
>>> 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/TPQum9wHFVg/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
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqR22pncxWPsmBq3biGDZZWtHBoN2Bm%2B1qfbv%3DXY1WhEQ%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/c1032e1c-b60b-4780-8d9e-a4fd116f9c36n%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-3Bie%3DyS8M3rhGWjUEZ3jz%2B4YfFV47Etfxw92tGfV3gRFjqg%40mail.gmail.com.

Re: Backporting has started and the RC is scheduled for 19th May

[jn...@cloudbees.com]

There are 2 regressions that I know of currently in 2.288,  one is a 
blocker and the other possibly so.

1. the `WithBridgeMethods` annotation no longer works and so we would break 
compatibility with plugins using bridge methods from core  PR to fix the 
injector is https://github.com/infradna/bridge-method-injector/pull/25 and 
this will need a release and a Jenkins PR and then backporting. (will 
create a Jira soon)

2. the HTML form submission has broken quite a few tests (could be HTMLUnit 
bug, or other but there are a number of plugins now with failing tests when 
bumping to this core) 
-> https://issues.jenkins.io/browse/JENKINS-65585  
, https://github.com/jenkinsci/jenkins/pull/5405#issuecomment-836265920 
and https://github.com/jenkinsci/jenkins/pull/5479


/James

On Monday, May 10, 2021 at 3:55:22 PM UTC+1 Oleg Nenashev wrote:

> Then let's postpone it until .2 at least
>
> On Mon, May 10, 2021 at 4:44 PM Basil Crow  wrote:
>
>> On Mon, May 10, 2021 at 2:35 AM Oleg Nenashev  
>> wrote:
>> >
>> > I wonder whether we should also create a Remoting 4.8 backport this 
>> time: https://github.com/jenkinsci/remoting/releases/tag/remoting-4.8
>> > There are 2 bugfixes which seem important though we could also just 
>> embed 4.8 into the LTS line. THere is one performance RFE and one minor 
>> feature added, so just backporting the version looks safe enough
>>
>> #449 is off-by-default and anyway only applies to the Swarm client
>> rather than the Jenkins controller. The other changes, while not
>> regression fixes, seem safe to me. I don't feel strongly either way.
>>
>> -- 
>> 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/TPQum9wHFVg/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 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqR22pncxWPsmBq3biGDZZWtHBoN2Bm%2B1qfbv%3DXY1WhEQ%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/c1032e1c-b60b-4780-8d9e-a4fd116f9c36n%40googlegroups.com.