Re: Plugin Development: Can't add another plugin as dependency

['Gavin Mogan' via Jenkins Developers]

I think it's because you put the dependancy in the dependancy management
section

I think you need a raw dependencies section

https://github.com/jenkinsci/lighthouse-report-plugin/blob/master/pom.xml#L43

Gavin

On Wed., Sep. 22, 2021, 5:22 a.m. t4k30ff, 
wrote:

> Hello,
>
> Since i am new to plugin-development (and Jenkins as well) my
> knowledge is not that great so it would be great if somebody helps me out.
>
> I am programming with eclipse and since i want to track the agents of
> pipeline-builds i need to implement the GraphListener interface in one of
> my classes. In order to do that - at least in my understanding - i need to
> add the workflow-api plugin as a dependency in maven.
> So i did that but neither eclipse nor maven would know the packages. (At
> least i assume this but i can't be shure because nothing is happening).
>
> I already tried things from this tutorial
> 
> (adding the jar manually) but nothing worked so far.
>
> Since i had some complications regarding setting up my eclipse project i
> have the .m2/settings.xml from this tutorial
> . So
> the jar file for the requested dependency is  already on my pc.
>
> So in the end, everytime i do a *mvn compile* i get a *package does not
> exist* and a *cannot find symbol* error.
>
> I attached my GraphListener implementation, pom.xml, settings.xml and a
> debug-log of a *mvn comlie* command if needed.
>
> Thanks for your help
>
>
> --
> 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/e0798036-05a7-48bb-9039-80d05604fd3en%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/CAG%3D_Duty8BAXFojBeZZQSdX%2BVT72sxXwpLDKGoKLCtjVMJtn9w%40mail.gmail.com.

Re: Release team members

[Mark Waite]

I would like to be a member of that group.

On Wed, Sep 22, 2021 at 11:49 PM Tim Jacomb  wrote:

> Hello
>
> Continuing from
> https://groups.google.com/g/jenkinsci-dev/c/YhXRKybGgMg/m/IRjH_VykCwAJ
>
> I would like to invite the previous release leads to join the release team
> officially in jenkinsci/jenkins-infra GitHub organisations:
>
>
>-
>
>Beatriz Muñoz (@bmunozm)
>-
>
>Ildefonso Montero (@imonteroperez)
>-
>
>Mark Waite (@MarkEWaite)
>-
>
>Raihaan Shouhell (@res0nance)
>-
>
>Basil Crow (@basil)
>
>
> Daniel, Olivier (olblak), Wadeck, Oleg you are all in the team in
> jenkins-infra, would you like to join the team in jenkinsci as well?
>
> If you would like to join then please reply to this email.
>
> For others if you would like to get involved in a release then consider
> stepping up for a release lead role for an LTS release or joining the
> #jenkins-release room on Libera IRC
>
> 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-3BieVaZAEP3wJBVzpKe1g5YvjEBcRag49vSJ-Fy8Q2%3DDQCw%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/CAO49JtFtg4-tYwuqB%3DqnA0tvR4MDiL2j%3D_QhaFHtnC8%3DrCmHPQ%40mail.gmail.com.

Re: Emeritus concept for Jenkins developers (was: Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team)

[Matt Sicker]

At Apache, emeritus status is typically requested by the individual.
That might be hard to emulate here if some otherwise emeritus members
of Jenkins aren't here to request emeritus. Some forms of active
versus inactive members could be useful, though, for code review
purposes and other bookkeeping.

On Thu, Sep 23, 2021 at 5:08 AM Tim Jacomb  wrote:
>
> +1 we have this in jenkins-infra
>
> On Thu, 23 Sep 2021 at 10:28, Baptiste Mathus  wrote:
>>
>> Hi all,
>>
>> Following up on Jesse's comment, and as I was reflecting on this a few days 
>> ago: I think we should introduce an Emeritus concept/status for Jenkins core 
>> team's inactive members.
>>
>> That would allow "cleaning up" the list for various reasons, while still 
>> recognizing the contributions of such individuals.
>>
>> I think, akin to Apache does in many projects, we should also have a 
>> straightforward way for such members to be reinstated inthe core list when 
>> they would request it.
>>
>> WDYT?
>>
>> Once we agree on this principle, we will also need to dicuss the "inactive 
>> member" definition, but that's a secondary concern for now IMO.
>>
>> Baptiste
>>
>> Le mer. 22 sept. 2021 à 14:10, wfoll...@cloudbees.com 
>>  a écrit :
>>>
>>> +1 as well, really involved in the community so it's just natural :-)
>>>
>>> On Wednesday, September 22, 2021 at 2:05:32 PM UTC+2 Jesse Glick wrote:

 If he is interested, absolutely +1!

 By the way there are a number of people in 
 https://github.com/orgs/jenkinsci/teams/core/members who are no longer 
 active in the Jenkins community and who should likely be removed.
>>>
>>> --
>>> 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/2735a776-6bdf-485c-bdb0-96d45175ab67n%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/CANWgJS5RcWPCSPghkpyBL3TH8iwv96ogjSbunVBbAdQ0rsTh6A%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-3Bie4XJNJ_WNDmH%3DJsuid4g5w9X%3D%2B8%3DTn3odWs0gZoZLHhQ%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/CACmp6kpV8vE-8C%3D7mAE3DgcAA3O84Fgyqg0CpXUPCq5-CrZxpw%40mail.gmail.com.

Jenkins 2.303.2 LTS RC testing started

[Beatriz Munoz]

Hello everyone,

Latest LTS RC was made public and it is ready to be tested. The final release 
is scheduled for 2021-10-06

Please, report your findings in this thread.

Download the release from 
https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/jenkins-war/2.303.2-SNAPSHOT/jenkins-war-2.303.2-20210923.142442-1.war
 

 

Thanks!


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/8DA50A6A-A546-45A4-8E81-3A9254517631%40cloudbees.com.

Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team

[Oleg Nenashev]

We've got +1s from most of the active Jenkins core maintainers. I went
ahead and added Basil to the Jenkins core team.
Thanks to everyone for the votes!

On Thu, Sep 23, 2021 at 11:08 AM Raihaan Shouhell 
wrote:

> +1 he has been leading the charge on a variety of improvements
>
> On Thu, Sep 23, 2021, 4:25 PM Baptiste Mathus  wrote:
>
>> +1. IMO Basil is wa past the minimum criteria to get this status.
>>
>> Le mer. 22 sept. 2021 à 11:14, Oleg Nenashev  a
>> écrit :
>>
>>> Dear all,
>>>
>>> Basil has been a very active contributor to the Jenkins core since 2020,
>>> and he has contributed a lot to Jenkins over the past several years. He is
>>> an active community member, and he helps a lot with the technical debt
>>> cleanup and code reviews in Jenkins.
>>>
>>> It would be great to have Basil joining the Jenkins core maintainers
>>> team. I propose to officially add Basil to the Jenkins core team. IMHO the
>>> code reviewer stage can be skipped, because he has been already
>>> contributing a lot to the reviews. Opinions/votes?
>>>
>>> References:
>>>
>>>- https://github.com/basil
>>>- Jenkins core maintainers team and ladder:
>>>
>>> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#team
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>> --
>>> 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/0c920f79-f7b7-4299-92d7-15a814821632n%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/CANWgJS55rBhwXNumbJL2rLRa1cc4h%2BpjLgiM00n%2BByBLsxf9fw%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/FpxsrxAgycA/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/CAFoxvgy%3D%3Dx0C6nibxugptU_Mm3p2zaKHNdn%3Dv6%3D7yBpwPDsSOw%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/CAPfivLC4f%2BFvK7N2sTzL0qkPPSNQO%3DPNPPcjBDEsms--8K0SSw%40mail.gmail.com.

Re: Question about extending SCMFileSystem of SCM API

[Goyot, Martin]

Hi Jesse,

Thanks for your answer, so that's what I thought. I was a bit worried
because there was no @NonNull annotation on the method and was wondering
which case it could be.

Thanks !

Le jeu. 23 sept. 2021 à 14:19, Jesse Glick  a écrit :

> Sorry, just noticed today that this never got a reply.
>
> On Fri, Sep 3, 2021 at 11:01 AM Goyot, Martin 
> wrote:
>
>> Which one should I build upon ? Is it the revision or the head ? Or both
>> depending on the context ?
>>
>
> A revision (commit) is more specific than a head (ref) so use a revision
> if present, and ignore the head unless you need it for some auxiliary
> purpose.
>
> I've seen that the revision can be null. In which cases is this possible ?
>>
>
> Do you mean in Builder.build
> ?
> Did you actually *observe* a null parameter, or are just concerned by the
> method specification? I would just return null in such cases unless a use
> case comes up, though you can also retrieve the current head revision. The 
> implementor’s
> guide
> 
>  does
> not seem to discuss `SCMFileSystem.Builder` in detail.
>
> If in doubt, follow the example of `github-branch-source`.
>
> --
> 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/CANfRfr2r_D%3DMiJnTPww9-uL5emHc70TD%3DLs%3D%3D_7%2B6KJqoqbn2g%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/CA%2Bb6JB8eanY%2BsBrKFW90E1s3fc3k0p%3D3iRYyr6tU%3D_GvupHV_A%40mail.gmail.com.

Re: Question about extending SCMFileSystem of SCM API

[Jesse Glick]

Sorry, just noticed today that this never got a reply.

On Fri, Sep 3, 2021 at 11:01 AM Goyot, Martin 
wrote:

> Which one should I build upon ? Is it the revision or the head ? Or both
> depending on the context ?
>

A revision (commit) is more specific than a head (ref) so use a revision if
present, and ignore the head unless you need it for some auxiliary purpose.

I've seen that the revision can be null. In which cases is this possible ?
>

Do you mean in Builder.build
?
Did you actually *observe* a null parameter, or are just concerned by the
method specification? I would just return null in such cases unless a use
case comes up, though you can also retrieve the current head revision.
The implementor’s
guide

does
not seem to discuss `SCMFileSystem.Builder` in detail.

If in doubt, follow the example of `github-branch-source`.

-- 
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/CANfRfr2r_D%3DMiJnTPww9-uL5emHc70TD%3DLs%3D%3D_7%2B6KJqoqbn2g%40mail.gmail.com.

Re: Emeritus concept for Jenkins developers (was: Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team)

[Tim Jacomb]

+1 we have this in jenkins-infra

On Thu, 23 Sep 2021 at 10:28, Baptiste Mathus  wrote:

> Hi all,
>
> Following up on Jesse's comment, and as I was reflecting on this a few
> days ago: I think we should introduce an Emeritus concept/status for
> Jenkins core team's inactive members.
>
> That would allow "cleaning up" the list for various reasons, while still
> recognizing the contributions of such individuals.
>
> I think, akin to Apache does in many projects, we should also have a
> straightforward way for such members to be reinstated inthe core list when
> they would request it.
>
> WDYT?
>
> Once we agree on this principle, we will also need to dicuss the "inactive
> member" definition, but that's a secondary concern for now IMO.
>
> Baptiste
>
> Le mer. 22 sept. 2021 à 14:10, wfoll...@cloudbees.com <
> wfollon...@cloudbees.com> a écrit :
>
>> +1 as well, really involved in the community so it's just natural :-)
>>
>> On Wednesday, September 22, 2021 at 2:05:32 PM UTC+2 Jesse Glick wrote:
>>
>>> If he is interested, absolutely +1!
>>>
>>> By the way there are a number of people in
>>> https://github.com/orgs/jenkinsci/teams/core/members who are no longer
>>> active in the Jenkins community and who should likely be removed.
>>>
>> --
>> 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/2735a776-6bdf-485c-bdb0-96d45175ab67n%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/CANWgJS5RcWPCSPghkpyBL3TH8iwv96ogjSbunVBbAdQ0rsTh6A%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-3Bie4XJNJ_WNDmH%3DJsuid4g5w9X%3D%2B8%3DTn3odWs0gZoZLHhQ%40mail.gmail.com.

Re: Release team members

['Olblak' via Jenkins Developers]

Hi Tim,

Thanks for driving this, I think that would be useful for me to be in the 
release team on the jenkins-ci organization

On Thu, Sep 23, 2021, at 9:48 AM, Tim Jacomb wrote:
> Hello
> 
> Continuing from 
> https://groups.google.com/g/jenkinsci-dev/c/YhXRKybGgMg/m/IRjH_VykCwAJ 
> 
> I would like to invite the previous release leads to join the release team 
> officially in jenkinsci/jenkins-infra GitHub organisations:
> 
> a release then consider stepping up for a release lead role for an LTS 
> release or joining the #jenkins-release room on Libera IRC
> 
>  * Beatriz Muñoz (@bmunozm)
> 
>  * Ildefonso Montero (@imonteroperez)
> 
>  * Mark Waite (@MarkEWaite)
> 
>  * Raihaan Shouhell (@res0nance)
> 
>  * Basil Crow (@basil)
> 
> 
> Daniel, Olivier (olblak), Wadeck, Oleg you are all in the team in 
> jenkins-infra, would you like to join the team in jenkinsci as well?
> 
> If you would like to join then please reply to this email.
> For others if you would like to get involved in a release then consider 
> stepping up for a release lead role for an LTS release or joining the 
> #jenkins-release room on Libera IRC
> 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-3BieVaZAEP3wJBVzpKe1g5YvjEBcRag49vSJ-Fy8Q2%3DDQCw%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/d63ba734-1a99-45c0-bc26-4fb34b5724ca%40www.fastmail.com.

Emeritus concept for Jenkins developers (was: Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team)

[Baptiste Mathus]

Hi all,

Following up on Jesse's comment, and as I was reflecting on this a few days
ago: I think we should introduce an Emeritus concept/status for Jenkins
core team's inactive members.

That would allow "cleaning up" the list for various reasons, while still
recognizing the contributions of such individuals.

I think, akin to Apache does in many projects, we should also have a
straightforward way for such members to be reinstated inthe core list when
they would request it.

WDYT?

Once we agree on this principle, we will also need to dicuss the "inactive
member" definition, but that's a secondary concern for now IMO.

Baptiste

Le mer. 22 sept. 2021 à 14:10, wfoll...@cloudbees.com <
wfollon...@cloudbees.com> a écrit :

> +1 as well, really involved in the community so it's just natural :-)
>
> On Wednesday, September 22, 2021 at 2:05:32 PM UTC+2 Jesse Glick wrote:
>
>> If he is interested, absolutely +1!
>>
>> By the way there are a number of people in
>> https://github.com/orgs/jenkinsci/teams/core/members who are no longer
>> active in the Jenkins community and who should likely be removed.
>>
> --
> 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/2735a776-6bdf-485c-bdb0-96d45175ab67n%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/CANWgJS5RcWPCSPghkpyBL3TH8iwv96ogjSbunVBbAdQ0rsTh6A%40mail.gmail.com.

Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team

[Raihaan Shouhell]

+1 he has been leading the charge on a variety of improvements

On Thu, Sep 23, 2021, 4:25 PM Baptiste Mathus  wrote:

> +1. IMO Basil is wa past the minimum criteria to get this status.
>
> Le mer. 22 sept. 2021 à 11:14, Oleg Nenashev  a
> écrit :
>
>> Dear all,
>>
>> Basil has been a very active contributor to the Jenkins core since 2020,
>> and he has contributed a lot to Jenkins over the past several years. He is
>> an active community member, and he helps a lot with the technical debt
>> cleanup and code reviews in Jenkins.
>>
>> It would be great to have Basil joining the Jenkins core maintainers
>> team. I propose to officially add Basil to the Jenkins core team. IMHO the
>> code reviewer stage can be skipped, because he has been already
>> contributing a lot to the reviews. Opinions/votes?
>>
>> References:
>>
>>- https://github.com/basil
>>- Jenkins core maintainers team and ladder:
>>
>> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#team
>>
>> Best regards,
>> Oleg Nenashev
>>
>> --
>> 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/0c920f79-f7b7-4299-92d7-15a814821632n%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/CANWgJS55rBhwXNumbJL2rLRa1cc4h%2BpjLgiM00n%2BByBLsxf9fw%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/CAFoxvgy%3D%3Dx0C6nibxugptU_Mm3p2zaKHNdn%3Dv6%3D7yBpwPDsSOw%40mail.gmail.com.

Re: Proposal: Adding Basil Crow to the Jenkins Core maintainers team

[Baptiste Mathus]

+1. IMO Basil is wa past the minimum criteria to get this status.

Le mer. 22 sept. 2021 à 11:14, Oleg Nenashev  a
écrit :

> Dear all,
>
> Basil has been a very active contributor to the Jenkins core since 2020,
> and he has contributed a lot to Jenkins over the past several years. He is
> an active community member, and he helps a lot with the technical debt
> cleanup and code reviews in Jenkins.
>
> It would be great to have Basil joining the Jenkins core maintainers team.
> I propose to officially add Basil to the Jenkins core team. IMHO the code
> reviewer stage can be skipped, because he has been already contributing a
> lot to the reviews. Opinions/votes?
>
> References:
>
>- https://github.com/basil
>- Jenkins core maintainers team and ladder:
>https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#team
>
> Best regards,
> Oleg Nenashev
>
> --
> 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/0c920f79-f7b7-4299-92d7-15a814821632n%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/CANWgJS55rBhwXNumbJL2rLRa1cc4h%2BpjLgiM00n%2BByBLsxf9fw%40mail.gmail.com.

Release team members

[Tim Jacomb]

Hello

Continuing from
https://groups.google.com/g/jenkinsci-dev/c/YhXRKybGgMg/m/IRjH_VykCwAJ

I would like to invite the previous release leads to join the release team
officially in jenkinsci/jenkins-infra GitHub organisations:


   -

   Beatriz Muñoz (@bmunozm)
   -

   Ildefonso Montero (@imonteroperez)
   -

   Mark Waite (@MarkEWaite)
   -

   Raihaan Shouhell (@res0nance)
   -

   Basil Crow (@basil)


Daniel, Olivier (olblak), Wadeck, Oleg you are all in the team in
jenkins-infra, would you like to join the team in jenkinsci as well?

If you would like to join then please reply to this email.

For others if you would like to get involved in a release then consider
stepping up for a release lead role for an LTS release or joining the
#jenkins-release room on Libera IRC

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-3BieVaZAEP3wJBVzpKe1g5YvjEBcRag49vSJ-Fy8Q2%3DDQCw%40mail.gmail.com.