Skip to content

A question about the Issue tracker.#4

Closed
arbox wants to merge 1 commit into
ruby:masterfrom
arbox:patch-1
Closed

A question about the Issue tracker.#4
arbox wants to merge 1 commit into
ruby:masterfrom
arbox:patch-1

Conversation

@arbox

@arbox arbox commented Feb 17, 2017

Copy link
Copy Markdown
Contributor

This is merely not a pull request but a question, since the README points for issue tracking to this repository. And the repository has no issues enabled.
The question is: Where is the right place to work with Tcl/Tk issues?

This is merely not a pull request but a question, since the README points for issue tracking to this repository. And the repository has no issues enabled.
The question is: Where is the right place to work with Tcl/Tk issues?
@basex

basex commented Feb 28, 2017

Copy link
Copy Markdown

I'm not a maintainer, but I think it's on the Ruby Issue Tracker: https://bugs.ruby-lang.org/projects/ruby-trunk/issues

@arbox

arbox commented Mar 1, 2017

Copy link
Copy Markdown
Contributor Author

I'm asking that here since many issues have been moved from the Ruby Trunk. Tk does not belong to the Ruby stdlib any more, it's a separate library packaged as a gem.

@hsbt

hsbt commented Mar 1, 2017

Copy link
Copy Markdown
Member

This is a canonical place to report the issue of tk gem. We have no resource to handle only issue report. Therefore we open only pull request also report with patch or reproduction code like a test.

@arbox

arbox commented Mar 1, 2017

Copy link
Copy Markdown
Contributor Author

@hsbt Ok, that clarifies the state of affairs :) I'll formulate a note for the projects readme about this point as a new pull request. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants