Re: Bug reporting etiquette question

You should attach the code to the ticket - otherwise when the snippet times
out, there's no record of the code. If it's in a git repo somewhere, that's
also fine, include a link to the specific code. In general, the more golfed
(shorter) the code is that shows the issue, the better.

Regarding the versions - report out the versions in the comment (works on
X, fails on Y) - no need to attach anything here. Also report OS versions,
dependencies, etc.

No need to reach out directly to developers for this.

On Fri, Nov 15, 2024 at 4:49 AM ToddAndMargo via perl6-users <
[email protected]> wrote:

> Hi All,
>
> I am about to report a regression bug over on
>
>     https://github.com/rakudo/rakudo/issues/new
>
> A question about bug reporting etiquette:
>
> 1) to reproduce the bug is 150 line of code.  Do
> I attach the code to the bug or do I post it
> up on vpaste.net?
>
> 2) I have two different revision of Rakudo.  The older one
> without the bug and the younger one with the bug.
>
> I am sure they do not want those both attached.  If
> the developer can give me his eMail address, I can send
> him an Ice Drive invite with my code and the two
> Rakudos.  Is this the right way to go about it?
>
> Many thanks,
> -T
>
>