-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Look into adding Sphinx docs #127
Comments
Hello John, I am a new PM for the CGP and I am trying to close out old tickets. I see a lot of tickets of yours that are OPEN, many with the tag of ready. Can we close these? |
Hi @cricketsloan , and welcome to the GI! Github projects typically have dozens of open issues to track feature requests, enhancements, bugs, etc. The "Ready" label just implies there's nothing blocking the ticket from being worked on, but doesn't indicate its priority or associated milestone or deadline. Is there a different label than "ready" you want me to use? |
Thanks, John.
The tickets that I am looking at are in the state of "Code Review" on the
waffle board. Seeing "ready" implied to me that they were reviewed. What
I am hearing is that they likely belong in TODO and there is no current
code to review.
…On Fri, Mar 23, 2018 at 10:55 AM, John Vivian ***@***.***> wrote:
Hi @cricketsloan <http:///cricketsloan> , and welcome to the GI!
Github projects typically have dozens of open issues
<https://github.com/BD2KGenomics/toil/issues> to track feature requests,
enhancements, bugs, etc. The "Ready" label just implies there's nothing
blocking the ticket from being worked on, but doesn't indicate its priority
or associated milestone or deadline.
Is there a different label than "ready" you want me to use?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#127 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADJZQwk4VxCv8LKLUDvOM39UbEUaoMq1ks5thTcrgaJpZM4QGqAZ>
.
--
Cricket Sloan
|
No description provided.
The text was updated successfully, but these errors were encountered: