tell where to file star bugs on rakudo web site

[rakudo]

tell where to file star bugs on rakudo web site

[stmuk]

The main R* README explains where to file bugs as does http://rakudo.org/tickets/

Not sure what this request means?

[coke]

The Readme says:

Bug reports about Rakudo Star or the Perl 6 specification should be sent to
[email protected] with the moniker [BUG] (including the brackets) at the
start of the subject so that it gets appropriately tagged in the RT system

which is, as I understand it, incorrect.

(1, but trivial, Don't tell people to use [BUG])
2, and more important: issues about star that are about the compiler should go to RT; Issues about star itself should come here; issues about modules should go to whatever issue system those modules use. Issues about the spec also have a different landing point. (perl6/roast/issues on github, probably)

[pmichaud]

When I did the original page for this, I figured that someone looking up "how to file bug reports" is fairly unfamiliar with the nuances of Rakudo (compiler) vs Rakudo Star vs modules and so on, and I'd rather just get a bug report *somehow* and the team figures out how to nicely forward it to the correct queue. I don't want someone to have to do a lot of investigating in order to file a bug report. So, perhaps better is to mention all of the issue trackers that exist, but also say "if you just want to file a bug report and you're not sure where it should go, then use [some tracker that won't mind handling mis-filed requests]." Pm

…

On Mon, Jul 31, 2017 at 08:30:32AM -0700, Will Coleda wrote: The Readme says: > Bug reports about Rakudo Star or the Perl 6 specification should be sent to > ***@***.*** with the moniker [BUG] (including the brackets) at the > start of the subject so that it gets appropriately tagged in the RT system which is, as I understand it, incorrect. (1, but trivial, Don't tell people to use [BUG]) 2, and more important: issues about star that are about the *compiler* should go to RT; Issues about star itself should come here; issues about modules should go to whatever issue system those modules use. Issues about the spec also have a different landing point. (perl6/roast/issues on github, probably)

[zoffixznet]

2, and more important: issues about star that are about the compiler should go to RT; Issues about star itself should come here; issues about modules should go to whatever issue system those modules use. Issues about the spec also have a different landing point. (perl6/roast/issues on github, probably)

IMO that's overly complex. People will just be afraid to make a mistake of reporting in the wrong place and won't report anything.

[coke]

I agree that it's complex; I was just describing the various queues, which is why, I think, this ticket was opened in the first place, because someone opened a compiler ticket on a star issue and got redirected.

If the consensus is keep it the way it is, and volunteers will sort on the receiving end, that's fine; maybe we can add a community "How to report a bug" on the docs site that still stresses that submitting to RT is fine, but if you want to take the time, you could do what the volunteer who is going to sort your ticket is going to have to do anyway.

... if we're going to do that, maybe RT isn't the default, but that's a whole other can of worms.

[stmuk]

Users aren't likely to know which bugs are R* specific and which are upstream or how to use RT without help. So looks like this is to do with updating documentation elsewhere and not in Rakudo Star anyway.

Closing