-
Notifications
You must be signed in to change notification settings - Fork 200
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
VerboseIterable and VerboseIterator are not tested #111
Comments
@yegor256 OK, I labeled it as |
@celezar it's yours now, please proceed keeping in mind our principles. Feel free to ask any technical questions right here in the ticket The budget of this task is 30 mins. This is exactly how much time will be compensated, when the task is completed. Read about our Definition of Done |
@yegor256 thanks for the ticket, your account was topped for 15 mins, payment 000-63718d45 |
@celezar check this "no obligations principle".. This task is on your name for at least 15 days. If you can't close it within the next 48 hours I will have to assign someone else to it. This article should help if you're stuck; added -30 to your rating, now it is equal to -30 |
@davvd please give it to someone else |
@davvd please assign this one to me |
@davvd assign @M4Solutions to this task pls |
@yegor256 done. @M4Solutions you are assigned to this task. please proceed... |
@M4Solutions the task is your hands for the last 16 days.. keep in mind that if it's not closed in the next 48 hours, it will be re-assigned to someone else, see No Obligations principle. This article should help if you're stuck -30 to your rating, your total score is +0 |
@marcuss in which pull request was it fixed? keep in mind that every time you fix a problem, it's a good practice to inform the ticket author about the PR it was solved in. also, see this: http://www.yegor256.com/2014/11/24/principles-of-bug-tracking.html |
@marcuss I'm closing, but still expecting you to post a message here with the number of PR |
@M4Solutions I don't see any messages from you above, not sure if there was actual contribution (correct me if I'm wrong) |
@davvd the thing is that I changed names, I was @M4Solutions, I changed that this week |
@marcuss next time, please inform us about it in advance :) |
Let's create unit tests for
VerboseIterable
andVerboseIterator
The text was updated successfully, but these errors were encountered: