On Sat, Nov 15, 2025 at 8:47 PM <[email protected]> wrote:
> [email protected] > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/jenkinsci-dev/topics> > Google > Groups > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > [image: > Google Groups Logo] > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > Topic digest > View all topics > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/jenkinsci-dev/topics> > > - 2.528.3 release lead <#m_-7762710450594949480_group_thread_0> - 4 > Updates > - Migration plan for core components to Jira > <#m_-7762710450594949480_group_thread_1> - 3 Updates > > 2.528.3 release lead > <http://groups.google.com/group/jenkinsci-dev/t/9da39ce1fef627ca?utm_source=digest&utm_medium=email> > Hervé <[email protected]>: Nov 15 12:29PM -0800 > > Hello > > Is anyone interested in being the release lead for 2.528.3? > > Planned dates can be seen on the event calendar: > https://www.jenkins.io/events/#event-calendar > Release candidate by 26th November > Release on 10th December > > The documentation is at: > > https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md > > Past release leads will be available to answer any questions and provide > guidance. > > We chat in #jenkins-release on libera IRC, > https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix > channel. > > Anyone interested? > > Thanks > Hervé > Hervé <[email protected]>: Nov 15 12:35PM -0800 > > Interested to be release lead again, but no problem letting anyone else if > wanted. > > On Saturday, 15 November 2025 at 21:29:38 UTC+1 Hervé wrote: > > Shalini Sudarsan <[email protected]>: Nov 15 12:48PM -0800 > > Hi Herve, > I am interested in being the release lead. > I am currently a DevOps Engineering Manager. Would be able to handle it. > > Please let me know. Thank you. > https://www.linkedin.com/in/shalini-sudarsan-473bb535/ > > Shalini Sudarsan > > > On Sat, Nov 15, 2025 at 12:36 PM Hervé <[email protected]> > wrote: > > Kris Stern <[email protected]>: Nov 15 10:39PM > > Hi Shalini, > > I mean you can work with Herve on this if he is willing since you will not > have access to everything to handle the tasks on your own, as you are not a > part of the Release Team. > > Herve, what do you think? > > Best, > Kris > ________________________________ > From: [email protected] <[email protected]> on > behalf of Shalini Sudarsan <[email protected]> > Sent: 16 November 2025 04:48 > To: [email protected] <[email protected]> > Subject: Re: 2.528.3 release lead > > Hi Herve, > I am interested in being the release lead. > I am currently a DevOps Engineering Manager. Would be able to handle it. > > Please let me know. Thank you. > https://www.linkedin.com/in/shalini-sudarsan-473bb535/ > > Shalini Sudarsan > > > On Sat, Nov 15, 2025 at 12:36 PM Hervé <[email protected] > <mailto:[email protected]>> wrote: > Interested to be release lead again, but no problem letting anyone else if > wanted. > > On Saturday, 15 November 2025 at 21:29:38 UTC+1 Hervé wrote: > Hello > > Is anyone interested in being the release lead for 2.528.3? > > Planned dates can be seen on the event calendar: > https://www.jenkins.io/events/#event-calendar > Release candidate by 26th November > Release on 10th December > > The documentation is at: > > https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md > > Past release leads will be available to answer any questions and provide > guidance. > > We chat in #jenkins-release on libera IRC, > https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix > channel. > > Anyone interested? > > Thanks > Hervé > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]<mailto: > [email protected]>. > To view this discussion visit > https://groups.google.com/d/msgid/jenkinsci-dev/e12ec1e2-037b-4c09-bd6c-3b21e57cc3fcn%40googlegroups.com > < > https://groups.google.com/d/msgid/jenkinsci-dev/e12ec1e2-037b-4c09-bd6c-3b21e57cc3fcn%40googlegroups.com?utm_medium=email&utm_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 [email protected]<mailto: > [email protected]>. > To view this discussion visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPAR%2BmJ4rN3LJw__afoQMj4LUOFky74rcQtaez%2B0sNG3bSC8TA%40mail.gmail.com > < > https://groups.google.com/d/msgid/jenkinsci-dev/CAPAR%2BmJ4rN3LJw__afoQMj4LUOFky74rcQtaez%2B0sNG3bSC8TA%40mail.gmail.com?utm_medium=email&utm_source=footer > >. > Back to top <#m_-7762710450594949480_digest_top> > Migration plan for core components to Jira > <http://groups.google.com/group/jenkinsci-dev/t/48443b52d6df450e?utm_source=digest&utm_medium=email> > Daniel Beck <[email protected]>: Nov 15 07:04PM +0100 > > Thanks, the descriptions in the most recent import look a lot better. > > I cannot find any issues reported against the 'cli' component in Jira in > your imports though. The 'cli' Jira component is tracking issues in the > CLI, which is part of jenkinsci/jenkins. If this is intentional, it seems > important enough to mention in the JEP. > > Is there a test import of remoting issues we could review? > How are you going to handle issues with both 'core' and 'remoting' > components (and similar overlaps)? Does one repo take precedence, e.g., > only import into jenkinsci/jenkins, not jenkinsci/remoting? Or perhaps into > remoting, it being the more narrowly scoped repo? > > How are you going to update the changelog YAML format, generation and > rendering in jenkins.io to account for the change in issue tracker? I > cannot find any related PRs. > > -- > CONFIDENTIALITY NOTICE:_ This email and any attachments contain > confidential and proprietary information of CloudBees intended only for > the > named recipient(s). Unauthorized use or distribution is prohibited. If you > received this in error, please notify the sender and delete this email._ > Tim Jacomb <[email protected]>: Nov 15 09:56PM > > > I cannot find any issues reported against the 'cli' component in Jira in > your imports though. The 'cli' Jira component is tracking issues in the > CLI, which is part of jenkinsci/jenkins. If this is intentional, it seems > important enough to mention in the JEP. > > CLI issues will be in the next test migration, kicked off later tonight. > Will be here: > https://github.com/timja-org/jenkins-gh-issues-poc-11-15/issues > > > How are you going to handle issues with both 'core' and 'remoting' > components (and similar overlaps)? > > They will all go to the jenkins repository if they have the core component. > (handled by the fact we are archiving the issues as part of the migration > which prevents them showing up in searches). > > I'll do a bit of sweeping through the ones with multiple components that > are open and see if any can be assigned better. > > > Is there a test import of remoting issues we could review? > > I was planning to do the other core components not going to the jenkins > repo afterwards. > There's an export that was run here though: > https://github.com/timja-org/remoting-gh-issues-poc-11-15/issues > > (Note this will include multi component issues as the way they are excluded > is by archiving them after migration) > > > How are you going to update the changelog YAML format, generation and > rendering in jenkins.io to account for the change in issue tracker? I > cannot find any related PRs > > https://github.com/jenkins-infra/jenkins.io/pull/8541 > > On Sat, 15 Nov 2025 at 18:05, 'Daniel Beck' via Jenkins Developers < > [email protected]> wrote: > > Ullrich Hafner <[email protected]>: Nov 15 11:08PM +0100 > > > > > How are you going to handle issues with both 'core' and 'remoting' > components (and similar overlaps)? > > > They will all go to the jenkins repository if they have the core > component. (handled by the fact we are archiving the issues as part of the > migration which prevents them showing up in searches). > > > I'll do a bit of sweeping through the ones with multiple components that > are open and see if any can be assigned better. > > Is the information about other components lost after the migration? E.g., > JENKINS-76249 has core, credentials-plugin, ssh-credentials-plugin. > I don’t see this information in > https://github.com/timja-org/jenkins-gh-issues-poc-11-12/issues/5375 > > What is the plan with cross project issues? Is it still possible to > connect them somehow in the affected repositories? > Back to top <#m_-7762710450594949480_digest_top> > You received this digest because you're subscribed to updates for this > group. You can change your settings on the group membership page > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/jenkinsci-dev/join> > . > To unsubscribe from this group and stop receiving emails from it send an > email to [email protected]. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFt5oa_JuLrVQNKz3PLpsJQb-if3tC1Q_BqY1SLXe9DVrZC%2BWw%40mail.gmail.com.
