Introduction

[Roger Riggs]

Hi Robin,

Don't underestimate the value of the collective knowledge on the right 
email list.
If you don't find an existing issue you are pursuing, create a new issue 
with enough of
a description to explain the issue.

A brief query to the appropriate email list may elicit support or 
additional context
that will be useful to fix it before you invest much of your time.

A reproducer is very valuable and recommended for someone else to fix an 
issue.
And whoever fixes it, generally provides the regression test.

Thanks, Roger


On 7/8/16 10:31 AM, Robin Stevens wrote:
> Rest assured, I wasn't planning on logging random issues hoping that
> somebody else would pick them up.
> I asked it for the scenario where I find a bug that I am planning to fix.
> In that case, I need an issue number to properly schedule the code review.
> So it is extremely useful that I am allowed to just log the issue, assign
> it to myself and start working on it.
>
> Robin
>
> On Fri, Jul 8, 2016 at 4:23 PM, dalibor topic <dalibor.topic at oracle.com>
> wrote:
>
>