I'm interested. Please include me. Mark Waite
On Mon, Apr 10, 2017 at 2:57 PM Richard Bywater <[email protected]> wrote: > Not sure how much time I'll be able to dedicate but interested in keeping > getting up-to-date about this effort. > > Richard. > > On Tue, 11 Apr 2017 at 08:44 Slide <[email protected]> wrote: > > I wanted to follow up on this now that all the craziness of the start of > the year (new babies and adoptions in my family!) are done. There were a > few people who responded to me about being interested in helping with this > Bug Triage. If you are still interested, please let me know. I setg up a > filter on JIRA [1] for people to work from, with the idea being we would > look at issues in core and the wizard suggested plugins as an initial go. > There are also several hundred issues with no component at all [2] that > could use a look as well. If anyone is interested in adding their plugin to > the triage, please let me know and I will update the filter and send it > out. I'd like to start the team looking at issues at the start of May. As a > review, we would like to do the following: > > 1) Assign correct components to issues > 2) Replicate issues as possible and update with findings to help issue > owners recreate the issue (PR's with new tests would be great in this > regard) > 3) Do NOT set assignee on issues because of the workflow that people use > 4) Close out issues as "Incomplete" if they are old and have few details > to try and reproduce them > > Please let me know if I am missing anything and if you are interested! > > Regards, > > Alex > > 1 - > https://issues.jenkins-ci.org/browse/JENKINS-22?jql=project%20%3D%20JENKINS%20AND%20(resolved%20is%20EMPTY%20OR%20resolution%20%3D%20Unresolved)%20AND%20component%20in%20(core%2C%20cloudbees-folder-plugin%2C%20antisamy-markup-formatter-plugin%2C%20build-timeout-plugin%2C%20timestamper-plugin%2C%20ws-cleanup-plugin%2C%20ant-plugin%2C%20gradle-plugin%2C%20workflow-aggregator-plugin%2C%20github-organization-folder-plugin%2C%20pipeline-stage-view-plugin%2C%20git-plugin%2C%20subversion-plugin%2C%20ssh-slaves-plugin%2C%20matrix-auth-plugin%2C%20pam-auth-plugin%2C%20ldap-plugin%2C%20email-ext-plugin%2C%20email-ext-plugin%2C%20mailer-plugin)%20ORDER%20BY%20key > > 2 - > https://issues.jenkins-ci.org/browse/JENKINS-11545?jql=project%20%3D%20JENKINS%20AND%20component%20is%20EMPTY%20 > > On Mon, Jan 30, 2017 at 12:45 PM Oleg Nenashev <[email protected]> > wrote: > > Hi, > > Just FYI, at some point we have created the _unsorted > <https://issues.jenkins-ci.org/browse/JENKINS-41572?jql=project%20%3D%20JENKINS%20AND%20component%20%3D%20_unsorted>component > in JIRA. It is being shown as the first one in the component selection > list, so some issues go into this component. Mostly there are barely > created issues, unfortunately. Of course such component does not prevent > people from randomly setting components like they do now sometimes. > > Generally I agree with the summary above. The project will definitely > benefit from any kind of a triaging team IFF we find people, who are ready > to consistently dedicate time to it > > вторник, 24 января 2017 г., 23:33:21 UTC+1 пользователь slide написал: > > Sure, that shouldn't be a problem > > On Tue, Jan 24, 2017 at 3:07 PM Ullrich Hafner <[email protected]> > wrote: > > Am 23.01.2017 um 22:47 schrieb Slide <[email protected]>: > > Ok, to summarize... > > 1) We don't want to set the assignee > 2) We do want to make sure the component(s) are correct > 3) We want to try and replicate the issue and add findings > 4) We want to close out issues that are very old with little information > to clean things up > > Is there anything I missed? > > > Would it be possible to label issues in step 3 that are important and not > overly complex to reproduce? I’m planning to assign several student > projects to create acceptance tests for the ATH in the upcoming summer > semester. The last time we tried to do this was not very effective since it > took a long time to find good issues that could be transformed to an > acceptance test. > > Thanks for the discussion on this! > > Alex > > On Mon, Jan 23, 2017 at 2:37 PM Ullrich Hafner <[email protected]> > wrote: > > I would prefer to use the default Jira workflow as much as possible. So > adding a new start state would be much simpler. No other transition needs > to be changed in this case. > > > Am 21.01.2017 um 23:18 schrieb Daniel Beck <[email protected]>: > > > > > > > >> On 21.01.2017, at 15:07, Baptiste Mathus <[email protected]> wrote: > >> > >> adding the NEW status > >> > >> Having a state to basically say: "this is issue is new, but has not > been reviewed, so may be invalid/incomplete/whatever for whatever reason" > makes sense IMO. > > > > Shouldn't we create a new "To Do" or "Confirmed" status then, to > initialize all existing issues that aren't in progress etc. to that > unverified status? > > > > -- > > 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/9C189939-804F-40FB-B19F-2EF43E6EC357%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/8C8FA5DF-8CEA-4F3C-8599-F76C9C53BD22%40gmail.com > . > 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/CAPiUgVdm8BYO2Cwnpq_k_AJB5VeQY%3Dc5ZV9ceBmFv%2BALX8-9Kw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdm8BYO2Cwnpq_k_AJB5VeQY%3Dc5ZV9ceBmFv%2BALX8-9Kw%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/D65B16DD-EFEC-47F1-BC9B-4893379BEDC4%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/D65B16DD-EFEC-47F1-BC9B-4893379BEDC4%40gmail.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/aa645daf-82b0-4ac5-a5a9-fec900f4ee18%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/aa645daf-82b0-4ac5-a5a9-fec900f4ee18%40googlegroups.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/CAPiUgVd9zMw-3saX7p3_o_auCp4ZC1Ot7dSPsOXXLZsqc4z%2BMw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVd9zMw-3saX7p3_o_auCp4ZC1Ot7dSPsOXXLZsqc4z%2BMw%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/CAMui944h_BRHUQiFzheZdCKidHop9JD8KYsQ7qDKOYXzxpWRiA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui944h_BRHUQiFzheZdCKidHop9JD8KYsQ7qDKOYXzxpWRiA%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/CAO49JtHGBD%3DgJKY_X4ugEc-K%3D1GCy3%2BECxTjTy0AKzgZVdP-WA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
