Re: INFRA project issues migration from Jira to Github

The information was included in the import All of them have the reporter, and the ones assigned have it in the expanded details section, e.g https://github.com/jenkins-infra/helpdesk/issues/2690 GitHub doesn’t let you report as another user, and assignee would require a Jira -> GitHub mapping,

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

Hi All, Given Oleg's (limited) availability, we'll schedule the GSoC Knowledge Transfer for* tomorrow, Thursday 13 January, 2022 at 4pm UTC | 8am PT* - and since this time aligns with the Advocacy Outreach Sig meeting we will use tomorrow's Adv Outreach Sig meeting for this knowledge transfer.

Re: INFRA project issues migration from Jira to Github

It seems that the reporters (and assignees) of the issues have not been mapped. Is this planned? > Am 12.01.2022 um 14:50 schrieb 'Herve Le Meur' via Jenkins Developers > : > > Hello! > > As some of you might have already noticed, all issues related to the > Infrastructure project have been

Re: Governance meeting Jan 12, 2022

Hi all, I will have to skip today's meeting. I barely slept last night, and I am not very productive. I do not have major updates from my side. - Still waiting for green light from the Linux Foundation to enable EasyCLA for Jenkins - CDF has not yet been accepted to the Inclusive

Governance meeting Jan 12, 2022

Today's governance meeting will start at 9:00 PM UTC. Agenda items include: - News - Jenkins 2.319.1 LTS security released today - Jenkins 2.330 weekly

INFRA project issues migration from Jira to Github

Hello! As some of you might have already noticed, all issues related to the Infrastructure project have been migrated from Jira (https://issues.jenkins.io/projects/INFRA/issues) to Github (https://github.com/jenkins-infra/helpdesk/issues?q=label%3Aimported-jira-issue) It's almost done,

Re: Proposal: Move Jenkins Test Harness issue tracker to GitHub Issues

I archived the component in Jira for the ones I found, not all of them mapped to a component and I didn't dig too hard. Archiving seems to keep the component there but no new issues can be added which maps to what you said Jesse Anyone can migrate the issues, Herve is the one who did this most