On Thu, Jan 19, 2017 at 12:51 PM Slide <[email protected]> wrote:
> If that is a common practice, then we can skip setting the assignee and > focus on component assignment and reproducibility, or we can have a > "whitelist" of plugins that we set assignee for. The goal isn't to make > things harder for maintainers, we want to help as much as possible by > funneling things to the correct place. If there is something else that > would be more helpful, or an additional scope, please bring it up. > > Confirming that bugs are repeatable is very valuable. I feel like I've wasted time on many occasions trying to verify poorly phrased bug reports. Recently I've become more direct (harsh) and less willing to spend time trying to duplicate a poorly phrased bug report. Cem Kaner's online course "Bug Advocacy" is a great introduction to effective bug reporting... Mark Waite > On Thu, Jan 19, 2017 at 12:48 PM Mark Waite <[email protected]> > wrote: > > On Thu, Jan 19, 2017 at 12:11 PM Jesse Glick <[email protected]> wrote: > > On Thu, Jan 19, 2017 at 12:34 PM, Slide <[email protected]> wrote: > > The outcome of a triage on a specific issue would be that the correct > > component(s) and assignee were there. > > Do we really need to set an assignee? For example for most > `{workflow,pipeline}-*-plugin` components there is intentionally no > default assignee. If and when someone intends to work on a fix, they > can assign to themselves. > > > As further support for what Jesse says, please don't assign me as an owner > for bugs in the git plugin or the git client plugin during the triage > process, unless you're willing to accept that I'll immediately remove that > assignment and return them to "Unassigned". > > I only assign bugs to myself when I want to indicate that I'm working on > them, or intending to work on them "soon". I use the list of bugs assigned > to me as a reminder of active work, not as another way of expressing the > component name. > > Mark Waite > > > > > -- > 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/CANfRfr0SRoe%2BWirJPscSjeLb_kXszYVFxTqpQDOCNjio86-TbQ%40mail.gmail.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/CAO49JtH_W8iHnQUL_xjV2fA-pCibkzfOkkU2P%2BzUNrdqV0H43w%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH_W8iHnQUL_xjV2fA-pCibkzfOkkU2P%2BzUNrdqV0H43w%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/CAPiUgVfcK4R8i4W%3DGs8mW94Agzn5jdyudQk_zpt_Yg3XC9%2BbuA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfcK4R8i4W%3DGs8mW94Agzn5jdyudQk_zpt_Yg3XC9%2BbuA%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/CAO49JtFXoCOozn%2B2bBce03X5DZbyNPA%3DucnAEjrKkzcpRSx4pQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
