I'm interested. On Tue, Jun 16, 2020 at 2:22 PM Oleg Nenashev <[email protected]> wrote:
> Hi all, > > I would like to recover this thread. As a part of the CDF graduation > criteria, we are expected to pass the Core Infrastructure Initiative > checklist. There is a thread about it here > <https://groups.google.com/forum/#!msg/jenkinsci-dev/n1qH1K5_td0/pA_nUN_6BgAJ> > . > According to the CII criteria for issue reporting > <https://bestpractices.coreinfrastructure.org/en/projects/3538#reporting> > , > > - The project MUST acknowledge a majority of bug reports submitted in > the last 2-12 months (inclusive); the response need not include a fix > - The project SHOULD respond to a majority (>50%) of enhancement > requests in the last 2-12 months (inclusive). > > Under this criteria the "project" means the Jenkins core and its > components, our current certification process > <https://bestpractices.coreinfrastructure.org/en/projects/3538> does not > include plugins. I did some queries in Jira. We are somewhat compliant with > the first criteria (thanks to Daniel Beck and other contributors who > occasionally scrub issues), but not with the second one. > > In order to hit the goal, I think we need to discuss starting the triage > team as it was proposed by Alex Earl, and maybe introducing a formal > process for acknowledging defects (e.g. "confirmed" label). Would anyone be > interested to participate? > > Best regards, > Oleg > > > > On Sunday, December 16, 2018 at 1:05:08 PM UTC+1, Oleg Nenashev wrote: >> >> Hi all, >> >> Over last years I have been triaging incoming JIRA issues in the JENKINS >> project together with several other contributors. I was also a default >> assignee in the “_unsorted >> <https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20component%20%3D%20_unsorted>” >> JIRA component which was suggested by default in the issue creation screen. >> Currently there are around 500 issues in the component, and I suspect I >> processed hundreds of JIRA issues and assigned them to proper components >> since the _unsorted was introduced. >> >> As some of the Jenkins contributors already know, I will have a very >> limited availability in the community over the next several months >> (personal matters). I will be unable to provide a timely response in the >> tickets. I would like to ensure that I do not become a bottleneck in the >> issue triage process. >> >> - Several days ago I removed the default assignee in *_unsorted* and >> unassigned the rest of open tickets >> - There are only 40 open tickets >> >> <https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20component%20%3D%20_unsorted%20and%20status%20%3D%20Open> >> now, many of them can be actually closed >> - This component has explicit disclaimer that there is NO response >> ETA, and I was not able to process all requests there. I welcome >> anybody to >> become a default assignee there, e.g. on a rotation basis. >> - Next week I will stop triaging incoming issues in the Jenkins core >> - I used to take a look at new issues every few days after I started >> maintaining the Jenkins core (regressions, misreported high-severity >> issues), but it is not sustainable going forward >> - I will also stop triaging issues in plugins I used to maintain and >> then marked for adoption, but which have not been adopted yet >> - Examples: EnvInject <https://plugins.jenkins.io/envinject>, Mask >> Passwords <https://plugins.jenkins.io/mask-passwords>, Release >> <https://plugins.jenkins.io/release>, Periodic Backup >> <https://plugins.jenkins.io/periodicbackup>, etc. >> >> Thanks a lot to everybody who contributes to the issue triage in Jenkins >> JIRA! >> >> Best regards, >> Oleg >> >> >> >> On Tuesday, April 11, 2017 at 6:49:42 PM UTC+2, slide wrote: >>> >>> Any time that people can give is great. Even a spare 10 minutes here and >>> there would be helpful if you spread it across a large number of people. >>> >>> On Tue, Apr 11, 2017 at 4:01 AM Mark Waite <[email protected]> wrote: >>> >>>> My situation is similar to Oleg's. My first priority is to review bugs >>>> submitted against the plugins I maintain, and to reproduce bugs for those >>>> plugins, and to create automated environments to reproduce those bugs. >>>> Helping with other projects will come as a second priority. >>>> >>>> Mark Waite >>>> >>>> On Tue, Apr 11, 2017 at 3:13 AM Oleg Nenashev <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I am in. >>>>> >>>>> Right now I dedicate time for reviewing incoming issues in the core, >>>>> Remoting, "_unsorted", a couple of other modules and a bunch of plugins I >>>>> am supposed to maintain. I can unlikely dedicate more time to review other >>>>> components (would prefer to do bugfixing in core/remoting), but at least I >>>>> am ready to keep working on the current stuff. >>>>> >>>>> BR, Oleg >>>>> >>>>> 2017-04-11 10:07 GMT+02:00 Daniel Beck <[email protected]>: >>>>> >>>>>> >>>>>> > On 10.04.2017, at 22:44, Slide <[email protected]> wrote: >>>>>> > >>>>>> > if you are interested! >>>>>> >>>>>> I am. >>>>>> >>>>> >>>>>> -- >>>>>> 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/XToix3QpL_k/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> [email protected]. >>>>>> >>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/2F5B15D7-B147-4F4B-B8CE-04760B1F9A7D%40beckweb.net >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >>>>> 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 on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAypc6o5YBYDAVNKqD0euqGhLJ%2B-Z929s8fkZU51ZZv%2BA%40mail.gmail.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAypc6o5YBYDAVNKqD0euqGhLJ%2B-Z929s8fkZU51ZZv%2BA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> 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 on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHqHF8aboPTWkGQYx%2BF_qCHPd2bMGZ8HChVauPuk6NbGQ%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHqHF8aboPTWkGQYx%2BF_qCHPd2bMGZ8HChVauPuk6NbGQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- > 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 on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/31c5018d-da6f-4f71-93db-aab3ebcd9aaao%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/31c5018d-da6f-4f71-93db-aab3ebcd9aaao%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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH%3DvV1Rf7Ggea_Jj7V%3DG9Sq5tHpL%2BBhmKSYSASdb%2BZmKQ%40mail.gmail.com.
