Re: Reimbursement for code signing certificate

On Tue, Apr 18, 2023 at 12:29 PM 'Gavin Mogan' via Jenkins Developers wrote: > I would argue this discussion should happen before the spending not after. FTR, from JEP-15 (at revision b8bfe17), § 3.3.4 ("Reimbursement process"), lines 193-194: > Expenses should be pre-approved through the Jenkin

Re: Reimbursement for code signing certificate

On Tuesday, April 18, 2023 at 1:29:22 PM UTC-6 Gavin wrote: I would argue this discussion should happen before the spending not after. But +1 from me Thanks for the approval. I agree that I made a mistake not asking for the approval before spending the funds. I will do my best to not make

Re: Reimbursement for code signing certificate

+1, of course. On Tuesday, 18 April 2023 at 21:29:22 UTC+2 ga...@gavinmogan.com wrote: > I would argue this discussion should happen before the spending not after. > > But +1 from me > > On Tue, Apr 18, 2023 at 12:04 PM Tim Jacomb wrote: > >> +1 >> >> On Tue, 18 Apr 2023 at 19:32, Basil Crow wr

Re: Reimbursement for code signing certificate

I would argue this discussion should happen before the spending not after. But +1 from me On Tue, Apr 18, 2023 at 12:04 PM Tim Jacomb wrote: > +1 > > On Tue, 18 Apr 2023 at 19:32, Basil Crow wrote: > >> On Tue, Apr 18, 2023 at 11:23 AM 'Gavin Mogan' via Jenkins Developers >> wrote: >> > Shoul

Re: Reimbursement for code signing certificate

On Tue, Apr 18, 2023 at 12:03 PM Tim Jacomb wrote: > > +1 +1 from me as well -- 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...@go

Re: Reimbursement for code signing certificate

+1 On Tue, 18 Apr 2023 at 19:32, Basil Crow wrote: > On Tue, Apr 18, 2023 at 11:23 AM 'Gavin Mogan' via Jenkins Developers > wrote: > > Shouldn't this be submitted via expensify and approved in the board > > mailing list? > > From JEP-15 (at revision b8bfe17), § 3.3.2 ("Use of donations"), line

Re: Reimbursement for code signing certificate

On Tue, Apr 18, 2023 at 11:23 AM 'Gavin Mogan' via Jenkins Developers wrote: > Shouldn't this be submitted via expensify and approved in the board > mailing list? >From JEP-15 (at revision b8bfe17), § 3.3.2 ("Use of donations"), lines 177-178: > Budget requests should be submitted to the develop

Re: Reimbursement for code signing certificate

Shouldn't this be submitted via expensify and approved in the board mailing list? On Tue, Apr 18, 2023 at 11:19 AM Mark Waite wrote: > As part of the code signing certificate renewal process for the Jenkins > MSI installer and the Jenkins WAR file, we spent $1536.00 to purchase the > certificate

Reimbursement for code signing certificate

As part of the code signing certificate renewal process for the Jenkins MSI installer and the Jenkins WAR file, we spent $1536.00 to purchase the certificate. I sent the notice of that purchase in Feb 2023. The charge has now appeared on my credit card and I'd like to be reimbursed. I can pro

Backporting for LTS 2.387.3 has started

Hi everyone, Backporting for 2.387.3 has started, and the RC is scheduled for Wednesday, April 19th, 2023. Candidates: https://issues.jenkins.io/issues/?filter=12146 Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.387.3-fixed Rejected: https://issues.jenkins.io/issues/?jql=label

Re: Release lead for 2.387.3

Hi, I am interested. Best, Kris Get Outlook for iOS From: jenkinsci-dev@googlegroups.com on behalf of Tim Jacomb Sent: Tuesday, April 18, 2023 3:34:04 PM To: Jenkins Developers Subject: Release lead for 2.387.3 Hello Is anyone interes

Release lead for 2.387.3

Hello Is anyone interested in being the release lead for 2.387.3? Planned dates can be seen on the event calendar: https://www.jenkins.io/events/#event-calendar Release candidate by 19th April (apologies for short notice can be a little late if needed) Release on 3rd May The documentation is at: