Fix bugreport URL in error.c
|ruby -v:||ruby 2.0.0p353 (2013-11-22 revision 43784) [i686-linux]||Backport:||1.9.3: UNKNOWN, 2.0.0: UNKNOWN|
error.c refers to in REPORTBUG_MSG, which is only a redirect to . Instead it should refer to bugs.ruby-lang.org directly:
- it's the "canonical" ressource for anything bug-related
- it's already linked to from many other source files
#2 Updated by Yui NARUSE almost 2 years ago
- Status changed from Open to Rejected
#3 Updated by Marcus Stollsteimer almost 2 years ago
I agree that "bugs.ruby-lang.org" is not only a place to report bugs.
But it has all the relevant information on bug reporting right there on the root page ("How to Report a Bug"),
and it will always need to have that information, or it stops being bugs.ruby-lang.org.
Why use a second ressource that doesn't even exist?
It's already referenced in many places in the code, so in case you would want to move it to another site there would need to be fixes in the code anyway.
#4 Updated by Zachary Scott almost 2 years ago
- Status changed from Rejected to Feedback
- Assignee set to Yui NARUSE
I'm not sure why it would be unacceptable for next minor? We should be allowed to make backwards incompatible changes after 2.1 is released for next minor.
Anyways, I agree maybe it's better to implement the page on ruby-lang.org.
I can work on this.
#5 Updated by Marcus Stollsteimer almost 2 years ago
I assume that bugs.r-l.org is the established and known site for reporting bugs. So now users that go there (to report bugs) should be pointed first to a HowTo on www.r-l.org and then come back to bugs.r-l.org to actually open an issue? That's also not very convincing to me.
And I do not see any "backwards incompatibility" at all. The existing redirect from www.ruby-lang.org of course should be active as long as some officially supported branch points there.
Note also that www.r-l.org/bugreport.html hadn't existed for I do not know how long, maybe since the big reworking of the site several years ago, where maybe it was overlooked that it is referenced from the Ruby source. IMO that's a good argument for pointing to a more general ressource like bugs.ruby-lang.org. Even more so since that same ressource is already linked to from many places in the code.
Or alternatively error.c could just point to www.ruby-lang.org/.